mauricevo

Version is actually clonezilla-live-2.7.1-22-amd64

https://sourceforge.net/p/clonezilla/bugs/356/

kernel of 2.7.0-10 doesn't immediately recognize changes to a partition table

What appears to be going on here is that after Clonezilla creates the partition table in the target disk, it informs the kernel, but the kernel (from Clonezilla's own boot iso) ignores this new info and the restore can't proceed. Simply rebooting and re-running the restore works because now the kernel sees the new partition table and Clonezilla apparently can see it's exactly what it will need for the restore. This looks to be a bug in the kernel that Clonezilla is currently using.

What appears to be going on here is that after Clonezilla creates the partition table in the target disk, it informs the kernel, but the kernel (from Clonezilla's own boot iso) ignores this new info and the restore can't proceed. Simply rebooting and re-running the restore works because now the kernel sees the new partition table and Clonezilla apparently can it's exactly what it will restore to. This looks to be a bug in the kernel that Clonezilla is currently using.

I am running Clonezilla 2.7.0-10 in a Parallels virtual machine as a test. I installed Windows 10 to a virtual machine. I then added a storage disk and cloned the Windows disk to the storage disk as an image. It tested all partitions as recoverable. I then removed the Windows disk and added an empty disk to recover to. I booted from Clonezilla and told it to restore the saved image to this disk. It failed with the error Unable to find target partition "nvme0n1p1". I am attaching the log.