Have some problems with dban
-
@loktar Is this machine set to UEFI or legacy BIOS? DBAN is not working on UEFI machines.
-
@Sebastian-Roth its set to legacy.
-
@loktar Then please post the exact iPXE config you use to boot that DBAN iso…
-
@sebastian-roth
I have tried to mount the image both to /var/www/html/dban and /var/www/dbanMenu item: DBAN
Parameters: :DBAN kernel ${boot_url}/dban/dban.bzi nuke=“dwipe --autonuke” silent vga=785 bootthis is the files located x.x.x.x/dban/
about.txt
dban.bzi
isolinux.bin
isolinux.cat
isolinux.cfg
quick.txt
raid.txt
warning.txtdownloaded : http://downloads.sourceforge.net/project/dban/dban/dban-2.3.0/dban-2.3.0_i586.iso
-
@loktar Parameters should be as seen in the forums thread you initially posted:
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
Don’t mount in
/var/www/html/dban
but use/var/www/dban
instead!Have you double checked the hashsum after downloading the ISO file? Maybe the download was canceled.
-
@sebastian-roth This is what happens everythime I run the paramater.
Tried both settings and checked hash, hash is correct. I feel there is something strange happening, becouse after running dban… as seen above it just boot right back into:
I have no idea why. Its probably something obvious I missed somewhere, but I cant find out where or what it is. -
@loktar So can you download that file when you open the URL http://192.168.20.2/fog/dban/dban.bzi ??
And what that URL. The parameters I posted say:http://${fog-ip}/dban/dban.bzi
. Please post a picture of your iPXE menu settings for this entry. I kind of feel that you have something missing there. You see those commands I posted are not in one line but it’s actually two lines of code!!kernel .... boot ...
It wouldn’t work if you have:
kernel .... boot
-
@sebastian-roth
Please see: https://pastebin.com/LFzQhtwB its the complete ipxe.
I cannot download the file, it just redirect me to x.x.x.x/fog/management immediately.I got a new error now.
This is the pic for iPXE meny settings:
I really appriciate you helping me. Thanks alot!
-
@loktar Well, you now have used
${fog+ip}
instead of${fog-ip}
…No idea where you got that from.
-
@sebastian-roth
I tried a few things just before I sent you. I am sorry for that typo, fixed now. The error is stille the same though. -
@loktar Well then we need the big hammer to figure out what’s wrong here. Please boot up the client to the menu and move the cursor to the dban entry but don’t hit ENTER yet.
Go to your FOG server, open a terminal/SSH connection and run the following commands:sudo apt-get install tcpdump sudo tcpdump -w /tmp/dban.pcap host x.x.x.x
Replace
x.x.x.x
with the client IP address! The tcpdump command will print one line and then just sit there waiting. Now hit ENTER on the client to try and boot into DBAN. When you get back to the menu just stop tcpdump (Ctrl+C), upload that file/tmp/dban.pcap
to your dropbox/google drive and post a link here. -
-
@loktar The PCAP tells us what’s wrong:
GET /dban/dban.bzi HTTP/1.1 Connection: keep-alive User-Agent: iPXE/1.0.0+ (64865) Host: 192.168.20.2 HTTP/1.1 302 Found Date: Fri, 06 Oct 2017 07:16:32 GMT Server: Apache/2.4.27 (Ubuntu) Location: http://192.168.20.2/fog/management/index.php
Not sure if you can “read” HTTP header information. The first block is the client request from your PC. and the second block is the answer. Well, it does redirect the client to the web UI management interface. This is most probably happening because you have the ISO mounted in the “wrong” place. Please run the command
mount
on your FOG server and post output here. -
@sebastian-roth
Sorry for the late reply, here is the mount.edit: It worked now, I reinstalled Ubuntu and fog and followed all the tips/steps you have given me and now it works!
I still cannot list x.x.x.x/dban For some reason. It still redirects.
-
@loktar said in Have some problems with dban:
I still cannot list x.x.x.x/dban For some reason. It still redirects.
That’s ok. Just the way our redirecting works right now. It’s on my list to fix but … can’t do it all at once. But you should be able to access the file through URL directly. Just no directory listing possible!
Great you got it working now. Marking this solved.