Clonezilla Restore Disk Image Guide: Restore a Backup Image to a Target Drive

Tue, 23 Jun 2026 15:50:48 +0800

Clonezilla Live can restore a previously saved disk image to a drive. The official example restores the image bookworm-2023-10-15-03-img, stored on the second disk sdb, to the first disk sda.

Official document: https://clonezilla.org/fine-print-live-doc.php?path=clonezilla-live/doc/02_Restore_disk_image

This is useful for system recovery, batch deployment, lab rollback, or restoring a backup image to a new drive. Unlike copying files, restoredisk restores the full disk structure, including partition table, boot-related information, and partition data.

Confirm the risks first

Before restoring an image, confirm these points:

Data on the target disk will be overwritten.
The image files must be complete and readable.
The target disk should have enough capacity for the image.
The source image and target disk must not be confused.
For a system disk, BIOS/UEFI boot order may matter after restoration.

Clonezilla asks for confirmation twice before writing. Do not treat these confirmations as routine, especially when several disks or USB drives are connected.

Example scenario

The official example has two disks:

Device	Role
`sda`	Target disk, the first disk to be restored
`sdb`	Second disk that stores the Clonezilla image

The image directory is:

`1`	`bookworm-2023-10-15-03-img`

A Clonezilla image directory usually contains partition images, partition table data, disk information, hardware information, and metadata required for restore. The official example includes files such as sda-mbr, sda-gpt-1st, sda-gpt-2nd, sda1.vfat-ptcl-img.zst, and sda2.ext4-ptcl-img.zst.

Do not rename, move, or delete these files manually. When restoring, select the whole image directory, not a single compressed file.

Boot Clonezilla Live

Boot the machine with a Clonezilla Live USB drive, CD, or other boot media.

If needed, set USB or optical drive as the first boot device in BIOS/UEFI, or press the boot menu key during startup, such as Esc, F8, F9, or F12. The key varies by machine.

In the Clonezilla Live boot menu, the default 800x600 mode is usually enough. If display problems occur, try safe graphic settings. On a high-resolution display, the large-font mode may be easier to read.

Enter the restore flow

After booting, choose:

Select language.
Select keyboard layout. The default is fine for a US keyboard.
Choose Start Clonezilla.
Choose device-image.

device-image means backup or restore through image files, not direct disk-to-disk cloning. Disk-to-disk cloning uses device-device, so do not choose the wrong mode here.

Some Clonezilla menus require the space key for selection. The official document notes that when multiple choices are available, press Space; a selected item will show *.

Choose the image repository

Next, choose where the image is stored.

The official example chooses:

`1`	`local_dev`

local_dev is suitable when the image is on a second local disk, external drive, or USB drive. Clonezilla scans the local disks and partitions. If you have just inserted a USB drive or external disk, wait a few seconds for it to appear.

When the device appears in the scan list, press Ctrl-C to exit the scan report and continue.

If the image is not on a local device, you can choose other methods such as sshfs, samba, nfs, WebDAV, S3, or OpenStack Swift. For personal recovery work, local_dev is the most straightforward option.

Mount the partition that stores the image

The official example selects sdb1 as the image repository, meaning the first partition on the second disk.

Linux device names can be understood like this:

Name	Meaning
`sda`	First disk
`sda1`	First partition on the first disk
`sdb`	Second disk
`sdb1`	First partition on the second disk

If your image is on a USB drive or external disk, it may not be sdb1; it could be sdc1 or sdd1. Always judge by capacity, file system, and device model.

Clonezilla asks whether to check the file system before mounting the device. The official example skips it, but if you suspect the image disk has issues, checking first is safer.

Then choose the directory that contains the image. If the image is in the root of the partition, choose /, use Tab to select Done, and press Enter.

Choose restoredisk

After mounting the image repository, Clonezilla shows disk usage. Then choose:

`1`	`Beginner`

Then choose:

`1`	`restoredisk`

restoredisk restores a disk image to an entire drive. It is different from restoring a single partition and is suitable for full system disk recovery.

If you only want to restore one partition, do not choose restoredisk; choose the corresponding partition restore mode instead.

Select the image and target disk

First select the source image, such as:

`1`	`bookworm-2023-10-15-03-img`

Then select the target drive, such as:

sda

This is the most dangerous step. The source image is read. The target drive is overwritten.

Before confirming, check three times:

Is this the image you want to restore?
Is the target disk capacity and model correct?
Is there any unbacked-up data on the target disk?

Partition table and image integrity

Clonezilla asks how to create the partition table on the target disk.

The official document mentions two directions:

Use the partition table from the image.
Create the partition table proportionally on the target disk.

If the image was saved from a smaller disk and the target disk is larger, proportional creation may be convenient. But this affects the final partition layout, so do not change it casually if you are unsure.

Clonezilla also asks whether to check image integrity before restoring. The official document recommends checking the image because the directory existing does not prove that the image is intact.

If you are very sure the image is good, you can choose -scr to skip checking. For most recovery scenarios, checking first is better, especially when the image comes from an external drive, network storage, or old backup.

Start restoring

After confirming options, Clonezilla displays the restore command. This command is useful for custom Clonezilla Live media or repeatable deployment workflows.

If you chose to check the image, Clonezilla checks it first. After the check passes, it asks for confirmation twice before writing.

During restore, Clonezilla writes the image back to the target disk, usually including:

MBR and boot loader.
Partition table.
Data for each partition or logical volume.

Different file systems may be restored with different tools, such as partclone, ntfsclone, partimage, or dd. Ordinary users do not need to choose these manually; the important part is selecting the correct image and target disk.

What to do after completion

After restoration, Clonezilla lets you choose:

Power off.
Reboot.
Enter command line.
Start over.

If this is a system disk restore, it is usually safer to power off, remove the Clonezilla boot media and image disk, then boot from the target disk.

After booting, check:

Whether the system starts normally.
Whether partitions match expectations.
Whether important data exists.
Whether BIOS/UEFI boot entries point to the correct disk.

If the restored system does not boot, do not immediately redo everything. Check whether the boot mode is consistent, such as UEFI or Legacy BIOS, whether the target machine’s boot order is correct, and whether the ESP partition exists.

Short advice

When restoring a disk image with Clonezilla, remember this flow:

`1`	`device-image -> local_dev -> choose image repository -> Beginner -> restoredisk -> choose image -> choose target disk`

Spend your attention on:

Did you choose the correct image repository?
Did you choose the correct image directory?
Did you choose the correct target disk?
Should you check image integrity?
Has the target disk data been backed up?

Once these are confirmed, restoredisk becomes much safer.

System Recovery on KnightLi Blog