Difference between revisions of "Dd - Destroyer of Disks"
(→Image a drive)
|Line 72:||Line 72:|
dd if=/dev/sda of=disk_image bs=
dd if=/dev/sda of=disk_image bs=
Revision as of 11:32, 2 December 2008
These notes cover useful things you can do with `dd`.
- 1 Securely erase a drive
- 2 Erase MBR
- 3 Image a drive
- 4 Image a drive over a network
- 5 Show progress status statistics of `dd`
Securely erase a drive
This will destroy all data on a drive using `dd`. If you are in a hurry then just drill a hole through the top of case into the platters.
# faster to fill with zeros dd if=/dev/zero of=/dev/sda bs=1M # nearly ten times slower, pseudorandom data dd if=/dev/urandom of=/dev/sda bs=1M
Alternatively, you can do this:
# faster to fill with zeros cp /dev/zero /dev/sda # nearly ten times slower, pseduorandom data cp /dev/urandom /dev/sda
Tinfoil hat paranoia
It takes about 15 minutes to destroy a 1GB file using GNU `shred` (default options). It takes 30 seconds to destroy the file using 'dd if=/dev/zero of=somefile bs=1024 count=1M'. This is on a laptop with a 1.6Ghz dual core, 2GB RAM machine with a Seagate Momentus ST9160823AS laptop drive with ext3 filesystem -- in other words, nothing fancy.
Some people say that this isn't really secure because they heard that it's possible to read data that has been overwritten. This myth of the necessity for using multiple random overwrites for security came about because Dr. Peter Gutmann theorized that overwritten data could be recovered through the use of Scanning transmission electron microscopy. This is all theory -- no one has ever demonstrated this. No commercial data recovery or forensics firms offer any services that can recover overwritten data. Somehow this became accepted as fact and now everyone believes that supposedly the NSA and maybe space aliens can read overwritten bits on a drive. If your data is so sensitive that the government has to call the NSA or hire space aliens then you don't need my advice. Most drive erasure tools use very slow methods to prevent recovery of erased data. These tools overwrite each byte repeatedly with random data. This can take hours to erase a whole drive! Yet there is not a single example of overwritten data having ever been recovered using any exotic, theoretical method.
If you still prefer to use the GNU `shred` command then you may want to put this in your ~/.bashrc or alias file to make it a little more sane:
alias shred='shred --iterations=1'
One step disk wipe tool
This is useful if you want to reuse a lot of drives: Darik's Boot and Nuke
I had Linux with GRUB installed on a machine. I needed to get rid of it and put Windows on the machine. I used a Ghost recovery disk to restore Windows on it, but Ghost didn't restore the MBR. GRUB was still lurking in the Master Boot Record. On boot GRUB would try to start but would error out. Wiping out the MBR fixed the problem. This will wipe out the MBR of a disk (sda in this example) but keep the partition table and disk signature:
dd if=/dev/zero of=/dev/sda bs=440 count=1
It you also wish to totally erase the entire MBR include disk signature and partition table then use this:
dd if=/dev/zero of=/dev/sda bs=512 count=1
disk signature of boot disk
Disk signature is an obscure topic. These are the 4 bytes in the MBR starting after the first 440 bytes (offset 0x01B8 through 0x01BB). Often you can mess with it without problems, but in certain circumstances Linux may need to see a specific disk signature on the boot disk. The most critical fact is that the disk signature of the primary BOOT disk must be unique. In days past, I did not know the significance of the disk signature so I would often zero it out along with the MBR boot code using `dd if=/dev/zero of=/dev/sda bs=446 count=1`. That is not guaranteed to be harmless. It may cause problems; although, usually it is harmless. It is also bad to COPY a disk image including the MBR and then mount both copies on the same system. The system may not boot or nothing will go wrong at all!
Do not confuse disk signature with MBR signature. The MBR signature is always 0xAA55 starting at offset 0x01FE. It is stored little endian, so 0x01FE:0x55 and 0x01FF:0xAA.
The `ms-sys` command may be helpful in working with the MBR and disk signatures.
- Bios Enhanced Disk Drive Services (EDD) 3.0. This protocol determines which disk BIOS tries boot from. This uses the Disk Signature bytes. These are the 4 bytes in the MBR starting after the first 440 bytes (offset 0x01B8 through 0x01BB).
Image a drive
This is the most basic usage of `dd:
dd if=/dev/sda of=disk_image bs=1m
Image a CD-ROM to an iso file:
dd if=/dev/cdrom of=disk_image.iso
the following seems fancy, but what does this get you that the above example doesn't do?
isoinfo -d -i /dev/cdrom # Take Logical block size and Volume size from above and plug-in below: dd if=/dev/cdrom bs=2048 count=326239 conv=notrunc,noerror > disk_image.iso
Image a drive over a network
You can image a drive and have it stored directly on a remote server without touching a local disk. Here are two ways to do this.
Image a drive over a network with `dd` and `ssh`
I like this method better because this does it all from a single command on the sending side and the traffic is encrypted:
dd if=/dev/sda | gzip -c - | ssh firstname.lastname@example.org "dd of=disk_image.gz"
Image a drive over a network with `dd` and `nc` (netcat)
This example assumes the receiving machine's IP address is 192.168.1.100. I use port 2222 here, but you can use any port.
Start the receiving side first:
nc -l -p 2222 > disk_image.gz
Then start the sending side:
dd bs=1M if=/dev/sda | gzip -c - | nc 192.168.1.100 2222
If you are doing this on a live server you will need to unmount the drive or switch to single user mode (reboot and set single for boot option in GRUB) or you can boot from a live CD. If you boot into single user mode, don't forget to manually start the network. I have not done a lot of testing with copying a mounted disk in single user mode. This is not the ideal way, but it seems to work. It's better if the drive is not mounted.
Show progress status statistics of `dd`
Operations with `dd` can take a long time. Unfortunately, there is no command-line option to have `dd` print progress, but you can send the `dd` process a USR1 signal to have it print the progress statistics. For example, say you started `dd` and you know its PID is 15045. Example:
kill -USR1 15045
Here is a fancier example this will update every 10 seconds:
dd if=/dev/sda | gzip -c - | ssh email@example.com "dd of=disk_image.gz" & pid=$! while ps -p $pid > /dev/null; do kill -USR1 $pid; sleep 10; done