ZubeySweets :
The Original Ralph :
EaseUS ToDo wouldn't clone to the NVMe 950 PRO, but the samsung data migration did it flawlessly, cloning from an xp941 to the 950 PRO. But it cloned it so thorougly, not only did the 950 PRO boot without use of the windows dvd to repair boot files, the xp941 was taken "offline" (or so it said in disk management) because of a "signature collision"
- check it out http://www.samsung.com/global/business/semiconductor/mi...
but to make it screwier, it wouldn't clone back to the xp941, only because the 941 is an OEM unit and not on samsung's list of drives it will recognize
Ah. Weird stuff. I think The risk of me ruining my 256g 950 by trying to migrate OS to a larger one is too great then. I will have to be stuck with it unless I wanted to clean install on the larger one which I don't. I will just have to leave it as a os and programs drive and expand by raiding some 850 pros or something.
maybe my choice of words wasn't the best - the samsung data migration software worked flawlessly, including cloning the 950 PRO (512 GB) to a 256 gb samsung 840 EVO - that part actually surprised as much as the perfect clone from the xp941. We only cloned it to the 840 as we tweaked the OS after cloning to the 950 and running it as the OS drive.
what caught me by surprise was that, while it cloned the OS
from the xp941 fine, once i had the 950 PRO running as the OS drive, it wouldn't clone back to the xp941 - mainly because the xp941 is an OEM drive, and samsung does not offer support for it, not even in their data migration software. The manual for the data migration software lists the sammy drives it will support, ie clone to, and obviously the 840 EVO is one of them.
Also what was a little surprising, was that it would clone a larger drive, the 950 at 512GB, to a smaller drive, the 840 at 256GB. The 950 only held 102GB of data, so i created an "unallocated" partition of about 325 GB on the 950 hoping the samsung migration software would clone it, and it did. EaseUS refused, instead indicating the target drive was not large enough.
All this was on a bud's computer, a near identical build to mine - we actually built computers at the same time, a "first" DIY for both of us, kind of the blind leading the blind.