Snap Deployment Failing to NVMe M.2
We have a few Dell Optiplex 7050 towers that have NVMe M.2 drives right on the MoBo that are failing deployment. I can image the drive just fine via Win PE with the proper drivers loaded (iRST & Network Drivers) but when I deploy the image to the exact same machine it attempts to deploy the image, runs all the way to 99% and then fails. We are running the latest version of Snap Deploy 5 build 1749. The systems have UEFI enabled and Secure Boot disabled. I even tried swapping Sata from Raid to AHCI, reinstalled Windows 10, captured the new image, and went to deploy it again. Same result and same error. The error log is attached.
Host '146.201.x.x' has failed the deployment.
Additional info:
--------------------
Error code: 1
Module: 52
LineInfo: 6934824D6BD2F6B4
Fields: $module : "osd_server_vs_1749"
Message: Host '146.201.x.x' has failed the deployment.
--------------------
Error code: 1
Module: 51
LineInfo: E3394061D0E3A340
Fields: $module : "osd_server_vs_1749"
Message: Failed to deploy the master image.
--------------------
Error code: 1
Module: 7
LineInfo: CE31472D2102C9F
Fields: $module : "osd_server_vs_1749"
Message: Internal error: write outside of allowed area

- Se connecter pour poster des commentaires

Andrew,
I'm running in to the same issues with a Lenovo M710q (NVMe drive). I've also upgraded to the 1755 build but I have not been successful at all. Can you either post or PM me exactly what you did to make this work?
Thanks.
- Se connecter pour poster des commentaires

I was having the same issue with Lenovo M715q images, they would not even reach 99% before failing. I was able to fix this by changing to a Windows PE based boot image. It also fixed issues I was having with UEFI / TPM / Secure Boot.
Snap Deploy 5 will offer to download the WinPE stuff if it's not available when you try to create a WinPE image. Just download and unpack WinPE 10 and create the bootable image, then upload to PXE or make a bootable USB.
- Se connecter pour poster des commentaires

Hello Jam,
you'll probably need to re-create the master image with the build 1755. Then re-attempt the deployment.
- Se connecter pour poster des commentaires

We faced this issue before.
We switched to 1755 which fixed this particular issue and then 1761.
1755 needs 1755 images to work. I would actually upgrade to 1761 if you can. 1761 been solid for us and has fixed this issue as well (among many others) for us.
Also, you don't need to disable secure boot as Acronis SD5 supports it. We have secure boot enabled on our machines with no problem.
- Se connecter pour poster des commentaires