NVMe PCIe : BSOD after imaging "INACCESSIBLE_BOOT_DEVICE"
-
Hello,
As part of the reinstallation of a computer room with Fog (with Dell Precision 5820/7960), I’m encountering a problem.
I’m making an image on Fog of a Windows and Debian dualboot workstation from a workstation with a SATA SSD.
When I deploy the image on a workstation with a SATA SSD or SATA hard disk, I don’t have any problems, I can boot into Windows and Debian.
On the other hand, when I deploy the image on a workstation with an NVMe PCIe SSD (Samsung PM9A1), it’s impossible to boot on Windows, but it boots just fine on Debian.
Windows gives me this BSOD error “INACCESSIBLE_BOOT_DEVICE”.
I thought it wasn’t loading the NVMe drivers at boot time, since the host on which I made the image doesn’t have any NVMe disks, so I did this command sc.exe config stornvme start= boot so that Windows would load the driver at boot time, but it doesn’t change anything.
In the BIOS settings, both workstations are in AHCI and not in RAID.
I’ve been racking my brains for days, but I can’t find a solution.
-
@nathan67 That sounds like the image doesn’t have the nvme driver.
There’s a potential easy solution, first check the bios settings on the nvme machine, if there are settings for intel VMD or intel optane make sure those are off. They require a different storage driver that isn’t including by default in windows.You could also try recapturing the image from the nvme based machine
The more complicated solution involves recapturing the image and ensuring you use sysprep and add a set of basic storage drivers that don’t get wiped so they’re embedded and at the ready for multiple use cases. If the other options don’t work I can find some time to help with that. If it requires the intel vmd driver though, I’ve had experiences where that driver makes older non-vmd intel chipsets fail to boot. So I eventually gave up on having VMD enabled, it’s a pretty sweet feature and can add some performance, but not enough to matter for the operational complexity within a controlled and mixed business environment (at least that’s what I went with for me).
-
Is secure boot on or off? If it’s windows 11, i’ve had problems where it hates legacy and will only boot in secure boot due to UEFI needed
-
What type of SATA controller do you have is it a Intel RST chip?
Mat
-
@nathan67 That sounds like the image doesn’t have the nvme driver.
There’s a potential easy solution, first check the bios settings on the nvme machine, if there are settings for intel VMD or intel optane make sure those are off. They require a different storage driver that isn’t including by default in windows.You could also try recapturing the image from the nvme based machine
The more complicated solution involves recapturing the image and ensuring you use sysprep and add a set of basic storage drivers that don’t get wiped so they’re embedded and at the ready for multiple use cases. If the other options don’t work I can find some time to help with that. If it requires the intel vmd driver though, I’ve had experiences where that driver makes older non-vmd intel chipsets fail to boot. So I eventually gave up on having VMD enabled, it’s a pretty sweet feature and can add some performance, but not enough to matter for the operational complexity within a controlled and mixed business environment (at least that’s what I went with for me).
-
Hello,
My problem is solved, it was related to the lack of loading of NVMe drivers at Windows startup.
I made my image on a workstation with NVMe disks instead of sata disks, which gets around the problem. -
[[undefined-on, N nathan67, ]]
-
[[undefined-on, N nathan67, ]]
