Use Clonezilla’s
savedisk or
saveparts image to restore your partition table and data by booting from a live USB, selecting the device mode, choosing the correct backup source, and confirming the overwrite operation. This process rebuilds the disk structure exactly as it was during the backup, ensuring your Linux system partitions are restored with their original layout and file systems intact.
Preparing for Restoration
Before initiating any restoration procedure, you must ensure that the target drive is completely disconnected from any other operating systems or mounted volumes that might interfere with the write operations. Clonezilla operates at a low level, and having multiple drives connected can lead to accidental overwrites of the wrong device. Create a bootable Clonezilla Live USB using tools like Rufus on Windows or
dd on Linux. When creating the media, select the "iso" mode if you want to preserve the ISO checksums, or "image-zip" for smaller storage requirements. Verify the integrity of the backup files before starting; if the backup was stored on an external USB drive, ensure it is connected and recognized by the BIOS/UEFI firmware. It is critical to identify the exact device name (e.g.,
/dev/sda) of the drive you intend to restore. Misidentifying this device can result in catastrophic data loss on a different disk. You can use the
lsblk command in a temporary Linux environment to verify capacities and names if needed, but do not mount any partitions on the target drive during preparation.
Booting into Clonezilla Live
Insert the prepared Clonezilla Live USB into the computer and restart the machine. Access the boot menu by pressing the appropriate key (commonly F12, F9, or Esc depending on the motherboard manufacturer) or enter the BIOS/UEFI settings to change the boot order. Select the USB drive from the list of bootable devices. Once the Clonezilla Live environment loads, you will be presented with a text-based menu. Choose the default option, which is typically "Start_Clonezilla," to proceed to the language selection screen. Select your preferred language and keyboard layout. The next step involves choosing between local or remote backup storage. If your backup resides on a local external hard drive or USB stick, select "local_dev." If the backup is stored on a network server via SSHFS, NFS, or Samba, choose the corresponding remote option and configure the connection details accordingly. For most users restoring a single machine, "local_dev" is the standard choice. Ensure the backup drive is visible in the file browser that appears after selecting the storage type.
Selecting the Correct Restore Mode
Clonezilla offers several modes, but only two are relevant for full partition recovery:
savedisk and
saveparts. The
savedisk option restores the entire disk, including the Master Boot Record (MBR) or GUID Partition Table (GPT), all partitions, and the data within them. This is the recommended method if you want an exact bit-for-bit replica of the original state. The
saveparts option restores only the selected partitions, leaving the existing partition table intact. Use this only if you have manually recreated the partition layout and only need to recover the data inside specific partitions. In almost all cases where the partition table itself is corrupted or lost,
savedisk is the necessary choice. Select
savedisk and confirm that you understand the risks. You will then be asked to choose the device to restore. Carefully select the target hard drive from the list. Double-check the size and model name to avoid selecting the wrong disk. If you previously used
saveparts, you must select
saveparts here as well; mismatching these modes can cause errors.
Executing the Restoration
After selecting the target device, Clonezilla will display a summary of the operation. It will show the source backup directory and the destination disk. Read this information carefully. If everything matches your expectations, select "Yes" to proceed. The restoration process will begin, displaying progress bars and status messages. Do not interrupt this process. Power outages or forced reboots during this phase can corrupt both the source backup and the target drive. The time required depends on the speed of the USB interface and the amount of data being written. Once the process completes, Clonezilla will prompt you to reboot. Remove the USB drive before restarting to prevent the system from booting back into Clonezilla. Upon reboot, the system should load the restored partition table and file systems. If you restored a GPT partition table, ensure that Secure Boot is disabled or configured correctly, as some older backups may contain signatures that conflict with strict Secure Boot policies.
Troubleshooting Common Issues
If the system fails to boot after restoration, check the BIOS boot priority to ensure the internal drive is selected. Sometimes, the UUIDs of the partitions change if the disk geometry differs significantly, though
savedisk usually preserves them. If you encounter errors regarding "device busy," ensure no other processes are accessing the disk. Refer to related guides such as
Ubuntu Hard Disk Mounted with No Partitions if the drive appears empty after restoration, as this may indicate a deeper filesystem corruption rather than a partition table issue. Additionally, consult
File System Unknown after decryption with Veracrypt Rescue Disk if your partitions were encrypted, as encryption keys must be available to access the data even after the partition structure is restored.
Frequently Asked Questions
Can I restore a Clonezilla backup to a larger drive?
Yes, Clonezilla can restore to a larger drive, but the partition sizes will remain identical to the source unless you manually resize them afterward. You will need to use tools like
gparted or
resize2fs to expand the partitions into the new free space. Restoring to a smaller drive is not possible if the source data exceeds the target capacity.
What happens if I select saveparts instead of savedisk?
Selecting
saveparts will only overwrite the data within the specified partitions and will not touch the partition table. If your partition table is corrupted, this method will fail to fix the underlying structure issues. Always use
savedisk when the goal is to recover the entire disk layout.
Does Clonezilla preserve UUIDs during restoration?
Yes, Clonezilla preserves the UUIDs of the partitions during a
savedisk operation. This ensures that boot loaders and fstab entries continue to work without modification. However, if you restore to a new drive and the UUIDs conflict with another connected drive, you may need to update your boot configuration.
Is it safe to restore while the OS is running?
No, you must never attempt to restore a Clonezilla backup while the operating system is running on the target drive. Clonezilla requires exclusive access to the block devices. Attempting to restore over a mounted partition can lead to severe data corruption and system instability.
How do I verify the backup integrity before restoring?
You can verify the integrity of a Clonezilla backup by checking the md5sum or sha1sum files included in the backup directory. These checksums allow you to compare the current state of the backup files against the originals to ensure no data corruption occurred during storage or transfer.