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.
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.)
Hmmmm so... what am I doing wrong then?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]
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