We received our first Lat 7420 and had to flip it to AHCI (from Raid) in order to apply our image. No biggie, as we've had to do this with some past Latitudes. However, after the image was successfully applied, we were left with an error for the Standard SATA AHCI Controller...
A Microsoft driver is in place, so what we're seeing is "Device not started (storahci)," with a "0xC00000C2." The 'general' error being "The device cannot start. (Code 10). An I/O adapter hardware error has occurred."
Needless to say, applying the latest BIOS, Chipset, and nearly all the available drivers haven't addressed this. So, short of my researching the error...I'm wondering if it's more because we set it to AHCI.
We have the issue with Raid setting not working in SCCM as well, even with the latest IRST drivers.
So we flip it to AHCI. Imaging the device using AHCI has been working fine for us on this model (No errors during or after imaging), so i suspect you are missing the correct drivers. Did you pick up the latest F6 drivers from Dell, as well as import the SCCM drivers package for this model?
Also, we have had a couple of instances of the laptop reversing to Raid, even though no Dell updates have been installed. That, of course results in BSOD for the users until it is set back to AHCI in Bios. Major annoyance.
we´re having also issues with the "standard SATA-AHCI Controller". We have deployed the latest 20H2 driver package through our system, but the unknown devices still shows up in the device manager.
Just to clarify, I do show a driver on this device, but the "device cannot start." Now, maybe it's Microsoft's storahci.sys that's actually triggering the "Code 10" error, but a driver was automatically assigned...
Axel, do you mean that yours doesn't even have a driver on it?
We had 1 out of 6 devices that have this problem. We reverted back to Dell image but with AHCI set it BIOS and issue remains. Motherboard being replaced in a few days.
jddfw
2 Intern
•
87 Posts
7643
0
Posted March 8th, 2021 07:00
Needless to say, applying the latest BIOS, Chipset, and nearly all the available drivers haven't addressed this. So, short of my researching the error...I'm wondering if it's more because we set it to AHCI.