Linux DD Command - 15 Examples

With All Options

You wont find a more versatile utility than tar to create a file systembased backup.
In some cases, however, you dont need a backup based on a file system; instead,
you want to create a backup of a complete device or parts of it. This is where the dd
command comes in handy.

The Linux dd command is one of the most powerful utility which can be used in a
variety of ways. This tool is mainly used for copying and converting data, hence it
stands for data duplicator. This tool can be used for:

Backing up and restoring an entire hard drive or a partition.

Creating virtual filesystem and backup images of CD or DVDs called ISO files
Copy regions of raw device files like backing up MBR (master boot record).
Converting data formats like ASCII to EBCDIC.
Converting lowercase to uppercase and vice versa.

Only superuser can execute this command. You should be very careful while using
this command as improper usage may cause huge data loss. So, some people
consider this tool as data destroyer.

Syntax of dd command
The basic use of the dd command is rather easy because it takes just two
arguments: if= to specify the input file and of= to specify the output file. The
arguments to those options can be either files or block devices. I would, however,
not recommend using dd to copy files because cp does that in a much simpler way.
However, you can use it to clone a hard disk. The syntax is

ddif=<sourcefilename>of=<targetfilename>[Options]

We will learn the various options while going through the examples.
1. Backing up and restoring an entire
disk or a partition
It is possible to save all the data from an entire disk/partition to another disk/partition.
Not a simple copy as cp command but a block size copy.

a. Backup entire disk to disk

You can copy all the data (entire disk) from the disk /dev/sda to /dev/sdb . dd
doesnt know anything about the filesystem or partitions; it will just copy everything
from /dev/sda to /dev/sdb . You need to indicate the block size to be copied
at time with bs option. So, this will clone the disk with the same data on the same
partition.

#ddif=/dev/sdaof=/dev/sdbbs=4096conv=noerror,sync
97281+0recordsin
97280+0recordsout
99614720bytes(100MB)copied,2.75838s,36.1MB/s

This works only if the second device is as large as or larger than the first.
Otherwise, you get truncated and worthless partitions on the second one. Here, if
stands for input file , of stands for output file and bs stands for the block size
(number of bytes to be read/write at a time). Make sure you use block sizes in
multiples of 1024 bytes which is equal to 1KB. If you don't specify block size, dd use
a default block size of 512 bytes. The conv value parameter noerror allows the
tool to continue to copy the data even though it encounters any errors. The sync
option allows to use synchronized I/O.

b. Creating dd disk image (le image)

You can create an image of a disk or a file image. Backing up a disk to an image will
be faster than copying the exact data. Also, disk image makes the restoration much
easier.
 #ddif=/dev/sdaof=/tmp/sdadisk.img

You can store the output file where you want but you have to give a filename ending
with .img extension as above. Instead of /tmp/sdadisk.img , you could store
it for example at /sdadisk.img if you want.

c. Creating a compressed disk image

Because dd creates the exact content of an entire disk, it means that it takes too
much size. You can decide to compress the disk image with the command below

#ddif=/dev/vda|gzip
c>/tmp/vdadisk.img.gz

The pipe | operator makes the output on the left command become the input on the
right command. The -c option writes output on standard output and keeps original
files unchanged.

d. Backup a partition or clone one

partition to another
Instead of an entire disk, you can only backup a simple partition. You just need to
indicate the partition name in input file as below

#ddif=/dev/sda1of=/dev/sdb1bs=4096conv=noerror,sync

This will synchronize the partition /dev/sda1 to /dev/sdb1 . You must verify
that the size of /dev/sdb1 should be larger than /dev/sda1 . Or you can
create a partition image as below
 #ddif=/dev/sda1of=/tmp/sda1.img

e. Restoring a disk or a partition image

Save a disk or a partition helps to restore all the data if there is any problem with our
original drive. To restore, you need to inverse the input file with the output file
indicated during backup operation as below.

#ddif=/tmp/sdadisk.imgof=/dev/sda

You will retrieve data which were presents before the backup operation and not after
the operation

e. Restoring compressed image

As restoring disk partition, you can need to restore a compressed image. You need
to first indicate the compressed file and the output file which is the disk compressed
before.

#gzip
dc/tmp/vdadisk.img.gz|ddof=/dev/vda

The -d option here is to uncompress. Note the output file. You can mount the
restored disk to see the content. Note that you will data added after the last
compression backup operation.

2. Creating virtual lesystem and backup

images of CD or DVDs as iso les
You can need to create a virtual filesystem on Linux for some reasons as creating a
virtual machine on your Linux host. You can also need to create a backup iso image
of a CD or DVD

a. Creating a virtual lesystem

A virtual filesystem is a filesystem that exists in a file, which in turn exists on a
physical disk. You can need it to create for example an additional swap or loop
device or a virtual machine. We need /dev/zero which is a file used to create a
file with no data but with required size (a file with all zeros). In other words, this will
create a data file with all zeros in the file which will give the size to a file.

#ddif=/dev/zeroof=/filebs=1024Kcount=500
500+0recordsin
500+0recordsout
524288000bytes(524MB)copied,1.21755s,431MB/s

The option count refers to the number of input blocks to be copied. Combined
with block size value, it indicates the total size to copy. For example bs=1024k
and count=500 give a size=1024K*500 =524288000 bytes =524MB

Now let's check the size of our file

#ls
lh/file
rw
rr
1rootroot500MMay1718:57/file

You can see that we have our virtual filesystem created with the size indicated. You
can now use it to create loop device or a virtual disk or anything else.

b. Modify the rst 512 bytes of a le with

null data
If during the operation you indicate an existing output file, you will lose its data. For
some reasons, you can need to replace a block size of the output file.
 ddif=/dev/zeroof=file1bs=512count=1conv=notrunc

The notrunc option refers to do not truncate the file, only replace the first 512
bytes, if it exists. Otherwise, you will get a 512 byte file

c. Creating a backup iso image of CD or

DVD
You may wonder why not just copy the contents of your CD to a directory. How
would you handle the boot sector of a CD? You cant find that as a file on the device
because its just the first sector. Because dd copies sector by sector, on the other
hand, it will copy that information as well.

#ddif=/dev/cdromof=/mycd.iso

You need to know that you have to use the -o loop option, which allows you to
mount a file like any normal device. So, to mount /mycd.iso on the /mnt/cd
directory, do as below

#mount
oloop/mycd.iso/mnt/cd

3. Backing up and restoring MBR

The GRUB bootloader (https://linoxide.com/linux-how-to/set-grub-password/) is most
commonly stored in the MBR of the bootable drive. The MBR makes up the first 512
bytes of the disk, allowing up to 466 bytes of storage for the bootloader. The
additional space will be used to store the partition table for that drive. If MBR
gets corrupted, we will not be able to boot into Linux.

a. Backing up MBR
Because the MBR makes up the first 512 bytes of the disk, we just need to copy that
block size

#ddif=/dev/sdaof=/tmp/sdambr.imgbs=512count=1

With the count=1 and bs=512 , only 512 bytes will be copied which correspond
to the size of our MBR.

You can display the saved MBR with the od command which dump files in octal and
other formats as below

#od
xa/tmp/sdambr.img
0000000bf5281f48b66832d087d0f00e284
8000
R?tsohfvt
etx}bsnulsieotbnu
lnul
0000020ff7c740066461d8b8b66044d3166
b0c0
|delnultFfvtgsfvtMeotf1
@0

-a option selects named characters and -x selects hexadecimal 2-byte units

b. Backing up the boot data of MBR

excluding the partition table
The MBR 512 bytes data is located at the first sector of the hard disk. It consists of
446 bytes bootstrap, 64 bytes partition table and 2 bytes signature. It means that we
can exclude the partition table and bytes signature while backing up the MBR with
conserving only a block size equal to the bootstrap size.
 #ddif=/dev/sdaof=/tmp/sdambr2.imgbs=446count=1

c. Restoring MBR from MBR image

You can restore your MBR as shown on the previous commands with

#ddif=/tmp/sdambr.imgof=/dev/sda

3. Converting data formats

If an input file uses a character set that is not the native character set of the host
computer, the import operator must perform a conversion. For example, if ASCII is
the native format for strings on your host computer, but the input data file represents
strings using EBCDIC, you must convert EBCDIC to ASCII and vice versa.

a. Convert the data format of a le from

EBCDIC to ASCII
If theres an ebcdic file with you, mostly retrieved from mainframe systems, then, you
would like to convert them to ASCII for making modifications using text editors on
UNIX servers

#ddif=textfile.ebcdicof=textfile.asciiconv=ascii

The conv value parameter now is ascii because we convert from EBCDIC to
ASCII

b. Convert the data format of a le from

ASCII to EBCDIC
After modifying the ASCII version and once done, you may convert it back to
EBCDIC to be used by your application.

#ddif=textfile.asciiof=textfile.ebcdicconv=ebcdic

The conv value parameter now is ebcdic because we convert from ASCII to
EBCDIC. If youre just replacing particular number of bytes with an equivalent
number of bytes having different characters, the conversion would be smooth and
application reading the file should not have any issues.

4. Converting case of a le
dd command can be also used for an amazing thing. It can convert all text
(alphabets) in a file to upper or lower case and vice versa. For the example below,
we will have a file for the tests.

#catfile10
testddconvert

a. Converting a le to uppercase
Because our text file example is on lowercase, we will convert it to uppercase

#ddif=~/file10of=~/file20conv=ucase

The command will create the new file indicated. See that now conv option takes
ucase value. Let's check the result
After modifying the ASCII version and once done, you may convert it back to
EBCDIC to be used by your application.

#ddif=textfile.asciiof=textfile.ebcdicconv=ebcdic

The conv value parameter now is ebcdic because we convert from ASCII to
EBCDIC. If youre just replacing particular number of bytes with an equivalent
number of bytes having different characters, the conversion would be smooth and
application reading the file should not have any issues.

4. Converting case of a le
dd command can be also used for an amazing thing. It can convert all text
(alphabets) in a file to upper or lower case and vice versa. For the example below,
we will have a file for the tests.

#catfile10
testddconvert

a. Converting a le to uppercase
Because our text file example is on lowercase, we will convert it to uppercase

#ddif=~/file10of=~/file20conv=ucase

The command will create the new file indicated. See that now conv option takes
ucase value. Let's check the result
 #catfile20
TESTDDCONVERT

b. Converting a le to lowercase
Now we will do the reverse operation which will convert to lowercase

#ddif=~/file20of=~/file30conv=lcase

See that we use lcase of conv option to convert from upper case to lower case.

#catfile30
testddconvert

dd command does not convert the file names, only its content.

Conclusion
These are some examples of dd command usage. This data duplicator command
can be used in a lot more ways in your daily administration tasks. The dd command,
although not technically an archiving command, is similar in some ways because it
can copy an entire partition or disk into a file and vice versa.