Clonezilla Disk-to-Disk Clone Guide: Clone a Small Drive to a Larger Drive

Tue, 23 Jun 2026 15:49:24 +0800

Clonezilla Live can clone one full drive to another. The official example clones a 20GB old drive to a 60GB new drive, which is a common case when upgrading to a larger SSD, migrating a system disk, or replacing an old drive.

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

The most important point comes first: back up important data before doing any disk clone, and check the source and target disks more than once. Clonezilla overwrites the target disk. Choosing the wrong disk can erase data directly.

What to prepare

You need:

A new drive with capacity equal to or larger than the old drive.
Clonezilla Live boot media, such as a USB drive, CD, or the temporary method from the official example where Clonezilla Live is placed on the new disk.
A disk enclosure or adapter cable if the new drive is connected externally.
A computer that can boot from USB or an external device.

The official example puts Clonezilla Live on the new drive and boots from it. The advantage is that no extra USB drive is needed. The downside is that this is a one-time setup: after cloning, the Clonezilla Live files on the new drive will be overwritten by the target system.

If you already have a Clonezilla Live USB drive, you can boot from that instead. The rest of the procedure is almost the same.

Why choose ToRAM

In the Clonezilla Live boot menu, the official example recommends choosing an option with ToRAM, such as:

`1`	`(VGA 800x600 & To RAM)`

or:

`1`	`(VGA with large font & To RAM)`

ToRAM copies Clonezilla Live files into memory and runs from there. This releases the partition used for booting, so it is not kept busy by running programs during the clone.

If you boot from a separate USB drive, ToRAM is not always required, but it is still a safe choice. On very old machines with little RAM, copying to memory may take longer or may not be suitable.

Basic workflow

After entering Clonezilla Live, the flow is roughly:

Choose a language.
Choose the keyboard layout. The default is fine for a US keyboard.
Choose Start Clonezilla.
Choose device-device.
Choose Beginner.
Choose disk_to_local_disk.
Select the source disk.
Select the target disk.
Choose whether to check the source file system.
Choose how to handle the target disk partition table.
Confirm and start cloning.

The key steps are step 7 and step 8. The source disk is the old disk you want to copy from. The target disk is the new disk that will be overwritten. In the official example, the source is sda and the target is sdb, but your machine may be different.

Do not rely only on names like sda and sdb. Check capacity, model, and connection type together. For example, if the old disk is 512GB and the new disk is 1TB, use both capacity and model information to confirm.

Space after cloning a small drive to a larger drive

By default, Clonezilla clones the source disk’s existing data and partition structure. The official document notes that it does not automatically expand all remaining space on the target disk.

For example, if the source disk is 20GB with 8GB used and the target disk is 60GB, Clonezilla will process the data and structure that correspond to the source disk. The remaining space on the target disk may not automatically become an available partition.

If you want the cloned system to use the whole larger disk directly, pay attention to the -k1 option. The official document says that if you want to use the full target disk size, choose -k1, whether you are in Beginner or Expert mode.

If you keep the default -k0, it usually preserves the original partition table structure. This is more conservative, but after cloning you may still need to expand the partition in the operating system or with a partition tool.

In short:

Goal	Suggestion
Copy the original disk structure safely	Keep the default partition table handling
Use the larger target disk space as much as possible	Pay attention to `-k1`
Not sure what to choose	Back up first, then follow the official screenshots step by step

The confirmations matter

Clonezilla asks for confirmation more than once before it starts writing. Do not just press Enter through these prompts.

Check again:

Is the source disk the old disk?
Is the target disk the new disk?
Is there anything on the target disk that still needs to be saved?
Are you ready for the target disk to be overwritten?

After confirmation, Clonezilla prepares a pseudo image of the source disk, creates the target disk partition table, and then writes data to the target disk. Depending on disk size, interface speed, and data volume, this may take minutes or hours.

What to do after cloning

When everything is done, Clonezilla asks whether to reboot, power off, or return to the command line. For system disk migration, powering off first is usually safer.

After shutdown:

Remove the old disk.
Install the new disk in the machine.
Boot from the new disk.
Check that the system starts normally and that partitions and data are present.

The official document also warns against booting with both the source disk and the cloned target disk in the same machine. The two disks may contain identical file system UUIDs, and the operating system can become confused and mount the wrong file system.

If you really need to connect both disks at the same time, first check boot order, then verify disk UUIDs, mount points, and partition state after boot.

Suitable scenarios

Clonezilla disk-to-disk cloning is suitable for:

Upgrading an old drive to a larger SSD.
Migrating a complete system disk.
Copying a system environment between machines of the same type.
Quickly duplicating disks in labs, machine rooms, or repair work.

It is not a good idea to run it blindly when you have no backup, the disk state is unclear, or the partition layout is complex. If BitLocker, LUKS, dynamic disks, RAID, dual boot, or multiple boot partitions are involved, check compatibility and recovery options first.

Short advice

For a normal Windows or Linux single-system disk migration, Clonezilla’s device-device and disk_to_local_disk flow is enough.

The risky parts are not the menus themselves, but these three things:

Back up important data.
Confirm the source and target disks.
Decide whether to use -k1 when cloning from a smaller drive to a larger one.

Once these are clear, following the Clonezilla Live steps becomes much safer.

Disk Cloning on KnightLi Blog