Ok so I was trying to clone 512gb nvme ssd to my new 2tb drive with clonezilla and it keeps taking me to automatic repair. I unplugged the original drive and replaced it with the new one before booting. I ran a chkdsk both times before cloning.
The first time I cloned the drive i used these settings:
device to device beginer disk to local disk Chose my source and target Skip disk checking -k0 use source partition table
Then I tried these settings:
device to device expert disk to local disk Chose my source and target Left everything as default -k1 Create partition table proportionally
I also plan on partitioning half of the drive so that I can dual boot linux as Window 10 is reaching eol and I don’t want anything to do with Windows 11 and I still need Windows for gaming.
Did you try running the repair to see if it fixes it?
The reason is the boot drive now has a different ID, so Windows can’t boot from it. So it assumes (rightly so) that the boot drive has changed and launches into repair to fix it. This is something repair can fix for you normally.
Another way is to open up a command prompt in the repair environment (or from a Windows USB stick). Then use the bcdtool to edit the boot options and tell it to use the correct drive. There are plenty of instructions on this found with a simple Google search.
The cloning probably went fine, so don’t assume it has anything to do with that. Just a completely different ssd which trips up the boot.
Notably on Linux device ID are also normally used, so you would have the same kind of issue. Ignore all the Linux fanboys that go Windows bad Linux good and don’t actually help you.
I had the same issue, you need to run sysprep inside Windows immediately before you create the image. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation?view=windows-11
If you can, I recommend taking a full image of the old device and dumping it onto the new one (since the new one is bigger, this should work just fine. This will preserve all filesystem IDs and partition table quirks that may be triggering windows to repair itself.
You can do this with a command like:
dd if=/dev/sda of=/path/to/full_image.dat
Where /dev/sda is your old disk (may be sdb or sdc, use blkid to find out)
Then do the opposite on the new drive
dd if=/path/to/full_image.dat of=/dev/sdb
Where /dev/sdb is your new drive (may have a different letter)
If you can plug th both in to the same machine, you can copy the image directly
dd if=/dev/sda of=/dev/sdb
There are other dd params that may make the copy faster, but they don’t change the result. Note that dd is silent when working, but you can send signal USR1 to get progress
Ctrl-z to interrupt dd bg To continue the dd job in the background kill -s USR1 $(pgrep dd) to get a progress message
Typically, I’ve fixed this with a Windows install stick and using the bcdboot command to rebuild the BCD from scratch.
Are you booting EFI with Windows, or is the old drive MBR?