[SOLVED] NVMe to NVMe system cloning problem (with a twist)

Apr 4, 2019
2
0
10
Hey there,

I have been for a few weeks now the proud owner of a Razer Blade Stealth 2019. Since the 250GB storage was a bit too small for me as this is now my primary device with an eGPU solution, I decided to upgrade it to a Samsung 970 Pro for good measures. At first, I tried to do a clean install of windows 10 on the new drive but I encountered all kinds of issues from drivers, especially from Synapse and TB3. Therefor, I decided to clone it instead. Since both drives were NVMe, I had to buy a dedicated NVMe to USB 3.1 enclosure from Adwits, with a JMicron controller inside.

I first tried to use the Samsung utility but it was recognizing the enclosure controller instead of the drive inside, not allowing tranfer then. I tried to inverse the drives positions but I wasn't able to boot from the external drive.

I then tried using Macrium Reflects. Cloning worked, but I now have a BSOD when trying to boot forn the 970 Pro. I tried the solution found on this forum, using a recovery drive cmd and trying to rebuild the BSD but it returned something along the lines of "Specified path not existing" (I have windows in French, pardonnez moi). I tried using the recovery mode from the Razer BIOS but it did nothing to help with my problem.

What else can I try ?
 
Solution
Can you try imaging the 250 to an external drive, then swap in the new drive and restore the image, expanding the partition in the process.
Macruim can even create the recovery flash drive for you. Be sure it works to boot the system though, I've never tried it with NVME Drives.
Can you try imaging the 250 to an external drive, then swap in the new drive and restore the image, expanding the partition in the process.
Macruim can even create the recovery flash drive for you. Be sure it works to boot the system though, I've never tried it with NVME Drives.
 
Solution
That's what I ended up doing. I though tho that I would do another partition instead of extending the system one in order to streamline the process of cloning/imaging for my next recovery, to keep it in check with the 250 disk.
I'm not a 100% satisfied with the cloning solution tho. It's pretty peculiar but I didn't owned a wide enough disk to image my whole system so I had to delete some stuff including the 90gb Destiny 2 which I raid on daily, and it will take me about 20H to download again with my poor connection. That's really no biggie, but it might be good to seek another answer for someone in the same situation but with greater valued files.

Thanks for your answer !
 

TRENDING THREADS