This message was posted on behalf of Intel Corporation
According to the release notes, https://downloadmirror.intel.com/25771/eng/RSTe_ReleaseNotes%20_126.96.36.1993-public.pdf, the version Intel RSTe v188.8.131.523 should work with your system. However in this case the best support should be provided by your computer manufacturer and this is because from our end the support provided is for desktop chispets controllers since you have server motherboard ASRock Rack > is the right place in order to get more answers.
RSTe 184.108.40.2063 is for NVMe SSD's *only*. It's not for use with chipset based RAID.
220.127.116.113 is the correct driver. There are other versions that are slightly newer floating around on other manufacturers' websites, but I'm always scared to use storage drivers that aren't listed as supported by the manufacturer of the board (Asrock), or Intel.
Ok lets assume the RSTe 4.3 is the correct one. Then I wonder where I should get updates for this driver in the future as ASRockRack ususally does not update the drivers on their website and as far as I can see Intel also is not updating the RSTe in their download portal frequently?
And I still have this issue that with RSTe 4.3 installed, sending the PC into standby or shutting it down behaves strange: After sending the command, the hard drives are stopped, screen goes off and the Power LED starts blinking (in standby) or goes off (when shutting down). However, the PC does not turn off. Instead, after a few seconds, HDD and ODD drives are spinned up again and after another few seconds they are stopped again. Then the PC goes off finally. This does not happen with the Windows or the normal RST drivers. Can you explain this?
I can't explain it, drivers can do odd things sometimes.
Here's a newer RSTe driver and management utility from Lenovo, but it's for IastorA only. I don't think your Asrock board is using the SCU (IastorS), so it should be ok.
It's worth a shot, but keep in mind, you probably won't get support from Asrock if something goes awry.
I found the newest RSTe driver (v4.5.4) and tried it, but that changed nothing, stillt the strange behaviour...
What I do not understand: If I need the RSTe driver to have the storage controller work properly, why does it work with the Windows 10 integrated driver, which is - according to the driver version info - based on the regular RST 13.x driver?
The Windows 10 RST (iaStorAV) inbox driver contains the device ID for your RAID controller: PCI\VEN_8086&DEV_2826&CC_0104
Production versions of the RST driver from Intel do not contain that device ID.
I can't tell you why it's included in the Windows 10 inbox driver. Maybe for ease of installation for folks that don't understand how to add a storage driver when installing Windows.
Ok so that's clear to me now. What is still unclear is the fact, that the Win 10 inbox driver can access all 8 ports when they are in AHCI mode, bot only 6 ones when in RAID mode.
I found this article (http://www.heise.de/newsticker/meldung/S...ar-2485969.html) that is related to the X99 chipset which had a similar issue. It describes that the standard RST driver only supports a max. of 6 drives and that the ports 6+7 are then controlled automatically by the Win 10 integrated driver (if drives are connected). However in my case, all ports are always controlled by one controller, there is no second controller if RST is installed or Win 10 inbox driver is used. So I do not understand why it works for AHCI, but not for RAID, even if drives are connected. Really strange...
Do you have an idea on that?
The device ID of the controller changes when you set it for AHCI vs RAID.
In your case:
When you set it for AHCI and install Windows 10, it uses storahci.sys
When you set it for RAID and install Windows 10, it uses iaStorAV.sys
So this means if the controller is in AHCI mode, Widows 10 is using the generic Microsoft AHCI driver that supports all 8 ports, but as soon as I switch to RAID mode, Windows 10 uses the Intel inbox driver which is derived from regular RST driver that supports a max. of 6 drives?