Comandos Linux

Salviano A. Leo
21/12/2013

Sumrio
1 Introduo

2 Usando o partclone

3 Using dd
3.1 Cloning a partition . . . . .
3.2 Cloning an entire hard disk
3.3 Backing up the MBR . . . .
3.4 Create disk image . . . . . .
3.5 Restore system . . . . . . .
3.6 Examples with compression

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

2
3
3
4
4
5
5

4 Using cp

5 Disk cloning software

Introduo

Neste tutorial pretende-se mostrar como fazer o backup de uma partio usando a linha de
comando. Primeiro, no se deve esquecer de verificar a partio para depois fazer o backup.
Tanto para verificar como para fazer um backup necessrio que a partio no esteja montada.
Neste caso usa-se um live CD que contenha os programas necessrio, ou faz-se um pen-drive
bootvel para tal fim. O que ser dito a seguir, supe-se que o sistema foi inicializado por
um live CD ou pen-drive. Note que em um pen-drive, co espao suficiente possvel instalar
os softwares que voc no tem, enquanto no live CD isso no possvel. Se estiver usando
um pen-drive com uma distribuio baseada no debian, ento, por exemplo, para instalar o
partclone digite:
> sudo apt - get install partclone

em seguida voc ter o partclone disponvel.

Antes de iniciar o processo de backup necessrio identificar a partio e para isso, pode-se
usar um software grfico com o gparted ou via linha de comando o software fdisk, da seguinte
forma
> sudo fdisk -l

ou usando o comando com recursos mais avanados cfdisk

> sudo cfdisk

Ento, identifica-se a partio a ser clonada, aqui ser considerado nos exemplos que ser a
partio /dev/sda1.
Para clonar a partio /dev/sda1 formatada com ext4, aconselhvel, primeiro verificar o
estado da partio com
> sudo e2fsck -f -y -v / dev / sda1

No se esquea de mudar a partio /dev/sda1 para a partio que se deseja fazer uma cpia
de segurana, um backup.

Usando o partclone

Usando o partclone para clonar a partio /dev/sda1 formatada com ext4 sem compresso.
Para fazer uma cpia de segurana da partio sem comprimir a imagem criada, e salvar no
arquivo /path/image_sda1.pcl faa:
> partclone . ext4 -c -s / dev / sda1 -o / path / image_sda1 . pcl

Para restaurar digite:

> sudo partclone . ext4 -r -s / path / image_sda1 . pcl -o / dev / sda1

Para realizar o mesmo procedimento com compresso da imagem gerada faa:

> partclone . ext4 -c -s / dev / sda1 | gzip -c > / path / image_sda1 . pcl . gz

Note que para se obter uma compresso mxima use a opo: "gzip -c9".
Para restaurar a partio digite:
> zcat / path / image_sda1 . pcl . gz | sudo partclone . ext4 -r -o / dev / sda1

Note que o partclone necessita se chamado com os privilgios do usurio root, no ubuntu
e variantes use o sudo.

Using dd

The dd command is a simple, yet versatile and powerful tool. It can be used to copy from
source to destination, block-by-block, regardless of their filesystem types or operating systems.
A convenient method is to use dd from a live environment, as in a livecd. Warning:
This paragraph used to contain several errors that misrepresented the inner workings of
the dd command. I tried to fix them, but YMMV.

 As with any command of this type, you should be very cautious when using it; it can
destroy data. Remember the order of input file (if=) and output file (of=) and do not
reverse them! Always ensure that the destination drive or partition (of=) is of equal or
greater size than the source (if=).

3.1

Cloning a partition

From physical disk /dev/sda, partition 1, to physical disk /dev/sdb, partition 1.

# dd if =/ dev / sda1 of =/ dev / sdb1 bs =512 conv = noerror , sync

Warning: If output file of= (sdb1 in the example) does not exist, dd will create a file with
this name and will start filling up your root file system.

3.2

Cloning an entire hard disk

From physical disk /dev/sdX to physical disk /dev/sdY

# dd if =/ dev / sdX of =/ dev / sdY bs =512 conv = noerror , sync

This will clone the entire drive, including MBR (and therefore bootloader), all partitions,
UUIDs, and data.
noerror instructs dd to continue operation, ignoring all read errors. Default behavior for
dd is to halt at any error.
sync fills input blocks with zeroes if there were any read errors, so data offsets stay in
sync.
bs=512 sets the block size to 512 bytes, the "classic"block size for hard drives. If and
only if your hard drives have a 4K block size, you may use "4096"instead of "512". Also,
please read the warning below, because there is more to this than just "block sizes- it also
influences how read errors propagate.
Warning: The block size you specify influences how read errors are handled. Read below.
The dd utility technically has an "input block size"(IBS) and an "output block size"(OBS).
When you set bs, you effectively set both IBS and OBS. Normally, if your block size is, say,
1M, dd will read 1M bytes and write 1M bytes. But if a read error occurs, things will go
wrong. Many people seem to think that dd will "fill up read errors with zeroes"if you use the
noerror,sync options, but this is not what happens. dd will, according to documentation, fill
up the OBS to IBS size, which means adding zeroes at the end of the block. This means, for a
disk, that effectively the whole 1M would become messed up because of a single 512 byte read
error in the beginning of the read: ERROR6789 would become 678900000 instead of 000006789.
If you are positive that your disk does not contain any errors, you could proceed using
a larger block size, which will increase the speed of your copying manifold. For example,
changing bs from 512 to 64K changed copying speed from 35MB/s to 120MB/s on a simple
Celeron 2.7GHz system. But keep in mind, that read errors on the source disk will end up as
block errors on the destination disk, i.e. a single 512 bytes read error will mess up the whole
64k output block. Tip: If you would like to view dd progressing, you can send it a USR1 signal.
pidof dd will tell you the PID of dd, then use kill -USR1. In one line: kill -USR1 $(pidof dd).
Note:
3

 To regain unique UUIDs of an Ext2/3/4 filesystem, use tune2fs /dev/sdXY -U random

on every partitions.
Partition table changes from dd are not registered by the kernel. To notify of changes
without rebooting, use a utility like partprobe (part of GNU parted).

3.3

Backing up the MBR

The MBR is stored in the the first 512 bytes of the disk. It consist of 3 parts:
1.) The first 446 bytes contain the boot loader.
2.) The next 64 bytes contain the partition table (4 entries of 16 bytes each, one entry for each
primary partition).
3.) The last 2 bytes contain an identifier
To save the MBR into the file "mbr.img":
# dd if =/ dev / sdX of =/ path / to / mbr_file . img bs =512 count =1

To restore (be careful: this could destroy your existing partition table and with it access to
all data on the disk):
# dd if =/ path / to / mbr_file . img of =/ dev / sdX

If you only want to restore the boot loader, but not the primary partition table entries, just
restore the first 446 bytes of the MBR:
# dd if =/ path / to / mbr_file . img of =/ dev / sdX bs =446 count =1

To restore only the partition table, one must use

# dd if =/ path / to / mbr_file . img of =/ dev / sdX bs =1 skip =446 count =64

You can also get the MBR from a full dd disk image.
# dd if =/ path / to / disk . img of =/ path / to / mbr_file . img bs =512 count =1

3.4

Create disk image

1.) Boot from a liveCD or liveUSB.

2.) Make sure no partitions are mounted from the source hard drive.
3.) Mount the external HD.
4.) Backup the drive,
# dd if =/ dev / sdX conv = sync , noerror bs =64 K | gzip -c
img . gz

> / path / to / backup .-

If necessary (e.g. when the format of the external HD is FAT32) split the disk image in
volumes (see also split man pages).
# dd if =/ dev / sdX conv = sync , noerror bs =64 K | gzip -c | split - a3 - b2G - / path / to / backup . img . gz

5.) Save extra information about the drive geometry necessary in order to interpret the partition table stored within the image. The most important of which is the cylinder size.
# fdisk -l / dev / sdX > / path / to / list_fdisk . info

Note: You may wish to use a block size (bs=) that is equal to the amount of cache on
the HD you are backing up. For example, bs=8192K works for an 8MB cache. The 64K
mentioned in this article is better than the default bs=512 bytes, but it will run faster
with a larger bs=.

3.5

Restore system

To restore your system:

# gunzip -c / path / to / backup . img . gz | dd of =/ dev / sdX

When the image has been split, use the following instead:
# cat / path / to / backup . img . gz * | gunzip -c | dd of =/ dev / sdX

3.6

Examples with compression

When you need to create the hard drive or a single partition compressed backup image file you
must use compression tools which can do backup from a stdout and the dd command. Those
compressed files cannot be mounted by the mount command but are useful to know how to
create and restore them.
7zip Install the [32]p7zip package from the [33]official repositories. This backup example will
split the dd command output in the files by up to the 100 megabyte each:
# dd if =/ dev / sdXY | 7 z a - v100m - t7z - si image - file .7 z

Restore with 7zip:

# 7 z x - so

image - file .7 z | dd of =/ dev / sdXY

Note: 7zip can split only the 7z compression type files

Zip Install the [34]zip package from the [35]official repositories, which contains zipsplit among
other utilities for the management of zip archives. It will create a file with -"name inside
the image-file.zip file which will contain data from the dd command output. To make a
5

raw output of the file you can use the -cp option with unzip in stdout for the dd command.
Backup:
# dd if =/ dev / sdXY | zip -- compression - method bzip2 image - file . zip -

Restore:
# unzip - cp image - file . zip | dd of =/ dev / sdXY

The zip tool cannot split files on the fly but you can use the zipsplit utility on an already
created file.
See also man zip for more information.
Rar Install the [36]rar package from the [37]AUR. Warning: The rar examples were made
based on the manuals, please confirm!
This should do a backup and split the creating file on the fly in by up to 150 megabyte
files each.
# dd if =/ dev / sdXY | rar a - v150m - siimage - file . rar

This should restore

# unrar x -p image - file . rar | dd of =/ dev / sdXY

or you can use the rar instead of the [38]unrar utility. The unrar utility is available in
the official repositories and can be installed with pacman -S unrar.
Bzip2 Creation by using the dd is more safe and use to be error free:
# dd if =/ dev / sdXY | bzip2 - f5 > compressedfile . bzip2
937016+0 records in
937016+0 records out
479752192 bytes (480 MB ) copied , 94.7002 s , 5.1 MB / s

And a safe way of restoring with combination of the dd:

# bunzip2 - dc compressedfile . bzip2 | dd of =/ dev / sdXY

or
# bzcat compressedfile . bzip2 | dd of =/ dev / sdXY

Warning: Never ever use the bzip2 -kdc imgage.bzip2 > /dev/sdXY and bzip2 -kc /dev/sdXY >
methods for serious backup of partitions and disks. The errors might be due the end of
the device or partition and the restore process gives also errors due the truncated end.

Using cp

The cp program can be used to clone a disk, one partition at a time. An advantage to using
cp is that the filesystem type of the destination partition(s) may be the same or different than
the source. For safety, perform the process from a live environment. Note: This method should
not be considered in the same category as disk cloning on the level at which dd operates. Also,
it has been reported that even with the -a flag, some extended attributes may not be copied.
For better results, rsync or tar should be used.
The basic procedure from a live environment will be:
Create the new destination partition(s) using fdisk, cfdisk or other tools available in the
live environment.
Create a filesystem on each of the newly created partitions.
Example:
# mkfs -t ext3 / dev / sdXY

Mount the source and destination partitions. Example:

# mount -t ext3 / dev / sdXY / mnt / source
# mount -t ext3 / dev / sdZY / mnt / destination

Copy the files from the source partition to the destination

# cp -a / path / to / source /* / path / to / destination
-a : preserve all attributes , never follow symbolic links and copy
recursively

Change the mount points of the newly cloned partitions in /etc/fstab accordingly
Finally, install the GRUB bootloader if necessary. (See [39]GRUB)

Disk cloning software

Partclone provides utilities to save and restore used blocks on a partition and supports
ext2, ext3, ext4, hfs+, reiserfs, reiser4, btrfs, vmfs3, vmfs5, xfs, jfs, ufs, ntfs, fat(12/16/32)
and exfat. Optionally, a ncurses interface can be used. Partclone is available in the
community repository.
Partimage, an ncurses program, is available in the community repos. Partimage does not
currently support ext4 or btrfs filesystems. NTFS is experimental.
PartedMagic has a very nice live cd/usb with PartImage and other recovery tools.
Mindi is a linux distribution specifically for disk clone backup. It comes with its own
cloning program, Mondo Rescue.
7

 Acronis True Image is a commercial disk cloner for Windows. It allows you to create a
live (from within Windows), so you do not need a working Windows install on the actual
machine to use it. After registration of the Acronis software on their website, you will
be able to download a Linux based Live cd and/or plugins for BartPE for creation of the
Windows based live cd. It can also create a WinPE Live CD based on Windows. The
created ISO Live CD image by Acronis doesnt have the hybrid boot ability and cannot
be written to USB storage as a raw file.
FSArchiver allows you to save the contents of a file system to a compressed archive file.
Can be found on the System Rescue CD.
Clonezilla is an enhanced partition imager which can also restore entire disks as well as
partitions. Clonezilla is included on the Arch Linux installation media.
Redo Backup and Recovery is a Live CD featuring a graphical front-end to partclone.