Windows 10 Clone Problems

doberschelp · 30 Jan 2019

I'm tearing my hair out trying to clone my OS from a Samsung 850 EVO (500gb) to a Samsung 840 (500gb). My system has the 850 as the primary boot drive with a WD 2TB HD for data storage. The Samsung 840 is connected via USB 3.0. I thought this would be easy, using similar SSDs, but Macrium Reflect, Acronis True Image 2019, Samsung Data Migration, MiniTool Partition, and the Windows 10 Backup all failed at different points with conflicting errors. DSKCHK /F was run on both drives and found no errors. I've disabled my anti-virus program with no joy. Memory checks out OK. My system OS finally became corrupted and I had to run Windows repair in order to boot again. I'm lost, tired, frustrated and don't want to corrupt my OS again. When I initially upgraded Win 7 to Win 10 the cloning went perfectly. Something obviously changed but I can't figure out what. Can anyone suggest a fix?Thanks, Dave

Clintlgm · 30 Jan 2019

Basically, nothing has changed with MR you would have both disks accessible and boot your MR Recovery USB either MBR or UEFI which every system you are using, Drag all the partitions from the old disk down to the new disk and clone. I have found it best to Clean the Disk that you intend to clone to in other words Delete all partitions so that it is RAW as it came from the factory.

At which point are you failing?

doberschelp · 30 Jan 2019

Thanks for the response. I've followed those procedures exactly as described. And before attempting the clone operation with each of these programs, I've deleted all partitions on the 840 by using the DISKPART command. The 840 has nothing on it before attempting to clone from the 850. The Samsung Data migration gave me at around 50% that said "Cloning failed. An error occurred while reading the disk. 301001{0497c9}. The resolution from Samsung was to connect the 840 to an internal SATA connection. MiniToolPartition gave me an error of "Operaton "copy partition cannot be completed because drive c: is being used now." The resolution for the error was not clear to me. Macrium Reflect gave me an error 8. The resolution gave three reasons for the failure: connection, bad sectors, and antivirus. None of which worked.

lx07 · 30 Jan 2019

Don't clone then. Make an image to your WD. Then restore it.

Clintlgm · 30 Jan 2019

Well, I'm not understanding AV is not active in Win PE which is the environment that MR runs in for Cloning. If the SSD your Cloning to is RAW and your failing during the actual clone then either a defective SSD or Cable connection.
How about creating a Full image of your old SSD to another disk somewhere then remove the SSD and install the new SSD and then restore the Image to the new SSD. This will tell you that the SSD your using now is still not defective as it won't image if there are problems with it.
Same goes for the new SSD When you're restoring from the Image you created if that fails then the problem is with the new SSD. This will eliminate a lot of factors like a bad cable or the ext hard drive case having a failing chipset. I only talk about MR for this operation. Acronis has had issues since 2012 Minitool I have never tried cloning with since MR works so well.

Perhaps you don't understand how MR Works Backup and Restore with Macrium Reflect | Tutorials

Samuria · 30 Jan 2019

If your cloning from within windows some files can be locked boot from Mr boot disk to clone or as suggested make an image

Infrasonic · 30 Jan 2019

Have you checked the target SSD to make sure it is OK? Does the Samsung software give any health stats?
I had an SSD fail a while back, got it replaced under RMA and I did a Macrium clone to the new SSD this afternoon, SATA to SATA, no problems at all.

doberschelp · 30 Jan 2019

I decided the simplest fix would be to take Samsungs' recommendation to connect the backup drive via the SATA interface and try the backup again. I used Samsung Data Migration and re-cloned the drive. This time it was successful. Which leaves me wondering if maybe the USB cable from the docking station to the computer is indeed bad. Kind of hard to believe a straight wire that is never removed or stressed can go bad, but I guess it does happen. I'll replace the USB cable and then try this again.

Anway, thanks to all who responded!

doberschelp · 30 Jan 2019

I should add a special thanks to Clinglgm who was right on in his recommendations!

Steve C · 31 Jan 2019

lx07 said:

Don't clone then. Make an image to your WD. Then restore it.

That's a better approach than cloning. Note using cloning results in two disks having the same ID which can cause problems if both disks are connected to the computer.