How to use dd in Linux without destroying your disk

Safely and reliably make perfect copies of drives, partitions, and filesystems with the Linux dd tool.
286 readers like this.
Perl tricks for system administrators

This article is excerpted from chapter 4 of Linux in Action, published by Manning.

Whether you're trying to rescue data from a dying storage drive, backing up archives to remote storage, or making a perfect copy of an active partition somewhere else, you'll need to know how to safely and reliably copy drives and filesystems. Fortunately, dd is a simple and powerful image-copying tool that's been around, well, pretty much forever. And in all that time, nothing's come along that does the job better.

Making perfect copies of drives and partitions

There's all kinds of stuff you can do with dd if you research hard enough, but where it shines is in the ways it lets you play with partitions. You can, of course, use tar or even scp to replicate entire filesystems by copying the files from one computer and then pasting them as-is on top of a fresh Linux install on another computer. But, because those filesystem archives aren't complete images, they'll require a running host OS at both ends to serve as a base.

Using dd, on the other hand, can make perfect byte-for-byte images of, well, just about anything digital. But before you start flinging partitions from one end of the earth to the other, I should mention that there's some truth to that old Unix admin joke: "dd stands for disk destroyer." If you type even one wrong character in a dd command, you can instantly and permanently wipe out an entire drive of valuable data. And yes, spelling counts.

Remember: Before pressing that Enter key to invoke dd, pause and think very carefully!

Basic dd operations

Now that you've been suitably warned, we'll start with something straightforward. Suppose you want to create an exact image of an entire disk of data that's been designated as /dev/sda. You've plugged in an empty drive (ideally having the same capacity as your /dev/sda system). The syntax is simple: if= defines the source drive and of= defines the file or location where you want your data saved:

# dd if=/dev/sda of=/dev/sdb

The next example will create an .img archive of the /dev/sda drive and save it to the home directory of your user account:

# dd if=/dev/sda of=/home/username/sdadisk.img

Those commands created images of entire drives. You could also focus on a single partition from a drive. The next example does that and also uses bs to set the number of bytes to copy at a single time (4,096, in this case). Playing with the bs value can have an impact on the overall speed of a dd operation, although the ideal setting will depend on your hardware profile and other considerations.

# dd if=/dev/sda2 of=/home/username/partition2.img bs=4096

Restoring is simple: Effectively, you reverse the values of if and of. In this case, if= takes the image you want to restore, and of= takes the target drive to which you want to write the image:

# dd if=sdadisk.img of=/dev/sdb

You can also perform both the create and copy operations in one command. This example, for instance, will create a compressed image of a remote drive using SSH and save the resulting archive to your local machine:

# ssh username@ "dd if=/dev/sda | gzip -1 -" | dd of=backup.gz

You should always test your archives to confirm they're working. If it's a boot drive you've created, stick it into a computer and see if it launches as expected. If it's a normal data partition, mount it to make sure the files both exist and are appropriately accessible.

Wiping disks with dd

Years ago, I had a friend who was responsible for security at his government's overseas embassies. He once told me that each embassy under his watch was provided with an official government-issue hammer. Why? In case the facility was ever at risk of being overrun by unfriendlies, the hammer was to be used to destroy all their hard drives.

What's that? Why not just delete the data? You're kidding, right? Everyone knows that deleting files containing sensitive data from storage devices doesn't actually remove the data. Given enough time and motivation, nearly anything can be retrieved from virtually any digital media, with the possible exception of the ones that have been well and properly hammered.

You can, however, use dd to make it a whole lot more difficult for the bad guys to get at your old data. This command will spend some time writing millions and millions of zeros over every nook and cranny of the /dev/sda1 partition:

# dd if=/dev/zero of=/dev/sda1

But it gets better. Using /dev/urandom file as your source, you can write over a disk with random characters:

# dd if=/dev/urandom of=/dev/sda1

Monitoring dd operations

Since disk or partition archiving can take a very long time, you might want to add a progress monitor to your command. Install Pipe Viewer (sudo apt install pv on Ubuntu) and insert it into dd. With pv, that last command might look something like this:

# dd if=/dev/urandom | pv | dd of=/dev/sda1
4,14MB 0:00:05 [ 98kB/s] [      <=>                  ]

Putting off backups and disk management? With dd, you aren't left with too many excuses. It's really not difficult, but be careful. Good luck!

David Clinton
DAVID CLINTON is a system administrator, teacher, and writer. He has administered, written about, and created training material for many important technology subjects including Linux systems, cloud computing (AWS in particular), and container technologies like Docker.


Instead of using Pipe Viewer I use the "status=progress" command line option of dd to monitor the progress.

"And in all that time, nothing's come along that does the job better"

I guess it's subjective, but I actually consider GNU ddrescue ( and dd_rescue ( to be better tools than plain dd.

I'm more familiar with GNU ddrescue, but both use a more sensible default block size than dd, keep going in case of errors, show progress and warn you if you try to overwrite a disk or partition.

And, if you prefer something more visual, there's Clonezilla (

That said, since I usually stick to dd because it's installed in most of our systems by default, I'd like to share a trick: if you already launched dd and don't want to stop it and launch it again with pv, you can make it tell you how far it is running from a different console 'kill -USR1 $(pidof dd)'.


Good point about status=progress - I hadn't been aware of that.

The status=progress is only on newer versions of dd. On older distributions, that option does not exist.

Any special considerations for LVM volumes? Thanks.

And of course there's the count= option as well. Handy for blowing away partition tables on a drive that has previously been part of a raid array, or are of a format that linux can't recognise.

dd bs=512 if=/dev/zero count=4 of=/dev/sdb

Back in the day, we used to use dd as the output pipe for tar or cpio when backing up to tape. Streaming tapes like a continuous stream of data, and tar, cpio and the like don't do this nicely when there's a lot of small files.
This would cause the tape drive to "shoeshine" the tape heads, as it needed to stop the tape, rewind and get a running start each time the data stream ran dry. (Not good for either the drive or the tapes due to wear and stretching.)

cpio -ov --format=crc

Rats! the command line above got chopped off as it had a less than redirection symbol, sanitising the input.

cpio -ov --format=crc (less than symbol here)/tmp/dumplist | dd obs=128k of=/dev/st0

I hope this gets though.

Strongly recommend mounting the disks you're wanting to backup as READ ONLY before performing this command. Otherwise you may potentially end up with a lot of files in the lost and found within your backups as it's running (due to sync operations)

Strongly recommend adding

mount -o ro,remount /dev/partitionwhateveryouwanttobackup


home can not be on the same device (sda)

# dd if=/dev/sda of=/home/username/sdadisk.img

That's a good point. However the current root device isn't necessarily sda. I've had workstations where, for various reasons, the root was sdb or even higher.

In reply to by Jalal

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.