Question Cloning SATA SSD to NVMe Drive

[Slidez]

I recently picked up a 1TB NVMe drive that I wanted to use as my windows drive. So I tried a couple different cloning programs untill I got one that worked. After the clone was complete I unplugged the old SATA drive (as suggested somewhere) and booted into Windows succesfully with the new NVMe drive. Happy with the results I turned the computer off and plugged in my old SATA drive. I ensured that the boot settings in bios were to boot from the NVMe drive. It would not boot into windows. I forget the error it gave me (I'm sorry). I went back into bios to check things again to ensure that it wasn't trying to boot from the SATA drive. It was not. I tried to boot again and it would not boot into windows. I again turned off the computer and disconnected the SATA drives to see if it would boot from the NVMe drive like it did previously. Now it would not boot from the NVMe drive either! Out of frustration, I just removed the new NVMe drive and my computer has booted and is running off the original SATA HD. Any ideas as to what could be happening? It's strange it would boot from the NVMe drive once, but not again and also not boot from the original SATA HD with the correct boot sequence selected.

 

[USAFRet]

If it didn't boot up with only the new drive, something went wrong with your clone process.

If you return the system back to original configuration, does it boot up? Without the new NVMe.
If so, please show us a screencap of the Disk Management window.

 

[Slidez]

If it didn't boot up with only the new drive, something went wrong with your clone process.

If you return the system back to original configuration, does it boot up? Without the new NVMe.
If so, please show us a screencap of the Disk Management window.

I don't think you read my post, but yes it booted again fine after I removed the new NVMe, and it also did initially boot from the NVMe drive immeditely after the cloning process with no other drives attached. It wasn't untill I re attached the old drives the problem became apparent. If you re-read my post its explained much more in detail of the process of events.

 

[USAFRet]

I don't think you read my post, but yes it booted again fine after I removed the new NVMe, and it also did initially boot from the NVMe drive immeditely after the cloning process with no other drives attached. It wasn't untill I re attached the old drives the problem became apparent. If you re-read my post its explained much more in detail of the process of events.

Yes I did read it.
I'm looking for a stable place for you to start over.

 

[USAFRet]

In addition, we'd need a full parts list, and what tool you used for this clone process.

 

[inditconsulting]

Hello...

my Acer win7 was moved to a more modern hard drive with all it's partitions, and ...

it took me three days and +15 tries even using linux disk tools...

a pain and I could not really tell you why it worked,

but used, COMODO backup, GParted, Disk util, ect, even CLI clone program (fast) on linux..

then once everything was finalized, I used emergency recovery disk (CD) to fix MBR and trouble shoot it's self and that worked ...

-tibor

 

[aldan]

judging from what you have said, you are screwed.listen to usafret

 

[USAFRet]

then once everything was finalized, I used emergency recovery disk (CD) to fix MBR and trouble shoot it's self and that worked ...

Yet now it does not work?

 

[Slidez]

Hello...

my Acer win7 was moved to a more modern hard drive with all it's partitions, and ...

it took me three days and +15 tries even using linux disk tools...

a pain and I could not really tell you why it worked,

but used, COMODO backup, GParted, Disk util, ect, even CLI clone program (fast) on linux..

then once everything was finalized, I used emergency recovery disk (CD) to fix MBR and trouble shoot it's self and that worked ...

-tibor

That's my next step, I created a recovery disk. I'm going to throw the new NVMe back in (not today) and see if fixing the boot config solves the issue. It booted up fine the first boot on the NVMe I think when I reinstalled the old SATA drives there is a conflict somewhere and it doesn't know what to do. If it doesn't work then I'll just roll with my SATA drives or take it somewhere to get fixed. It takes too long to get all my audio production software loaded up with all its stupid registration processes/licenses to start from scratch.

 

[USAFRet]

That's my next step, I created a recovery disk. I'm going to throw the new NVMe back in (not today) and see if fixing the MBR solves the issue. It booted up fine the first boot on the NVMe I think when I reinstalled the old SATA drives there is a conflict somewhere and it doesn't know what to do. If it doesn't work then I'll just roll with my SATA drives or take it somewhere to get fixed. It takes too long to get all my audio production software loaded up with all its stupid registration processes/licenses to start from scratch.

A proper and successful clone procedure should NOT need all these fixes.
One and done.

This is why I requested a screencap of the system as it is running on the old drive, so that we might start over.

 

[USAFRet]

-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Both drives must be the same partitioning scheme, either MBR or GPT
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung target SSD)
If you are cloning from a SATA drive to PCIe/NVMe, you may need to install the relevant driver for this new NVMe/PCIe drive.
Power off
Disconnect ALL drives except the current C and the new SSD
Power up

Verify the system boots with ONLY the current "C drive" connected.
If not, we have to fix that first.

Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

[Ignore this section if using the SDM. It does this automatically]
If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specify the resulting partition size, to even include the whole thing
[/end ignore]

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD. This is not optional.
This is to allow the system to try to boot from ONLY the SSD

(swapping cables is irrelevant with NVMe drives, but DO disconnect the old drive for this next part)
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 all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------