[SOLVED] NVME Clone failed, now Destination Drive Does not show

So last night I decided to upgrade my Intel 1 TB NVME (non OS E: Drive) to a 2TB Samsung 970 using a USB C external NVME enclosure.

During the Macrium cloning process I was notified it failed after 5 minutes.

Once that happened I was no longer able to see the destination drive on my desktop.

I was however able to connect with it once plugged into my laptop and all looked great.

I ordered a new enclosure and am going to try again using USB 3.0 tonight.

The current enclosure shows up on my desktop as Realtek with no typical drive information, but as a 970 on my laptop.

Anything I can do to try to increase my chances tonight?
 
Solution
It will be internal replacing the source as It needs more space.
Well, drag and drop may have issues.
Often, the sector size of the external enclosures is NOT the same as what the drive would be internally.

Take it out of the enclosure, and it may not work properly internally.


Recommendation above, Image.

In Macrium, an Image off to some other drive of sufficient space.
This results in a single file of xxxx.mrimage.
Swap the drives.
In the Macrium client, recover that Image to the new drive.
I have 2 NVME ports, one 970 with the OS and a second ( the Source Drive) Intel 1TB with all my music programs that will exceed the capacity if I install the whole suite. This is why I want to upgrade the Source Drive to a new 2TB 970.

I did not try a drag and drop in case there were hidden files.
 
You should be able to attempt imaging with Macrium rather than cloning.

It can work when cloning fails.

You would need a third drive (possibly external) to temporarily hold the image file.

1; make the image file; store it on the third drive
2; restore the image file from the third drive to the new NVMe.

Third drive would need to have a certain capacity...dependent on how much space is currently occupied on the source drive.

Your new NVMe could of course be defective in some way.


Samsung has software to transfer between drives. That might be worth a try if Macrium fails.
 
It's strange that the enclosure/drive shows when connected to laptop.

I have a new enclosure waiting for me hopefully it will resolve my issue.
You should be able to attempt imaging with Macrium rather than cloning.

It can work when cloning fails.

You would need a third drive (possibly external) to temporarily hold the image file.

1; make the image file; store it on the third drive
2; restore the image file from the third drive to the new NVMe.

Third drive would need to have a certain capacity...dependent on how much space is currently occupied on the source drive.

Your new NVMe could of course be defective in some way.


Samsung has software to transfer between drives. That might be worth a try if Macrium fails.
I tried an external HD last night but it was so unbearably slow. I have an all SSD system so I'm probably spoiled.

Going to give it another shot tonight, hopefully it was just an incompatible chipset driver on the enclosure though it worked like a charm on the laptop.
 
It's strange that the enclosure/drive shows when connected to laptop.

I have a new enclosure waiting for me hopefully it will resolve my issue.

I tried an external HD last night but it was so unbearably slow. I have an all SSD system so I'm probably spoiled.

Going to give it another shot tonight, hopefully it was just an incompatible chipset driver on the enclosure though it worked like a charm on the laptop.
What will be the final resting place for this target drive?
Internally, or in the enclosure?
 
It will be internal replacing the source as It needs more space.
Well, drag and drop may have issues.
Often, the sector size of the external enclosures is NOT the same as what the drive would be internally.

Take it out of the enclosure, and it may not work properly internally.


Recommendation above, Image.

In Macrium, an Image off to some other drive of sufficient space.
This results in a single file of xxxx.mrimage.
Swap the drives.
In the Macrium client, recover that Image to the new drive.
 
Solution
I actually just remembered I did use the same enclosure previously to upgrade my 1TB 970 from a smaller one using Samsung software. I've also used it with other drives doing the same. Probably got damaged. If new enclosure does not work I have my monthly image that I can restore from as a last case scenario.

One last thing, as Music Production takes up quite a bit of RAM, I just picked up some new RAM 2x32, will installing that first speed the process as data goes from source to RAM to destination (AFAIK).
 
I actually just remembered I did use the same enclosure previously to upgrade my 1TB 970 from a smaller one using Samsung software. I've also used it with other drives doing the same. Probably got damaged. If new enclosure does not work I have my monthly image that I can restore from as a last case scenario.

One last thing, as Music Production takes up quite a bit of RAM, I just picked up some new RAM 2x32, will installing that first speed the process as data goes from source to RAM to destination (AFAIK).
Music production is totally different than clone/image.

More RAM can't hurt, but it might not help.