Skip to main content

Acronis True Image 2018 DOES recover m.2 drives

I can now say that I had to test the ability to recover my m.2 Samsung 960 Pro on my EVGA X99 FTW K motherboard.  My first 960 Pro failed within 3 weeks of installation.  Took it back to the store and exchanged for a new one.  Unfortunately, the Clone part of 2018 didn't work.  Seems that it came up with errors.  Luckily I had a copy of 2017 Linux version and cloned the drive from original Samsung SSD.  Unfortunately, I didn't check to see if the clone made the 960 bootable, but the Linux version of 2017 did recognize the m.2.  So I finally just decided to give Disk Recovery a try with 2018 and viola...the drive is bootable and fully functional once more.   Thanks Acronis...as advertised...

0 Users found this helpful

Bob, thanks for giving the above feedback and glad to hear that you were able to recover your m.2 drive successfully.

Bob M,

You say that the clone part of 2018 didn't work, you got errors, can you please explain? 

It came up with errors during the clone procedure.  Gave me the option to retry or ignore.  Chose to cancel.  Tried to ignore the first time and the drive was not bootable.  Had to use the Linux version of TI 2017 to get the clone to complete without errors.  Don't have any WinPE recovery from 2017 anymore.  Guess I would have to try again and take photos to show exact error.  If you want to test...here is system config

 

i7 5820K

EVGA X99 FTW K Motherboard

32 GB of DDR4 2666 G Skill Memory

 

Question, did you use the Linux version of 2018 when attempting to clone the drive?

I tested the clone function extensively in 2018 and only had one failure.  I did not test the Linux version of 2018 however so possibly it does not work correctly with PCIe M.2 drives.

Thank you.  If you have the occasion to try this again, hopefully not, do so from within the Windows installed application.

This method (new to 2018 version) has worked very well for me.  The only exception was an attempt to use the clone feature to clone to a disk that already had a working OS image from the same machine on the disk.  The fix for that was to wipe the target disk before running the clone. 

With the limited information you were able to provide here I suspect that you could not use the Linux version of 2018 because of a lack of driver support for your M.2 drives.  Same goes for the WinPE version if you selected the Advanced creation method when using the Media Creation Tool.  If you use the Simple creation method then drivers specific for the system on which that media was created will be carried over to the newly created media so the clone tool will work with the M.2 PCIe based drives.