Intel R2312WF0NP Server System RSTe Driver 6.0.0.1357

Intel Rapid Storage Technology enterprise (Intel RSTe) package is intended for all customers. Included in this package are Intel Virtual RAID on CPU (Intel VROC) 6.0 Production Version (PV) release, Intel RSTe SATA RAID, and Intel RSTe NVMe RAID. For the Pre-OS environment, Intel VROC UEFI drivers and Intel RSTe SATA UEFI, and Legacy OROM images are included

Intel Virtual RAID on CPU (Intel VROC) is the term describing Intel RSTe with Intel Volume Management Device (Intel VMD)-enabled NVMe drivers, assisting CPU attached PCIe NVMe SSD bootable RAID.

Note: It is always recommended to update your system BIOS to the included PV release of Pre-OS drivers to take advantage of the most optimal and updated features of each Production Version release.

Issues Resolved in 6.0 PV:

- When attempting to install Microsoft Windows 10 RS5/Server 2019 onto an Intel VROC (VMD RAID) volume, a system crash may be encountered.
- In the BIOS, under SATA Mode Options, RAID options can be disabled, but RAID can still be created after save and reboot.
- When running in an Intel VROC configuration, the Negotiated Link rate for the NVMe drive connected may not be reported accurately in the device properties window pane in the Intel VROC GUI. In some cased, the Negotiated value may be 0.
- In VROC HII BIOS menu, After creating RAID 5 and setting the RWH value to Disable, if the value is changed to Journaling Drive, the BIOS returns an error mismatch message
- When installing Intel RSTe NVMe 5.5 onto a platform running Windows 7 64-bit, the device driver version reported for the filter driver, iaRNVMeF.sys, may report 8.8.8.8888 instead of the correct version
- When running Intel RSTe NVMe in a Pre-Purley platform with 48 drives that are configured in dual RAID 1/0 matrix array volumes duplicated until the maximum number of Arrays/Volumes is reached, rebooting the system may encounter a system failure.
- After Re-build operation is complete, if a Further “LOCATE”Operation is done on the same drive, after the LOCATE LED Blinking completes ( 10s), the Rebuild LED state comes back even though there is really no Re-build Operation indicated
- When upgrading to Intel VROC 5.4 from an older driver version may result in an existing RAID volume being incorrectly marked as "Initialized".
- VROC UEFI driver will poll for the hardware key even when VMD is disabled. This is adding increased boot times of up to 4 seconds when VMD is disabled.

Issues Resolved in Intel VROC 5.5PV:

- In the UEFI environment SATA RAID does not support Firmware Updates. This affects the Intel Firmware Upgrade Tool (FUT) used by customers when SATA RAID volumes cannot be updated to latest firmware
- When running in a platform where protocol errors (e.g.R_ERRs) can be encountered during I/O, Intel RSTe may inadvertently mark the drive, corresponding to the connection that encountered the error, as Failed when the drive is operational
- In the case where Windows 2008 R2 operating system is installed on a SATA device on the SATA or sSATA controller managed by RSTe and a HDD disk is unresponsive on the SCU (SAS) controller also managed by RSTe, the operating system may fail to boot until the unresponsive disk is removed
- When attempting to resume from an S4 power state with a degraded 3 drive RAID5 volume (as a result of a filed drive), may result in a system failure.
- With Windows 10 RS5 and RSTe SATA driver installed, the system does not resume from S4 correctly
- CSMI command to retrieve RAID information on SATA returns byte-swapped and truncated data
- VROC UEFI Drivers are not Backward compatible
- Having Windows installed on a 4-disk RAID 10 on the SATA controller managed by the RSTe driver, the disk or volume with the operation system may not be marked as the system volume. Consequently, the option to delete the volume is present. Deleting the system volume will cause a blue screen and delete any data on that volume
- Windows may stuck when one of the RAID5 member drive hot-removal during the RAID5 rebuilding
- Changes in UEFI 5.4 VMD Scan Code Require 5.4 VMD Windows version. No backward compatibility for Pre-OS
- On Microsoft Windows 7 64 bit operating system, if both power states S3 (sleep) and S4 (hibernate) are set to be initiated in that order, a blue screen may occur when Windows attempts to resume from S4.
- Changes in UEFI 5.4 VMD Scan Code Require 5.4 VMD Windows version. No backward compatibility for Pre-OS
- Using 5.4 VROC RSTCli64.exe tool in WinPE environment, the device cannot be seen
- When running in a configuration where a RAID volume is in a Rebuild state and an I/O stress test is running to that rebuilding RAID volume, the system may reboot
- In a configuration that includes both SATA and NVMe disks connected to the platform, a SATA disk may appear to have disappeared from both Windows Disk Management and the RSTe GUI after resuming from sleep state S3. This issue was reproduced when Windows 10 64 bit is installed on an NVMe disk connected to PCIe and VMD is not enabled; although it may not be limited to this exact configuration.
- When running in a 2 drive RAID 1 configuration where drive A has encountered many ECC error, removing Drive B and hot inserting a new Drive B can result in drive A becoming Failed (due to the number of Back Blocks) causing the RAID volume to fail. Drive A may then become inaccessible
- Certain Intel NVMe Devices with custom firmware versions display double device entries in the HII menu
- When VMD is disabled, Intel Virtual Raid on CPU menu option should not be visible in BIOS HII menu
- System power states testing S3 and enter S4 using power button to wake from S4 causes black screen hang up and sometimes get 0x1E BSOD.
- When running in a configuration where an Intel VROC RAID volume is spanning Intel VMD controllers, if one of the drives is removed the information of the drive being removed may not be properly propagated throughout the platform. Running a tool like "list disk" may still report the missing drive.
- When using the RSTe CLI tool in a WinPE environment or opening a command window within a Windows pre-install process using "Shift-F10", after using the RAID create command to create any RAID array using SATA disks on the SATA or sSATA controller, executing the RSTe CLI information command may fail to return any disk information.
- Some systems do not update the SlotStatus register PresenceDetectedState bit to indicate a hot plug has occurred. Intel VMD driver gets the interrupt when this Slot Status register is set. This does not occur in Linux because the PCIe Hot plug driver uses LinkStatus DataLinkLayerActive first and then SlotStatus PresenceDetectedState second, so this incorrect setting for the SlotStatus PresenceDetectedState register is ignored.
- In the case where Windows 2008 R2 operating system is installed on a SATA device on the SATA or sSATA controller managed by RSTe and a HDD disk is unresponsive on the SCU (SAS) controller also managed by RSTe, the operating system may fail to boot until the unresponsive disk is removed.
- When running on a system with Windows Server 2016, in a configuration where the system may repeatedly restart, a 0x9F System Error may be encountered.
- There are two entries on some customer platforms and when booting, the system may hang.
- On a platform that has HDD devices connected to the SATA controller and Windows 10 RS3 operating system installed on either a single HDD or multiple in a RAID volume made up of those HDD devices, the platform may hang when entering S4 hibernate sleep state if there is also an eSATA device connected to the same SATA controller
- Intel VROC UEFI driver is returning unexpected values for RouteConfig Conformance and ExtractConfigFunction for SCT 2.6 version UEFI Test cases
- In Windows OS with RAID 5, a new NVMe device is hot inserted and the UI allows user to select "Change mode" in RWH mode property and choose the system disk as Journaling Drive to Close RAID Write Hole. System Disk should never be allowed

To install this package please do the following:

- Save the downloadable package on an accessible location (such as your desktop).
- Unzip the file and enter the newly-created directory.
- Locate and double-click on the available setup file.
- Allow Windows to run the file (if necessary).
- Read EULA (End User License Agreement) and agree to proceed with the installation process.
- Follow the on-screen instructions.
- Close the wizard and perform a system reboot to allow changes to take effect.

About RST (Rapid Storage Technology) Drivers:

Once Intel's Rapid Storage Technology (RST) driver is applied, desktop and notebook systems will be able to manage the available storage (one or more drives) more easily.

And that's not all you should expect: updating the RST version can also bring about improved storage performance, lower power consumption, faster boot times, quicker data reads, as well as several other changes.

As far as applying this release is concerned, simply make sure your system configuration is compatible with this package, run the available setup, and follow the on-screen instructions for a complete installation. In addition to that, don't forget to perform a reboot to make sure that all changes take effect properly.

Even though other operating systems might be compatible as well, we do not recommend installing this package on platforms other than the specified ones.

With this in mind, click the download button, and get and apply the present version. Also, check with our website as often as possible in order to stay up to date with latest releases.