I have 6 SATA HDDs connected to the server. Is there a way to dBan each disk individually. As of right now the controller creates a virtual drive and when the dBan is initialized it only wipes the virtual drive.
I am working on researching a project for work and thought that I would ask for your advice. I am trying to find out how to setup a PXE boot server within CentOS that would allow us to PXE boot a variety of system tools and utilities. Ideally it would also allow us to load ISO images and boot from them. Some of the things that we would like to have as boot time option from a PXE menu include the following:
- Darik's Boot and Nuke (DBAN)
- Memtest86
- Gparted
- Breakin
- Ubuntu ISO
- WinPE or BartPE
- Ultimate Boot CD
- Symantec Ghost CD
With this in mind, we would also like to have it setup such that there is a menu displayed (preferably with a background image that we can customize). On this menu there would be a default option that would boot the local hard drive and then an alternate set of choices for the technicians where they would have to enter a password to access the bootable resources - especially considering the destructive power of DBAN.
I was curious if there were any tips, tricks, how-tos, or walkthroughs that the community might point me in the direction of. This would be for a setup where the DHCP server already exists on the network and that the PXE server would not handle local DHCP requests. We would also need to make sure that the PXE server can handle PXE booting regular desktops, laptops, and virtual machines that exist within our VMWare cluster. Lastly, it would have to be a solution such that we can update the NIC drivers used for PXE booting since there is constantly new hardware released and our PXE server will need to support the newer devices as they are released.
Thank you in advance and I look forward to the ideas, thoughts, tips, and suggestions that you have to offer.
P.S. I should mention that we are a state funded higher education institution that does not have a lot of funding and the solutions presented will have to take that into consideration.
When people ask on how to wipe a drive, it almost seems as if the default answer is DBAN and I am not really sure why. Especially when doing commands like
dd if=/dev/zero of=/dev/sda
dd if=/dev/urandom of=/dev/sda
dcfldd pattern="00" of=/dev/sda
dcfldd pattern="FF" of=/dev/sda
shred /dev/sda
wipe /dev/sda
cat /dev/sda | cat > /dev/sda
etc
All of these will do the exact same thing and using a tool like hdparm to execute a secure-erase command will be much better than all of the above. Given that it will also erase those blocks on the glist,
So what makes Dban so good and so recommended. Is there a technical reason why it is recommended? To me it seems like a waste of bandwidth and a blank cd.