Clone from 512-byte NVMe to 4096-byte NVMe behind USB-C
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
I am trying to clone a WIN10 NVMe drive back to itself.
I did a savedisk to an image file with the drive installed in my laptop, which presents the device as having 512-byte sectors.
I want to restoredisk to the (same) drive installed in a WavLink NVMe-to-USBC enclosure, which (apparently) presents the drive as having 4096-byte sectors.
The restore goes along and then says
Target disk sdc does not exist in the image saved from disk(s) "nvme0n1". Creating a tmp Clonezilla image ... based on image "2021-01-25-14.img" so that we can restore the image ... (was saved from nvmen01) to sdc
This was puzzling (and a bit ominous) but I thought perhaps it might be saying "hey, the original disk had 512-byte sectors and the new one has 4096-byte sectors, so we need to twiddle some things."
The restore ultimately fails after
/dev/sdc1: Created a new partition of type "EFI System" and of size 2GiB
/dev/sdc2: Created a new partition of type "Microsoft reserved" and of size 128MiB
/dev/sdc3: The last usable GPT sector is 62514768, but 498069503 is requested.
Failed to add #3 partition
The first two sizes (2GiB and 128MiB) are 8x what they should be (in particular the original "Microsoft reserved" partition was just 16MiB) so I'm thinking clonezilla doesn't realize it needs to translate. I don't see an advanced option that seems relevant...
Maybe you can manually create the partition table on the destination disk, then restoring it without repartitioning it, i.e., choose the option "-k" in the expert mode:
https://clonezilla.org/clonezilla-live/doc/02_Restore_disk_image/images/ocs-09-advanced-param-k.png
BTW, please give the latest Clonezilla live a try, i.e., 2.7.1-22 or 20210127-groovy:
https://clonezilla.org/downloads.php
Steven
I restored to a 512G USB key in order to get the partition information and created partitions containing the same number of bytes (1/8 as many blocks or sectors or whatever it is fdisk -l reports) on the NVMe drive in the enclosure.
(The 512G USB key does not fully boot; I am told by a wizard this is probably because whatever is doing the booting doesn't incorporate USB drivers...)
Cloned with options -g auto -e1 auto -e2 -v -c -j2 -k (I think everything but -v and -k was the default.)
The NVMe drive will not attempt to boot :-( If I connect it to a booted Tumbleweed system Tumbleweed sees the NTFS partitions and their contents look reasonable
However, the EFI Boot Partition would not mount. I manually formatted it and copied the contents of the USB key's EFI Boot Partition. The NVMe drive still does not attempt to boot.
This is with Clonezilla live 2.7.0-10-amd64. Do you still think it worthwhile to try 2.7.1-22?
Last edit: Jonathan Edwards 2021-02-01
"Do you still think it worthwhile to try 2.7.1-22?" -> Maybe. We recommend to try the latest one, and if there are bugs and are always reproducible, it's easier for us to fix.
Steven