Samsung 950 PRO M.2 3.0 X4 NVMe SSD?

After installing Windows 10 on a new Samsung PRO M.2 NVMe SSD, I wanted to created a drive image using ATI2016's rescue media (I have ATI2016 installed on a bootable USB thumbdrive).
But, ATI2016 doesn't "see" the M.2 / NVMe device...
All "other" drives/partitions are correctly detected...
Anyone have the same experience?
Is there a work around, or a new version that will allow me to image my new Windows partition?
Thanks

- Log in to post comments

I tried to clone my Interl 530 SSD to Samsung 950 Pro. Acronis 2016 sees the new disk, but such as disk was not initialized, the cloning stops - the "non-initialized" disk can not start. I initialized Samsung 950 Pro SSD manually, but Acronis 2016 still can not proceed with cloning. It is an obvious bug, I believe.
Samsung Windows 10 driver is present, and I can access the disk using windows explorer.
- Log in to post comments

You will need create a WinPE disk and add the driver for your device so that True Image can recognize the device and work with it. Have a look at this link:
- Log in to post comments

I wrote a pretty short how to in this thread - https://forum.acronis.com/forum/102426
- Log in to post comments

Thanks for your help guys. There is a simpler solution - instead of paid Acronis "next year" non-working crap I used free Samsung Migration Software 3.0 and it did the job without problems, just needed to create restore disk and run it to link the new boot record on the new SSD to Windows 10.
Windows 10 has my Samsung driver (the driver is Microsoft's) it can recognize the disk and work with it, installed Acronis TI 2016 shall be able to see this driver and use. Of course, if their statement regarding Wiindows 10 support =true...
- Log in to post comments

Today I confirmed I could create a WinPE disk using the latest revision of the ATI2016 software, that I could boot from that disk (or thumb drive in my case), that I could use the drvload command to load the Samsung NVMe drivers, and afterwardS I could see the Samsung 950 PRO, I could image it, I could restore that image I just created, and most importantly, I could successfully boot my PC from the NVMe drive.
Question, is there a way for me to auto load the drivers?
- Log in to post comments

1. If you build the Acronis TI 2016 WinPE with the Windows 10 ADK installed, you will get the Windows 10 native NVMe driver in the WinPE and will not need to add the Samsung driver. I have tested this and it worked.
2. You can also add the Samsung driver to the WinPE if you want by following my guide at https://forum.acronis.com/forum/100770 . I got the .inf and .sys files needed from my Windows 10 64 bit system after installing the Samsung driver. The guide explains how to get these files. I have tested this and it worked.
The Samsung 950 Pro driver can be downloaded from http://ssd.samsungsemi.com/ecomobile/ssd/update15.do?fname=/Samsung_NVMExpress_Driver_rev10.zip . This driver is in .exe format and needs to be installed in Windows. Then the necessary .inf and .sys files can be found using the guide.
@dframeli
You should be able to auto load the Samsung driver by adding the drvload command to \Windows\System32\winpeshl.ini. You need to mount \sources\boot.wim to edit winpeshl.ini and unmount and save the changes. The guide gives you the necessary commands. I have not tested this.


I have a Samsung 950 Pro SSD issue. Rather than starting a new thread, I will post it here. I have a Samsung Pro SSD in an MSI X99A SLI PLUS motherboard. Windows 10 and Acronis 2016 installed. This software was migrated to the 950 Pro using Samsung migration software. The NVMe controller is using the Samsung driver. Everything is working except Acronis. Acronis cannot see the "c" drive (the 950 Pro). Backup does not appear in Acronis opening screen and there is a red dot at the top. Most likely indicating a problem, which there is. Is there anything that can be done, without having to make a disk or USB fob and operate Acronis outside the Windows 10 operating system?
- Log in to post comments

You do not say what driver version you are using. It is possible that an update to the latest driver will fix the issue. The latest driver seems to be the
Samsung NVMe driver v1.4.7.16 WHQL
You can get this digitally signed by Microsoft driver at this link: http://www.win-raid.com/t29f25-Recommended-AHCI-RAID-and-NVMe-Drivers.h…
- Log in to post comments

Easysky, Mustang already explained the solution - install Misrosoft Windows 10 ADK and use the original Microsoft driver Samsung NVM) instead of proprietary Samsung one (Samsung NVM Express ver. 1.0). It seems there is some kind of incompatibility between Samsung driver and Acronis TI 2016, may be it exists in some random situations.
May be new proprietary Samsung driver fixes the situation, I am going to try this one http://www.win-raid.com/t29f25-Recommended-AHCI-RAID-and-NVMe-Drivers.h… per previous post, thanks for sharing the link.
No, I am not going to try the "new" driver dated 10/13/2015 .... while the "old" ver. 1.0 driver is dated 2015 11/ ....I will just wait untill Samsung releases a new version of it's original NVM Express driver.
- Log in to post comments

Anyone try build 6027, released today, to see if it does a better job (natively) of recognizing M.2 NVMe SSDs?
- Log in to post comments

Well, instead of trying a new build I returned my Samsung 950 Pro back to the store - AMD motherboards don't support PCI-3.0 (except of one version of rare ASUS motherboards). I assume FM2+ boards don't really support it too (or maybe just video cards), because even having booting installation I can not apply any MS updates - the SSD stops to boot. I have ASRock FM2-A88-ITX+ motherboard. So I decided to use slower Samsung 850 Pro SATA SSD (no problem with it so far, Samsung Migration software works flawlessly. I don't intend to use Intel motherboards, so will wait for AMD motherboard with native support of m.2 slot and DDR4, hopefully it will happen sometime in the future. Good luck to all of you, guys!
- Log in to post comments

I was under the assumption that the Windows 8.1 ADK also had drivers for NVMe. Make sure 8.1 adk...
- Log in to post comments

dframeli wrote:Anyone try build 6027, released today, to see if it does a better job (natively) of recognizing M.2 NVMe SSDs?
it does not. BTW: Clonezilla Live CD does.
- Log in to post comments

After having very good results using the free version, I purchased multiple licenses for Macrium Reflect.
- Log in to post comments

Yes i confirm that Macrium reflect free do the job and it is free. After waiting and waiting for an Acronis update who isn't free, i'll also purchase licenses of Macrium. Sorry Acronis, but you are too late for your update..
- Log in to post comments

I'm trying to use Acronis True Image Home 2016 to clone a Windows 10 image (that has been upgraded from Windows 7 Ultimate) from a SATA disk to a Samsung V-Nand SSD 950 Pro M.2 NVM Express drive. Here's what happens:
1. Acronis True Image 2016 can see my SSD and I can choose it as the taregt drive.
2. Acronis restarts the PC and the Acronis loader starts.
3. I then get a window pop up that reads: "One or more of your removable disks may not have started at the moment. Click "Yes" to wait for full startup of te devices (recommended). Click "No" to ignore uninitialized devices and continue. Click "Cancel" to stop the current operation. Do you want to wait for the devices startup?"
4. If I click "Yes", I just get the same window again and again.
5. If I click "No" or "Cancel" the process just stops and the clone fails.
If I can't use Acronis for this, I'd like a refund.
Cheers.
- Log in to post comments

When you clone from within Windows, Acronis loads the default Linux recovery environment upon restart. That does not support NVMe drives. You need to create the optional WinPE recovery media with the Windows 10 ADK installed and perform the clone using that media.

Like others, I am having an ATI2016 - Samsung Pro 950 NVMe issue: The drive is installed on an ASUS X99-a mobo - with a clean install of Windows Insider Build 11099.
950 is recognized in BIOS and by ATI in the BACKUP mode - have made at least 6 backs up so far
950 is NOT recognized in the DESTINATION DISK part of the RESTORE mode
Have tried with latest Windows 10 drivers, as well as latest Samsung NVMe drivers - 1.4.7.17 - smae results - not recoginzed in the RESTORE mode.
In the process of building a WinPE based USB with Acronis Plug-in and trying to decide if this is the most fun ,or frustrating, experience I've had with ATI since I started wtih ATI 8 ;-)
ETA - WinPE USB made - now the M2 shows up in the RESTORE mode - didn't actually do a restore yet,
- Log in to post comments

BChat wrote:Like others, I am having an ATI2016 - Samsung Pro 950 NVMe issue: The drive is installed on an ASUS X99-a mobo - with a clean install of Windows Insider Build 11099.
950 is recognized in BIOS and by ATI in the BACKUP mode - have made at least 6 backs up so far
950 is NOT recognized in the DESTINATION DISK part of the RESTORE mode
Have tried with latest Windows 10 drivers, as well as latest Samsung NVMe drivers - 1.4.7.17 - smae results - not recoginzed in the RESTORE mode.
In the process of building a WinPE based USB with Acronis Plug-in and trying to decide if this is the most fun ,or frustrating, experience I've had with ATI since I started wtih ATI 8 ;-)
ETA - WinPE USB made - now the M2 shows up in the RESTORE mode - didn't actually do a restore yet,
By all means, do a test restore! On my machine, Acronis ran fine and happily backed up my Samsung NVMe drive and the WinPe disk recognized it, Acronis performed a "successful" restore however it would NOT boot the restored drive. Sorry, I do not plan to try any attempts at making this work for me so I can't offer any help except to perform a test restore to make sure it works!
P.S. I found this out on a fresh install of Windows 10 with nothing else installed besides Windows updates and Acronis. Windows using it's default NVMe driver. Tried also with the Samsung NVMe driver. No good.
- Log in to post comments
ATI version 6027 was last used. I have moved on to other backup means until (maybe) some day Acronis fixes their software.
System: ASUS Z170 Deluxe and i7 6700K, 16 gig DDR4, Asus GeForce GTX 980 TI, 250 gig M.2 NVME boot

Thanks for the info - not tried a restore as of yet - put an 850 Pro 256 GB SSD in the machine and installed Win 10 to it - just in case ;-)
The NVMe drives are still fairly new and probably not a lot of people using them - factual info seems scarce.
- Log in to post comments

Yeah may take awhile for any useful info to surface using these drives.
I also tried Carbonite, which now has a drive image feature they say is bootable. That did not work either so NVMe issues aren't limited to Acronis.
- Log in to post comments
ATI version 6027 was last used. I have moved on to other backup means until (maybe) some day Acronis fixes their software.
System: ASUS Z170 Deluxe and i7 6700K, 16 gig DDR4, Asus GeForce GTX 980 TI, 250 gig M.2 NVME boot

I have also succesfully made and restore an Acronis image to a NVMe Samsung 950 Pro, but it is not bootable. I'm trying now to restore to an external SATA drive and the clone the NVMe with Samsung Migration Software. Hope it will work.
- Log in to post comments

Razvan -- wrote:I have also succesfully made and restore an Acronis image to a NVMe Samsung 950 Pro, but it is not bootable. I'm trying now to restore to an external SATA drive and the clone the NVMe with Samsung Migration Software. Hope it will work.
Any news on this? I tried restoring to a sata HDD which wouldn't finish booting. It would get to the Windows desktop but not load icons, screen would blink about every 2 seconds. The image was of a fresh 10 install with the latest updates and drivers. I had also tried using onboard video and a different video card.
- Log in to post comments
ATI version 6027 was last used. I have moved on to other backup means until (maybe) some day Acronis fixes their software.
System: ASUS Z170 Deluxe and i7 6700K, 16 gig DDR4, Asus GeForce GTX 980 TI, 250 gig M.2 NVME boot

No luck. My hdd restore was not bootable. I ran out of ideeas.
- Log in to post comments



I have made a succesful restore. I didn't select all the drive to be restored, only the "system reserved" and the active partition, WITHOUT checking the MBR. It worked perfectly. If the MBR is already messed out from the previous tentatives of restoring, install a fresh copy of windows (10 will do best because it already recognise the NVMe) and then try to restore, without overwriting the MBR.
- Log in to post comments

@Razvan - WTG - BRAVO! - Worked for me too using a Win PE USB - THANK YOU!
- Log in to post comments