New
#51
[QUOTE=antares;2610568]Just some facts to make it clear:
- The source disk is a Samsung 970 512MB Nvme installed in my Dell XPS 9570 laptop, it has Windows 10 installed and it works perfectly fine. sfc and dism tests show the file system has no corruption.
- The target disk is a Samsung 980 1TB Nvme,...
First let me entertain you with a seriously funny coincidence!
Other than the laptop, I have, bought and did exactly to a T the same!!
Oddly enough, I had also exactly the same problem ending with a unbootable clone once inserted into the motherboard.
Acronis was a failure and so AOMEI.
However, when I use Paragon disk/partition software to clone the drive it worked!
Thereafter I experimented and could verify that indeed the two aforementioned apps do have a cloning bug.
The only one that had done the job flawlessly was the paragon disk/partition manager.
I reported this to the relevant support departments including my verifiable and reproducible issue.
[QUOTE=antares;2610810]No, but the issue I encountered with cloning the identical Drive set was the software used.
For some reason Acronis and AOMEI somehow do not properly clone GPT partitions.
also make sure that before you clone the new drive is set to GPT.
In my case only paragon did it right.
Yes, I know Clonezilla does the cloning offline, and I always do it offline with Acronis too, safest method. I was just saying that even if offline, when I choose the source drive it is listed as "Startech mass storage etc", not as "Samsung 970 Pro...", so even if offline the drive inside the enclosure is not seen, just the enclosure's flash rom chipset, and this MIGHT be the reason of the unsuccessful clone.
As per the price of the enclosure I agree it's BS, even if it wouldn't have this issue.