Problems Cloning OS, HDD -> nVME m.2; Advice?

Formula.350

[H]ard|Gawd
Joined
Sep 30, 2011
Messages
1,102
I decided that it'd be in my best interest to create a new thread instead of using the other, similar, thread to seek help... This is where the below quote comes from. For anyone not wanting to read all of that, there is still a question at the end to weigh in on.

Yes, usb to sata enclosure if your laptop has only 1 2.5".

No need for an M2 enclosure. Just chuck in the M2 and clone, then change boot order to the M2 from the HDD.

It's worth noting that samsung drives come with a cloning tool. Other drives may not [this may have changed though]
Hmmmm so... what am I doing wrong then?

I have Win10 installed on a temp (old) WD VelociRaptor 150GB drive, and since I have it configured very much how I like it, I didn't really want to reinstall Windows.
Per the recommendation of someone (I've yet to comb through my posts to find out who, could've even been you hah), I used Macrium Reflect to clone it. Since it didn't suggest rebooting into any sort of WinPE environment or what not, I did it from within Windows, from the one I was cloning. It did so via Shadow Copy and completed in roughly 20 minutes (not bad, considering it's a 95% full SATA II host drive to an nVME drive).

The nVME is an OEM Samsung PM961 240GB. Was indeed brand new, or at least time was taken to completely reset it to RAW state.
Either way... I had initialized it as GPT, formatted it but left it without a drive letter.
Loaded up Macrium Reflect, selected my VelociRaptor to be cloned, and selected the m.2 drive as the target.

Now, since this is my first m.2 drive I don't know if this is normal or not... But while M$'s Drive Manager did not show this, Reflect was showing there to be a 128MB partition, in addition to the one I created... As I didn't know its purpose, I left it alone and let Reflect clone to the partition I created.

That being said, it took 20mins as stated, everything seemed fine. There was a discrepancy in the size of the clone though, not having as much data as the VelociRaptor showed (both Size and Size on Disk, so not a difference in formatting size), which my understanding was a Shadow Copy was able to access even in-use files and copy them so... not sure why this was the case.
From there I restarted, disconnected the HDD's cables, and set the M.2 as the boot drive.

Again, being my first m.2, I don't know if this is normal... but my MSI Titanium X370 motherboard was not listing the m.2 as a UEFI drive as I had expected. Whether or not this is due to the fact that the VelociRaptor was an old Dell drive with a UEFI partition that held the Vista Installation files, and that I didn't clone that partition... I don't know. The main Windows partition is not UEFI either, but operates fine.

Regardless, I set it to be the primary boot, and... nothin! It skipped the m.2 and actually ended up falling back to another drive further down the list that had an old Win7 install on one of the partitions.
Reconnected the VelociRaptor and set it to be the next boot device after the m.2, and this time Win10 loaded, but it did so from said HDD :\

At this time I'm figuring it was because I set the m.2 as GPT instead of MBR; and in my haste I deleted the partition in Drive Manager before really looking at it... BUT when I right-clicked the m.2 drive I did notice there was the option to "Convert to GPT"... So it looks like Reflect actually had converted it to MBR upon cloning....

As such, I am confused and now debating whether or not I should try to clone it again, but this time remove that mystery 128MB leading-partition from the m.2 (Reflect can remove it).

So my question becomes: Is that mystery 128MB leading-partition something that the PM961 controller created for an important purpose and I shouldn't remove it, or is it something Windows 10 created where removing it is no big deal? In short, should I leave it or can I safely remove it?


(For the record, I did try the Samsung Migration Tool, but since this is an OEM PM961 and not a "Retail" product, the program doesn't detect the m.2 drive, only my SATA 850 EVO :( And I lack the know-how to hex edit the app to try and swap in the Device ID to allow the program to recognize it.)
 
I've had issues where it didn't detect my drive because it was GPT disk instead of MBR. Make sure it is an MBR formatted disk and try to clone again.
 
I've had issues where it didn't detect my drive because it was GPT disk instead of MBR. Make sure it is an MBR formatted disk and try to clone again.
Since I removed the partition from it last night in Disk Management (been calling it Drive Manager, whoops), inside Reflect there now is no longer that 128MB Partition. So perhaps that's related to the GPT.

However, I've also now noticed that if I drag the Partition I want to clone onto the Destination drive (the m.2), the "Cloned Parititon Properties" option becomes available. Inside there I now have the options to:
Set Drive Letter (I can even select C: despite it being my current HDD"s drive letter)
Partition Type: Primary | Active (auto selected) | Logical
Partition Size
Alightment: XP (CHS) | Vista/7/SSD (1MB) (auto selected)

So I was thinking this time of setting it to C, increasing the partition size to max to save me time afterwards, but I still lack the ability to set the partition to all the additional flags as the HDD has. Of them, the important ones to me are: Boot, Primary, Active.

I'm wondering then, if after I clone this and before I shut down, if I should fire up DiskPart and see about setting those flags?
Or rather, after I clone if it doesn't boot, as I'm just "preparing for the worst". Which my curiosity has me wondering if, due to how wonky Win10 is with its bootloader, if I won't need to also modify the BootCfg to point to the m.2's device ID.

Either way, I think in order to set it to MBR, I'll have to use DiskPart anyways. There's an option to Clear all the config data from a drive, which would hopefully let me initialize it again, allowing me to for-certain set it as MBR.
I'm going to try cloning it quick as I said, set to C, and Active. If that fails, I'll try setting it to Boot and Primary in DiskPart, and if that fails, I'll Clear the cfg data so that I can do it exactly as you said.
 
The software I used to clone our drives here at the office was called Backupper(went from HDD to SSD en masse). The free option was good enough. I just needed to make sure the drive was MBR not GPT. Then cloned and it worked fine.
 
The software I used to clone our drives here at the office was called Backupper(went from HDD to SSD en masse). The free option was good enough. I just needed to make sure the drive was MBR not GPT. Then cloned and it worked fine.
If this try doesn't pan out I may just go with that, then. Are there any special steps needed to take, or Live Environments I need to boot into?

EDIT: I believe my method worked. With the drive initialized but no partition set (but I presume set as MBR due to aforementioned reasons), set to C:, left it Active, then Cloned... It appears to be booted off the m.2 now! (Though, it took just as long as it did off the HDD heh)
C:\ is now the SSD, the HDD moved to E:\ and L:\ (listen I have a lot of partitioned drives, leave me alone lmao)

I'll reboot in a moment with the HDD completely disconnected to make sure it is booting off the m.2, considering the boot wasn't very hasty.
 
Last edited:
Hmpf. Now Windows is bitching about activation and how "We can't activate Windows on this device ass the product key you entered has already been used on a different device. Go to the Store to buy genuine Windows."
And yet... The activation key I have is a 5 System key, which has only been used on 2, maybe 3 systems :shifty:

:rolleyes: GG M$! (y)

EDIT: Ok so this was mentioned on another site...
"If it was activated on HDD it should reactivate on SSD, unless you have both drives in same PC or put SSD in another PC?"​

And since I was just about to shut down finally to remove the original HDD that 10 was on and install my new 6TB that arrived today, before I noticed that activation watermark... I'll assume that is exactly the case. Still, seems dumb that a multi-user key would take issue with this considering there are at least 2 system activations available yet. We shall see...
 
Last edited:
isnt there any option to activate via phone? I always do that option whenever it doesn't auto activate. never had issues.
 
isnt there any option to activate via phone? I always do that option whenever it doesn't auto activate. never had issues.
Ok so good news is that with the old HDD removed, Windows boots up at a speed I'd expect from an nVME drive :)

The bad news is, it's still not wanting to activate, and so I'll in fact have to call (it does provide an "Activate by phone" option. I just bluh... waste of time heh). :(
 
activate by phone doesn't take more than 5 mins. just do it! lol
 
activate by phone doesn't take more than 5 mins. just do it! lol
I prefer to exhaust all other options to make sure that it really is an issue that merits calling them. I find it improves my own knowledge heh

In this case, it was because Windows Update service was disabled. I don't recall having done that, personally, but it's quite likely I did (considering I did not want anything being downloaded due to my metered and slow connection).

But yea, once I enabled that, started the service, and clicked the Troubleshooter... PRESTO!

So now I know that if I run across this again, it's possible the WU service isn't running. :)


Anyways, thank you for all the assistance!
 
Back
Top