panreyes

Well then, I don't know why did you need to do that, as the -ICDS parameter removes the optional LastLBA parameter, which actually was used by sfdisk to confirm that the target disk is as long as the disk.

Hi Nicolas! Did you try to do that in expert mode with the -ICDS parameter? It should solve that for you :)

Hello! I have not tried cloning Windows 10 enterprise yet, but I do it with Windows 10 Home and Pro very often without issues, except for OneDrive's cloud-only "pointer" files that get restored after OneDrive's syncs those again. Which options are you using in Clonezilla? Are you cloning or imaging?

No, I have only tried to clone a disk bigger than the target disk. Please tell me any other cases you may think of, so I will be able to test them. Still, afaik, that line just removes a second hard disk size comparison check that sfdisk realizes when importing a dump from another disk (the first check is the one that currently -icds skips), so in theory it should be safe :)

I think it may just fit in the -icds option, as it just removes the size of the origin disk in the partition table dump so it can be applied in a smaller target disk :)

Hi again Steven. I just tried the -k1 option, but it doesn't solve this case, at least when cloning NTFS partitions. I have a 64GB disk with a 20GB NTFS partition. If I try to clone it to a 21GB disk with -k1, Clonezilla creates a 6GB partition in the partition table, instead of 21GB, and outputs this message while cloning the partition: "target seek ERROR:Invalid argument" If my suggestion doesn't make any harm to other cases, it could be useful in cases like this one. We just used it again today...

I just tried again with the latest testing build and applying my little patch, and it worked for me perfectly. I used 2 disks: one of 64GB and one of 20GB. I created a 18GB NTFS partition in the 64GB disk and then I cloned it to the 20GB disk with -icds and just copying the partition table (MBR). It worked as expected. Then I repeated the operation but with GPT and it also went well. It just needs to have the origin disk last partition's last sector a little before the end of the target disk :) Without...

Well, the last time I did it, it was a 1TB HDD to a 240GB SSD. It had a NTFS partition with just 80GB used, so I shrinked the partition and then used this method.