Comments on: How to Migrate Windows 10 from HDD to SSD Using Clonezilla

By: Timoothy Takemoto timtak

Timoothy Takemoto timtak — Wed, 08 Feb 2023 09:17:31 +0000

In reply to Matt. Hi Matt, I am sorry I don't remember! I guess it was because the system recovery disk may be created at the top end of your drive, but if you want to put it in the smallest space possible then (where M is your windows related files and R is your recovery drive)

MMMMMMMMMMMMR

is preferable to

MMMMMMMMMMMM         R

where there is some unused disk space between the windows files and the recovery partition. The above did work for me, and all of the steps may not have been necessary, but I don't know why or how now! I have 3 PCs with SSDs that have been going for ages.

By: Matt

Matt — Tue, 07 Feb 2023 20:40:06 +0000

In reply to Timothy Takemoto timtak.

Timothy, not sure if you’ll respond after 3 years but here goes: It looks like your procedure greatly simplified the process by eliminating the command lines. Can you please confirm if this worked for you? Can you elaborate on step 5 as to why you need to move your recovery partition to the left? A link to a video or screenshots would help. Thanks

By: Maximiliano Castro

Maximiliano Castro — Sat, 09 Oct 2021 17:38:53 +0000

Many many thanks for this. I followed the tutorial religiously and not also managed to make it work, choosing only the partitions that I needed, but also I learned a lot in the process. A couple of extra steps I needed to do in order to make it all work on my end: The cloning process failed on the C: drive because of bad sectors on the source. I saw this exact message:

Warning: The disk has bad sectors. This means physical damage on the...

I was able to solve this by:

Boot on the source disk OS.
Run chkdsk /f. As the disk cannot be locked it schedules it for the next boot. I went through with it and rebooted to let it run.
Rebooted on Clonezilla, used Expert mode, and retried cloning C: now with the -rescue flag.

It detected bad sectors on the source but kept going till the end. The SSD wasn't able to boot after. So I run:

Created a bootable windows 10 install USB drive and booted from it.
Troubleshoot > Boot Repair. It failed so I then:
Troubleshoot > Shell prompt, issued:

> bootrec.exe /fixmbr
> bootrec.exe /fixboot
> bootrec.exe /scanos
> bootrec.exe /rebuildbcd

followed Method 4 of https://www.ubackup.com/windows-10/cloned-ssd-wont-boot-windows-10-4125.html) and Reboot, and it finally booted :)

Thanks again!

By: klapa

klapa — Mon, 21 Dec 2020 19:09:01 +0000

I guess I don’t understand why one would go through all of this when all that is needed to migrate make exact clones of disks are native Linux tools – sfdisk to duplicate partitions and gpartd to copy from one drive to the other.

Such can be done on the subject host by booting a Linux “live” disk after attaching the new drive alongside the original, or by a “third party” Linux machine with the drives attached.

By: Vanessa WH

Vanessa WH — Tue, 03 Nov 2020 08:17:39 +0000

We can also draw support from other professional system migration software. Steps of the migrating systems with such software could be easier. Besides, when we transfer the system from HDD to SSD, we should pay attention to whether the new disk has been 4K aligned. If it is not 4K aligned, the performance of the SSD will be poor. I have ever used this software to transfer the system from SSD to HDD and it helped me make the 4K alignment in SSD automatically. And the whole operation is only 4 simple steps. The software here has helped me many times to migrate systems with simple steps.