DBAN FOG Boot Menu

[Sebastian Roth]

@Arrowtron Where exactly on the FOG server did you extract the DBAN iso/put the dban.bzi file? There has been some change in HTTP redirecting configuration (for the FOG API) that might get in the way here.

[Arrowtron]

@sebastian-roth I have placed the iso in this directory

/iso/dban.iso

executed this code below:

mount -t iso9660 -o loop /iso/dban.iso /var/www/html/dban

After that command it shows up like so:

[Wayne Workman]

I think that the ${boot_url} looks blank? Looking at the photo you posted, it just shows /dban/dban.bzi when it should show something more like http://awh-wc-fog/dban/dban.bzi @Sebastian-Roth what do you think? I’m just guessing here.

Maybe try this for the long parameter:
http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke --method quick" silent vga=785 Don’t remove the ${fog-ip} part, that’s a variable.

[Sebastian Roth]

@Wayne-Workman Seeing the output /dban/dban.bzi............. I have the impression that it actually starts to load the file properly. AFAIK iPXE is able to “reuse” the IP address from the last HTTP request (loading the menu boot.php). So this should be fine. Though I still think you are right. It ought to be http://${fog-ip}/... or ${boot-url} (hyphen not underscore).

@Arrowtron I am wondering about the connection reset. Are you able to take a packet capture of this? Run tcpdump -w dban.pcap port 80 on your FOG server and boot into the dban thing. Then stop the capture (Ctrl+C), upload to dropbox/googledrive and post a link here.

[x23piracy]

This is my PXE Advanced Menu, all of this is working:

:MENU
menu
item --gap -- blabla - PXE Boot Menu - blabla
item --gap --
item bootlocal Festplatte booten
item --gap Partition/Backup/Restore
item acronis2014 Acronis True Image 2014
item acronis2016 Acronis True Image 2016
item acronis2017 Acronis True Image 2017
item easeuspms EaseUS Partition Master Server 9.2.1
item aomeipau AOMEI Partition Assistant 6
item veeam Veeam Endpoint Backup Recovery
item --gap Password/Recovery/Restore/Repair
item erd2005 ERD Commander Windows XP
item dart7 DaRT 7.0 Windows 7 Server 2008 R2
item dart8 DaRT 8.0 Windows 8 Server 2012
item dart81 DaRT 8.1 Windows 8.1 Server 2012 R2
item dart10 DaRT 10.0 Windows 10 Server 2016
item --gap Destroy
item dban DBAN Darik's Boot And Nuke 2.3.0
item --gap --
item return <---
choose --default bootlocal --timeout 60000 target && goto ${target}
:bootlocal
sanboot --no-describe --drive 0x80 || goto MENU
:acronis2014
initrd http://${fog-ip}/iso/acronis2014.iso
chain memdisk iso raw ||
goto MENU
:acronis2016
initrd http://${fog-ip}/iso/acronis2016.iso
chain memdisk iso raw ||
goto MENU
:acronis2017
initrd http://${fog-ip}/iso/acronis2017.iso
chain memdisk iso raw ||
goto MENU
:easeuspms
initrd http://${fog-ip}/iso/easeuspms.iso
chain memdisk iso raw ||
goto MENU
:aomeipau
initrd http://${fog-ip}/iso/aomeipau.iso
chain memdisk iso raw ||
goto MENU
:veeam
initrd http://${fog-ip}/iso/veeam.iso
chain memdisk iso raw ||
goto MENU
:erd2005
initrd http://${fog-ip}/iso/erd2005.iso
chain memdisk iso raw ||
goto MENU
:dart7
initrd http://${fog-ip}/iso/dart7.iso
chain memdisk iso raw ||
goto MENU
:dart8
initrd http://${fog-ip}/iso/dart8.iso
chain memdisk iso raw ||
goto MENU
:dart81
initrd http://${fog-ip}/iso/dart81.iso
chain memdisk iso raw ||
goto MENU
:dart10
initrd http://${fog-ip}/iso/dart10.iso
chain memdisk iso raw ||
goto MENU
:dban
initrd http://${fog-ip}/iso/dban_2.3.0.iso
chain memdisk iso raw ||
goto MENU
:shell
shell ||
goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU
autoboot

[Wayne Workman]

@x23piracy #wiki worthy

[Arrowtron]

@wayne-workman @Sebastian-Roth

http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke --method quick" silent vga=785
${boot-ip}/dban/dban.bzi nuke="dwipe --autonuke --method quick" silent vga=785

Both give me this error message pretty much

dban.bzi and other files are defiantly listed under - http://awh-wc-fog/fog/dban/
’

Here is the tcpdump @Sebastian-Roth
https://www.dropbox.com/s/j8x6y88m1bickbp/dban.pcap?dl=0

Thanks for your Advanced Menu @x23piracy. I tried to select a portion of the code to use but it didn’t work well
’
’

Ive placed this in the DBAN iPXE Menu item Parameters

:dban
initrd http://${fog-ip}/iso/dban_2.3.0.iso
chain memdisk iso raw ||

[Sebastian Roth]

@Arrowtron Sorry we all missed the kernel part of the command. Please try:

kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke --method quick" silent vga=785
boot || goto MENU

or

kernel ${boot-url}/dban/dban.bzi nuke="dwipe --autonuke --method quick" silent vga=785
boot || goto MENU

What x23piracy posted is also valid but doing it a different way. It boots the ISO without mounting/extracting it first. This does work for some ISOs but causes trouble with others. So this might work but I haven’t tried it myself:

initrd http://${fog-ip}/iso/dban_2.3.0.iso
chain memdisk iso raw || goto MENU

But you need to have the DBAN ISO file in the right place for this as well, /var/www/iso/dban_2.3.0.iso (where /var/www/html/iso/dban_2.3.0.iso does not work in recent FOG versions because of the API redirecting but maybe you’ve switched that off anyway)…

And sorry about the confusion from what is written about DBAN in the wiki!! We need to correct this soon!

[Arrowtron]

@sebastian-roth said in DBAN FOG Boot Menu:

kernel ${boot-url}/dban/dban.bzi nuke=“dwipe --autonuke --method quick” silent vga=785
boot || goto MENU

Ah of course!
I have tried all the commands above and this one worked well!

kernel ${boot-url}/dban/dban.bzi nuke="dwipe --autonuke --method quick" silent vga=785
boot || goto MENU

Yes may need to update the Wiki! Thanks for your replies and assistance!

[Wayne Workman]

@sebastian-roth Am I correct in my understanding that the only difference here is the ISO needs mounted to /var/www instead of /var/www/html ?

[Sebastian Roth]

@Wayne-Workman There were other issues like missing kernel command and incorrect variable name as well. Though in current FOG versions you cannot put stuff in /var/www anywhere you like because of our redirect configuration. When you turn on redirect engine debug logging you can see why. I remember having had a first unsuccessful go with trying to come up with a different redirect/rewrite config that works for the API but still allows you to have files pretty much anywhere in /var/www…