Paragon OS Migrate fail, both new and old SSDs now won't boot Win10; need help asap!

[JoshMc1404]

I recently got a new SSD and used Paragon Migrate software to clone my previous 120Gb Samsung 840 to the new Corsair Force 240Gb. I followed the instructions completely yet when I tried to boot onto the new drive from BIOS the message "No OS found, please remove drives without OS on and restart" came up, I have tried multiple fixes from the Paragon troubleshooting pages but none have worked, and to top it off I can't get back onto Windows 10 on my original SSD, so I'm stuck! I've tried using the Paragon migrate recovery tool to fix Boot files and reset the MBR etc, but none of it worked! One thing I noticed was the drive name for my old SSD has been changed to L: instead of C: Could this be the problem and if so can I change it back using command prompt (built into the recovery usb) somehow?

I'd be happy just to have my old SSD back and running so I can use my PC, but after that i need some advice on how to get this cloning process correct/troubleshooted. Cheers

If you need any extra info to advise me just ask

 

[JoshMc1404]

*Update* - Tried reassigning drive letters but that didn't work, now the message 'No OS found' isn't even showing up, the only this on screen that happens to either drive is a blinking underscore jumps around the black screen and occasionally s6 appears in top left corner but the 6 is cut off, so it could be an error code thats hidden...

Unfortunately I don't have any disk images to restore to with 3rd party software. I also don't have a Windows 10 recovery drive either but will have one soon. Is it worth trying to fix or is it best just to reinstall Windows 10 and try to recover files using something like Recuva etc? Any thoughts would be greatly appreciated!

 

[USAFRet]

To 'fix' the current situation, completely unknown.

For future cloning attempts, this:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive
Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe as necessary.
Delete the original boot partitions, here:
https://social.technet.microsoft.com/Forums/windows/en-US/4f1b84ac-b193-40e3-943a-f45d52e23685/cant-delete-extra-healthy-recovery-partitions-and-healthy-efi-system-partition?forum=w8itproinstall
-----------------------------

 

[JoshMc1404]

To 'fix' the current situation, completely unknown.

For future cloning attempts, this:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive
Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe as necessary.
Delete the original boot partitions, here:
https://social.technet.microsoft.com/Forums/windows/en-US/4f1b84ac-b193-40e3-943a-f45d52e23685/cant-delete-extra-healthy-recovery-partitions-and-healthy-efi-system-partition?forum=w8itproinstall
-----------------------------

So if you can't see any fix for the current issue, do you reckon it would be best to reinstall Win10 on the new or old drive and then try to recover any files after that if possible?

Thanks for the info on future cloning as well, I was very careful to stick to the instructions for the Paragon software, so I honestly don't know how it messed up so bad :/

 

[USAFRet]

Install on the NEW drive, and attempt to recover some stuff from the old.

Also...BACKUPS.
A full drive image made before this attempt would allow you to start over again, with zero loss of data.

 

[JoshMc1404]

Install on the NEW drive, and attempt to recover some stuff from the old.

Also...BACKUPS.
A full drive image made before this attempt would allow you to start over again, with zero loss of data.

Yeah I thought that would be the best option availiable to me, but I will definitely learn from this, thanks for your advice.

The genuine irony of this situation is that I also installed a new 4tb HDD (alongside the new ssd) for backing up all my smaller drives to today, but I chose the cloning first.. I wish I had thought it through more in the moment!

 

[JoshMc1404]

To 'fix' the current situation, completely unknown.

For future cloning attempts, this:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive
Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe as necessary.
Delete the original boot partitions, here:
https://social.technet.microsoft.com/Forums/windows/en-US/4f1b84ac-b193-40e3-943a-f45d52e23685/cant-delete-extra-healthy-recovery-partitions-and-healthy-efi-system-partition?forum=w8itproinstall
-----------------------------

Just a quick follow up question, with regards to cloning using the Macrium Reflect, is it best to use it whilst on Windows on the SSD I am cloning, or better to use the WinPE version from a USB? Cheers

 

[USAFRet]

Just a quick follow up question, with regards to cloning using the Macrium Reflect, is it best to use it whilst on Windows on the SSD I am cloning, or better to use the WinPE version from a USB? Cheers

I've never had a problem with doing it from the Source drive.
It takes a snapshot at the beginning of the process, and continues from there.

 

[JoshMc1404]

Just a quick follow up question, with regards to cloning using the Macrium Reflect, is it best to use it whilst on Windows on the SSD I am cloning, or better to use the WinPE version from a USB? Cheers

I've never had a problem with doing it from the Source drive.
It takes a snapshot at the beginning of the process, and continues from there.

Ok Cheers I'll give it a go