NVMe support drives
I just want to ask if ACRONIS 2016 sees any NVMe drive to clone?. The reason why I ask is because I have the 2014 version and I did try to do a clone drive of my intel 750 NVMe pci-e drive and the acronis bootable program won't see my NVMe drive, so I decide to ask if the 2016 version should see to clone my NVMe PCI-e 750 SSD, thanks for any info.


- Log in to post comments

I have a new motherboard, Gigabyte Z170X-UD5, with Samsung 950 PRO NVME, and it is under Intel Rapid Storage (motherboard RAID), and the WinPE bootable media does not see it! I also made and booted the Linux version and that also does not see this motherboard RAID.
How might I discover if WinPE is being updated and when the next update happens?
- Log in to post comments

Richard, WinPE uses the default drivers in the Windows ADK used to build the winPE. The problem here is that the RAID controller drivers need to be added to your WinPE "boot.wim" as well.
Download the controller drivers from gigabyte and extract them somehwere easy to get to. Then, assuming your rescue media is on USB flash drive, copy the boot.wim file from the sources directory somewhere easy to access as well. The following commands need to be modified to fit your locations, but should help you get the drivers injected. Once that is done, copy the boot.wim back to the USB flash drive and test it out.
(note that you need to make a blank mount folder first and make sure to give the mount folder, driver folder and teh boot.wim file full access to the account you are using these commands on/from in the Windows ADK. Not sure what version of Windows you have installed or what version of the Windows ADK you're using, but I'd use the windows 10 ADK as it has the best driver compatibility and can be installed/run on Win 7- Win 10). Inject drivers that match the version of ADK you use to create the WinPE too. )
---------------------------------------------------------------------------------------------------
Dism /Mount-WIM /WimFile:"C:\boot.wim" /index:1 /MountDir:"C:\MOUNT"
Dism /Image:C:\MOUNT /Add-Driver /Driver:C:\MyDriverFolder /Recurse /ForceUnsigned
Dism /Unmount-wim /mountdir:"C:\MOUNT" /commit
- Log in to post comments

Similar question in regards to cloning:
I currently have traditional BIOS and have readily 'cloned' my C: drives as a backup precaution. Love Acronis True Image for that (I can just switch out drives if I ever have a problem that is not fixed by 'system restore'....not had to do that, but just in case).
I'm now contemplating a new PC build with a Z170 chipset MB PC that supports NVMe in PCIex, M.2 and U.2 slots. My question is, can I clone a bootable UEFI NVMe drive? And does that cloned drive need to be another NVMe drive (in one of the PCIe, M.2, U.2 slots) or can I clone it into a regular SATA SSD?
I think I may have just answered my own question....if you clone the NVMe drive onto a SATA SSD as a backup, and then the NVMe drive does down, then you won't be able to do anything with the SATA SSD, correct?....or will that boot (if you clone the NVMe drive onto it)?
I guess I can find out by trying it, but I like to think ahead and work it out beforehand. Thanks for any help.
Regards,
-PMM
- Log in to post comments

PMM,
Well, right now I would have to say you stand a 50/50 chance of success. I would also have to say that this is highly dependent on the bios of the MB you are using.
I have performed a clone of an NVMe PCIe M.2 drive to an SATA III SSD drive with success on an ASUS Z97 Deluxe board. Another MVP here, Bobbo, has tried this with a Gigabyte Z170 board and has faced failure that at this point looks like a locked drive problem along with BCD corruption.
So I suppose it is at present a try and see proposition!
- Log in to post comments

I think it will work. migrating from one system to the other is the most challenging part as drivers are likely to be different, the new system bios may need to have things like secure boot disabled and/or CSM/legacy enabled... you'll want to make sure to boot your recovery media in legacy mode to do the restore, and you'll need to make sure the new system SATA mode is set to be the same as the old system (AHCI or RAID in most cases). Then run UR to generalize drivers on the deployed image and hopefully it works.
As for moving from NVME to SATA, it works. I went from SATA to NVME and have recently been doing my own testing going from NVME back to SATA as well. What I found is that my migrated disk becomes "locked' when reverting back, but it may just be my board that's causing this. As a result, it fought with "no device found' messages for weeks and finally found that it was the disk being locked. To unlock it, I have to use F8 to boot into safemode first - that immediately unlocks the drive and then boots. On my board, I can't just push F8 either though. I have to wait for it to fail, 4 loud beeps, enters bios automatically, don't save anything and boot, fail again, 4 loud beeps and then Windows tells me it failed twice and presents me with F8 for safeboot.
Your scenario is complicated by moving different systems though so may have other hurdles to get through first. I would suggest clonging to an SSD in the same system and getting that sorted out first to make sure it works. Then take your working/cloned SSD and put it in another system and run UR on it and play with the bios as well if need be.
- Log in to post comments