Intel Virtual RAID on CPU (Intel VROC) and Intel Rapid Storage Technology Enterprise (Intel RSTe) 5.0 Production Version

Transcription

1 Intel Virtual RAID on CPU (Intel VROC) and Intel Rapid Storage Technology Enterprise (Intel RSTe) 5.0 Production Customer Release Notes March 2017 Revision 1.0

2 Revision History Revision Description Date 0.8 Intel RSTe Beta Release August Intel RSTe VC2 Release October Intel RSTe VC3 Release November Intel RSTe PC Release December Intel RSTe VC4 Release February Intel RSTe 5.0 PV Release March Intel RSTe 5.0. PV Release Notes

3 By using this document, in addition to any agreements you have with Intel, you accept the terms set forth below. You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information. The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling , or go to: Code names featured are used internally within Intel to identify products that are in development and not yet publicly announced for release. Customers, licensees and other third parties are not authorized by Intel to use code names in advertising, promotion or marketing of any product or services and any such use of Intel's internal code names is at the sole risk of the user. Intel, Atom, Core, and the Intel logo are trademarks of Intel Corporation or its subsidiaries in the U.S. and other countries. *Other names and brands may be claimed as the property of others. Copyright 2017 Intel Corporation. All rights reserved. 1.0 Intel RSTe 5.0 PV Release Notes 3

4 1BContents 1 Introduction Overview Defect Submission Support Supported Operating Systems Purley BKC for Intel RSTe PV Supported Platforms Release Package Contents New In This Release Intel VROC Premium SKU and HW Activation Key Enforcement Limitations Windows 2012 R2 RAID Member Port Limitations Intel VROC Key Removal/Upgrade Limitation Drivers, Images and Utilities Known Issues in this Release Issues Fixed in PV Issues Fixed in PC Issues Fixed in Release VC Issues Fixed in Release VC Issues Fixed on Release Beta Intel RSTe 5.0. PV Release Notes

5 1 Introduction 1.1 Overview The Intel Virtual RAID On CPU (Intel VROC) Production (PV) release package is intended for all customers. This package contains the Production release version of the Intel VROC and Intel Rapid Storage Technology enterprise (Intel RSTe) SATA drivers for Windows* and UEFI. This release supports platforms built with the Intel C620 and C422 series chipsets. 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 SSD bootable RAID. 1.2 Defect Submission Support With this release, Intel will accept and process issues reported by customers via the Intel Premier Support (IPS) portal. To submit an issue, please use the Intel Premier Support (IPS) tool. Information, training and details can be found at the below website. Your local FAE can also provide you the necessary requirements to enable you to submit an IPS issue (also known as a case ) including an account setup if you do not already have one. When submitting a case, please include the following Fields in order to flag Intel VROC / Intel RSTe AE support for Purley Skylake SP platforms. - Case Information -> Product = Purley - Case Details -> Subject= <Add short title summary of issue> - Case Details -> Case Description = <add description and how to reproduce error) - Case Details -> Case Type = <fill in type of request> - Case Details -> Severity = <fill in severity of issue> - Case Details -> End Customer = <name of OEM> - Case Details -> Issue Source = IPS Cloud - Case Details -> Severity - Product/Project Info -> Case Category = TechnologyInitiative - Product/Project Info -> Case Subcategory = Intel Rapid Storage Technology enterprise (Intel RSTe) - Environment Details -> Purley-PCH = lbg-4 - Environment Details -> Purley-CPU = skx-2s (or skx 4s) - Environment Details -> BKC or SW = Supported Operating Systems Only 64bit OS support is available for the following OS versions Windows* 7 SP1 (supported on Purley Workstations only) Windows* Server 2012 R2 Enterprise (supported on Purley Server platform only) Windows* 10 (supported on Purley Workstations and Basin Falls platforms only) Windows* Server 2016 Enterprise (supported on Purley Server platform only) 1.0 Intel RSTe 5.0 PV Release Notes 5

6 1.4 Purley BKC for Intel RSTe PV ***Validation uses the latest Purley BKC ingredients. Consult the latest release of Purley BKC to align with all platform ingredients NOTE: This Intel RSTe PV drop may not be included in all Purley BKC packages. 1.5 Supported Platforms Intel Xeon E5/E7 SP Purley Intel Xeon processor E5 / E7 SP (Sky Lake) product family with Intel C620 series chipset Intel Xeon SP Basin Falls Intel Xeon processor -SP (Sky Lake) product family with Intel C422 series chipset family Note: For answers to questions concerning the Intel RSTe C620 and C422 series chipset and/or to obtain other technical collateral, please contact your local Intel FAE. 6 Intel RSTe 5.0. PV Release Notes

7 2 Release Package Contents 2.1 New In This Release This release of Intel RSTe PV introduces the following: 1. The Intel VROC f6 folder name and files have changed from iarvmd to iavroc. For example, the Intel RSTe 5.X Beta / Intel VROC f6 folder for Microsoft* Windows* 7 was named iarvmd.free.win7.64bit.5.x and in this PV release it is named iavroc.free.win7.64bit.5.x. All the files within the folders have also been renamed from iarvmd to iavroc including the Intel RSTe driver. 2. An updated Installer; version Hybrid Sleep is supported for platforms that support S3 and Microsoft* Windows* Intel VROC Premium SKU and HW Activation Key Enforcement With this release, we no longer provide a version of the Intel VROC PreOS UEFI driver package that by-passes HW activation key enforcement (Super SKU). You will need to connect either an ES or QS Intel VROC key on the board to test standard or premium features. 2.3 Limitations Windows 2012 R2 RAID Member Port Limitations For Boot Volumes on ports with Intel RSTe SATA RAID Boot volumes, devices must be attached to any of the first 6 ports. Ports greater than 6 should not be used for System RAID volume members Intel VROC Key Removal/Upgrade Limitation On Windows 10 Fast Startup is enabled by default. Disable Fast Startup prior to removing/upgrading the Intel VROC HW key. OR, perform a complete reboot when removing/inserting a HW key when Fast Startup is enabled. 1.0 Intel RSTe 5.0 PV Release Notes 7

8 2.4 Drivers, Images and Utilities List of Modules supported on Intel Xeon based platforms delivered with Intel VROC for this release Feature Notes Intel VROC UEFI Driver version o efi_standalone_rste_rs /VMDVROC_1.efi (HW key enforcement in effect) Note: With this release, we no longer provide the super SKU UEFI driver version Intel UEFI Drivers Intel VMD UEFI version o VMDVROC_2.efi Note: All of these images are required and intended to support Intel VMD and Intel RSTe SATA functionality as a combined installed package. Intel RSTe SATA Driver version o SataDriver.efi Intel RSTe ssata Driver version o ssatadriver.efi Legacy OROM Images Intel RSTe SATA OROM pre-os image version o SataOrom.bin Intel RSTe ssata OROM pre-os image version o ssataorom.bin Intel RSTe Windows* Drivers Intel RSTe Windows GUI version Intel VROC Windows Installer Package version o SetupRSTE.exe (Multi-lingual) Intel VROC Windows F6 Driver version o iavroc.sys Intel RSTe Windows F6 Driver version o iastore.sys (SATA) o iastorb.sys (ssata) o iastorf.sys (Filter driver - Windows* 7 only) 8 Intel RSTe 5.0. PV Release Notes

9 Feature UEFI Based RAID Configuration Utility Notes Intel VROC version o RCfgRSTeRS.efi Intel RSTe SATA version o RCfgSata.efi Intel RSTe ssata version o RCfgsSata.efi Note: Secure Boot must be disabled to use this tool DOS Based RAID Configuration Utility Intel RSTe SATA version o RCfgSata.exe Intel RSTe ssata version o RCfgsSata.exe UEFI Based Comply Utility Intel VROC version o RcmpVMD.efi Intel RSTe SATA version o RCmpSata.efi Intel RSTe ssata version o RCmpsSata.efi Note: Secure Boot must be disabled to use this tool DOS Based Comply Utility Intel RSTe SATA version o RCmpSata.exe Intel RSTe ssata version o RCmpsSata.exe UEFI based SATA SGPIO/LED Test utility Intel RSTe SATA version o LedToolSata.efi Intel RSTe ssata verison o LedToolsSata.efi Note: Secure Boot must be disabled to use this tool UEFI based Intel VROC LED Test utility Intel RSTe VROC verision o LedToolVMDRSTeRS.efi Note: This tool can be used to exercise LEDs for NVMe disks behind VMD 1.0 Intel RSTe 5.0 PV Release Notes 9

10 Feature UEFI Based Clear Metadata Utility Notes Intel RSTe SATA version o RClrSata.efi Intel RSTe ssata verison o RClrsSata.efi UEFI Based Intel VROC HW Key Checker Intel VROC Activation Key Checker o HWKeyCheckRSTeRS.efi Note: This tool will check for the presence and type of the HW key 10 Intel RSTe 5.0. PV Release Notes

11 3 Known Issues in this Release This section outlines the known issues that are being actively worked on with the Intel RSTe 5.0 PV release Windows* Device Manager May not Detect Hot-removing of RSTe Managed NVMe Disks / RSTe_ On a Windows* system, when hot-removing RSTe managed NVMe disks, the Device Manager may not show the disks as removed. Use the Intel RSTe GUI to detect Hot removal of NVMe devices. All RAID Member Disk LEDs Blinks On Rebuild / RSTe_ On a Windows* system that has a RAID volume in rebuilding status, the fault LED for all RAID member disks will blink along with the activity LEDs. This effects only RSTe managed SATA devices. The planned change is to have only the RAID volume member disk that is being rebuilt blink the fault LED, not all of the RAID volume member disks. VMD Windows NVMe Compare command cannot be passed through to NVMe SSDs behind Intel VMD / NSD-2688 Intel VROC 5.0 PC On NVMe SSDs that support the NVMe Compare Command, an error status is returned on devices connected to VMDenabled ports None at this time 1.0 Intel RSTe 5.0 PV Release Notes 11

12 Write performance is too low when use 6 SSDs or HDDs to build Intel SATA RAID 5 volume(rste driver ) / RSTe_5_0PV Rebuild of RAID 5 volume with 6 member disks creates very low performance during Writes None at this time 12 Intel RSTe 5.0. PV Release Notes

13 4 Issues Fixed in 5.0 PV Stripe Size in RSTe UI May Differ From the List in the BIOS / RSTe_ During creating a RAID volume in the RSTe UI, the Stripe size options listed in the Advanced section may differ from the options listed in the RSTe VROC HII Fixed in release PV VMD UEFI Assert when booting installation from Legacy CD-ROM NSD VMD UEFI Driver When booting to Legacy CD ROM (CSM enabled), VMD driver error occurs and platform freezes. Fixed in VMD UEFI Driver VMD UEFI driver does not discover devices behind both switch and direct connect at the same time NSD VMD UEFI Driver With switch connected devices AND directly connected devices to the backplane, not all devices are visible. These are on separate CPU VMD domains, so should all be visible. Fixed in VMD UEFI Driver 1.0 Intel RSTe 5.0 PV Release Notes 13

14 Missing register mark on Intel RSTe SATA Controller in BIOS / SATA OROM SATA Pre-OS is missing Intel (R) mark in the menu string Fixed in Release Win2016 can't be installed when NVMe drive connected in different CPU Win2016 can't be installed in the scenario when two NVMe drives connected in different CPU and only one VMD be enabled Fixed in Release NVMe hot-plug may not work when the drive are not plug/exit before OS boot If OS boot without NVMe connected hot-plug/removal may not work Fixed in Release 14 Intel RSTe 5.0. PV Release Notes

15 System BOSD after load F6 driver when install Win10 in Third Party SSD / Installation with win10 with Third Party drive BSOD may happen after load F6 driver. Fixed in Release ACPI action abnormal on Win10 RS1 OS with secure boot enable after installing IRSTe driver / Windows Secure Boot needs signed driver, and if Secure Boot is enbabled, abnormal actions are observed Fixed in PV Release memory leak when running mass storage test tools on 5 SATA SSD RAID / SATA trend of increasing Pool Nonpaged memory and decrease in Available memory Fixed in Release 1.0 Intel RSTe 5.0 PV Release Notes 15

16 BSOD and RSTe UI hangs with 4 disk RAID 5 on Surprise Hot Plug during IO PC Create a RAID 5 and begin sending IO to the volume then surprise hot plug a disk notice that the UI will hang and then the system will BSOD Fixed in Release System halt on starting windows screen or response is slow in OS after installing Intel RSTe driver in RAID mode PC SATA only - In RAID mode both Windows* 7 and Windows* 10 halt on install or response time is too slow when install is successful and system reboots Fixed in Release Cannot access ControllerName2 Protocol in VMD/VROC UEFI driver / NSD PC ControllerName2 Protocol is not present in Intel VMD/VROC HII menu Fixed in VMDVROC UEFI Driver Release 16 Intel RSTe 5.0. PV Release Notes

17 System Boot Volume has Delete volume Option When degraded PC In a scenario where an Operating System is installed on a NVMe boot RAID volume and that volume changes to status Degraded, the Intel RSTe GUI may present the Delete volume actionable link. Initiating this function will delete the volume and any data will be irrecoverable. Fixed in release RSTe Installer does not delete files for Windows* 7 when uninstalling RSTe PC When using the installer to uninstall the previous version of RSTe in Windows* 7 OS driver files are not deleted from destination folder as expected Fixed in installer package for release System Boot Volume has Delete volume Option When degraded PC In a scenario where an Operating System is installed on a NVMe boot RAID volume and that volume changes to status Degraded, the Intel RSTe GUI may present the Delete volume actionable link. Initiating this function will delete the volume and any data will be irrecoverable. Fixed in Intel RSTe 5.0 PV Release Notes 17

18 Device Not Detected after Loading RSTe F6 Driver the first time need to click rescan button PC When installing OS using F6 RSTe driver if the user clicks the "load Driver" no devices are discovered unless the "rescan" button is clicked another 1 or more times. Fixed in (Or, Click "rescan" button during OS load. No workaround need in PV release) Intel VMD RAID system hangs up with Black Screen debug code 99 when resuming from S / NSD PC Some NVMe devices do not contain an extended capability field for identify device information the Intel NVMe driver may time out because the device must be queried for device information on an S3 resume Fixed in SATA - installer fails on Win10 with platform not supported message on Basin Falls platform in AHCI mode Basin Falls Beta Basin Falls AHCI device ID is not included in early 5.0 Basin Falls release Fixed in release Intel RSTe 5.0. PV Release Notes

19 no signed device drivers were found occurs when loading VMD Win10 driver PC VMD enable and RAID created in HII. Loading F6 driver then choosing driver in folder, an error occurs "no signed device drivers were found. The reason for this is that you cannot load VMD driver on windows 10rs1 because manufacture section had been wrongly written Re-scan. Fixed in release VMD Windows - BSOD A0 during S4 with OS on Certain M.2 NVMe drives with Serial Number Capability missing NSD Some 3 rd party NVMe SSDs are missing the serial number capability field required by the VMD NVMe driver to execute properly during crashdump mode. Fixed in release VMD Windows BSOD during Windows* 10 install using certain Third Party NVMe SSDs NSD Some 3rd party NVMe SSDs are causing BSOD from NVMe during copying installation files on Microsoft Windows* 10 RS1 install Fixed in release 1.0 Intel RSTe 5.0 PV Release Notes 19

20 UI - Incorrect disk controller association after switching disk between controllers SATA to ssata When switching a disk from the SATA controller to ssata controller, the disk may still be listed under the SATA controller in the RSTe UI. Close and re-open the RSTe UI. Fixed in release NVMe SSD May Not be Detected After Loading RSTe f6 Driver / In the Windows* 10 pre-install phase, a NVMe SSD that resides behind VMD may not be detected after loading the RSTe F6 driver. Fixed in release Cannot configure IASM using loopack host name (localhost) For standalone configuration, it is not possible to configure Intel ASM with use of loopback hostname (localhost). Fixed in release 20 Intel RSTe 5.0. PV Release Notes

21 5 Issues Fixed in PC Int./Ext. Reference No: Description NSD-2262, VMD Windows Not all Drives may be showing in RSTe EFI HII when Connecting PCIe NVMe Devices in a Hot Swap back Plane and a Backplane Card Reported by RSTe validation but not able to reproduce with latest builds WORKAROUND: No Longer Occurs RAID WRITE Hole volume is still dirty after recovery - parity INIT unsuccessful. Issue only occurs on dual Linux/Windows boot - when a data RAID member PCIe device is force failed, the volume partition is not recovered as expected NSD-2124 A Blue Screen Event (BSOD) may occur during resume, if a boot disk changes position in PCI slots during hibernate If a user hot plugs an NVMe device during hibernation, this causes resources to change and the PCI address of the boot device can be changed causing the system to have a Blue Screen Event (BSOD) during resume. The PCI address can be changed by moving the boot device to another slot, removing a data disk from one of the slots or inserting a data disk in an empty slot during hibernation *See Hot-Plug limitations in this release NSD-2281 VMD Enabled with Serial Cable 24x JBOD enclosure does not see all SSDs Not all devices within the JBOD enclosure can be seen when attached to a PCIe Slot with VMD enabled. * in BIOS setup for VMD-enabled PCIe slot. This will expose more devices in a JBOD enclosure (may not show all): On VMD PStack#, change the following defaults to: ->CfgBar Size[27] ->CfgBar attribute <64-bit prefetchable> ->MemBar1 Size [26] 1.0 Intel RSTe 5.0 PV Release Notes 21

22 ->MemBar1 attribute <32-bit non-prefetchable> Not all Drives may be showing in RSTe EFI HII when Connecting PCIe NVMe Devices in a Hot Swap back Plane and a Backplane Card In a configuration where there are 4 NVMe disks in a Hot Swap back Plane (HSBP) connected to a switch off PCIe slot 2 and 4 more NVMe disks connected to a backplane add-in-card Intel VROC HII shows 7 PCIe Devices instead of 8 after connecting 4 in Hot Swap Back Plane (HSBP) using Retimer card in PCIe slot 2 and a backplane card in PCIe slot 4 with 4 PCIe devices Issue only seen in BIOS RSTe VROC HII. *: Refer to RSTe GUI to view correct number of NVMe SSDs NSD-2393 VMD Intel VROC for Windows - Not all 3rd party NVMe drives are visible when VMD is enabled This issue is related to some NVMe SSD s msix table size is 0x81. Intel VMD-enabled Windows driver is not handling msix table size more than (0x20) / The Intel RSTe Option ROM UI May not Appear for ssata Controller The Intel RSTe legacy Option ROM may not show up in a configuration where 2 HDDs are connected to the ssata controller in RAID mode. It does not affect the Intel RSTe OROM for the SATA controller System Boot Volume has Delete volume Option When degraded In a scenario where an Operating System is installed on a NVMe boot RAID volume and that volume changes to status Degraded, the RSTe GUI may present the Delete volume actionable link. Initiating this function will delete the volume and any data will be irrecoverable. 22 Intel RSTe 5.0. PV Release Notes

23 6 Issues Fixed in Release VC3 Int./Ext. Reference No: Description / Intel RSTE GUI Does Not Show Negotiated Link Speed for PCIe NVMe Devices In the Intel RSTe GUI on a platform having NVMe devices connected to PCIe managed by VMD, the Negotiated link speed text string in the Disk Properties pane is missing / / NSD-2377 Memory corruption / NULL de-reference in VMDVROC_2.efi entry point When VMDVROC_2.efi is loaded, its entry point code will write the value 1 to a de-reference of a NULL pointer / Memory leak with 4 or more SSDs in RAID0 on Windows* 10 On a system running Windows* 10 from a single HDD, running performance based tools on a RAID 0 consisting of SSDs may yield results showing a trend of increasing pool non-paged memory and decrease in available memory / Copy compare command causes degraded 5 RAID array, remove faulty disk, activate LED, system BSODs / RAID slow format issue / No Change type Add disk button for RAID0 Migration prompt in IRST UI with 2TB HDDs / BSOD 1E iastore.sys rebuilding SSD RAID5 Win10_ / RSTe_ _VC2 installer does not install the driver on SATA most of the time / System show BSOD D1 pointing to Intel RSTe driver continuously with Driver Verifier enabled / Auto Rebuild RAID 5 Array Does not Begin 1.0 Intel RSTe 5.0 PV Release Notes 23

24 7 Issues Fixed in Release VC2 Int./Ext. Reference No: Description / Intel RSTE GUI Does Not Show Negotiated Link Speed for PCIe NVMe Devices In the RSTe GUI on a platform having NVMe devices connected to PCIe managed by VMD, the Negotiated link speed text string in the Disk Properties pane is missing Cannot create RAID on SATA Cannot create raid 5 volume with JD driver using CLI Incorrect behavior when trying to rebuild degraded volume with too small disk UI help lack of information about creating R10 with keeping data is possible up to ss 64kB UI fails to open after disable support for used volume type in BIOS Installer: Add embedded manifest file Windows 10 rs1 get BSOD on resuming from S Hover message to hide or show volume Properties contains wrong message UI fails to open after disable support for used volume type in BIOS Wrong pop up message above tray icon after platform restart R1 stripe size info is shown as 128kB in CLI and UI system report BSOD during Windows boot with RAID volume containing bad blocks BSOD when creating RAID10 with keep data and 128kB strip size CLI returns wrong exit code after attempting to create RAID volume with non-existing device Disk with the SMART Event has Format Ok(0) state in EFI / BSOD D1 on Win10 after 254 S4 cycles on Windows Intel RSTe 5.0. PV Release Notes

25 99999 RSTe GUI Does Not Start If VMD is Enabled and No VMD Devices Connected On a Purley based platform which includes VMD support and includes any disks on the SATA or ssata controller used as the operating system boot device, if there is any PCIe NVMe devices connected to the platform and/or VMD is enabled in the BIOS, the Intel RSTe GUI will fail to open. This is not an issue so long as there is 1+ PCIe Devices connected to the platform. Note: by default, VMD is disabled in the BIOS / BSOD D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL Installing Win7x / Initializing or Formatting a RAID volume Consisting 2TB or Greater Disks may Result in an Error In a configuration where the Windows* operating system is installed on a hard drive and a RAID 1 volume is configured using 2x 2TB or greater sized hard drives, attempting to initialize the RAID 1 volume logical drive in Windows* Disk Management may result in an error. Consequently, the initialization fails to start / Creating a RAID volume Using 2TB or Greater Disks may Result in an Error In a configuration where the Windows* operating system is installed on a hard drive, attempting to create a RAID volume using 2x 2TB or greater sized hard drives may result in an error. The RAID volume fails to be created / Windows* OS Installation process Fails to Identify RAID Volume consisting of 2TB or greater Disks The Windows* hardware selection window as part of the beginning of the operation system installation process may not identify a RAID volume as qualifying boot device which consists of 2TB or greater sized disks / BSOD D1 May Occur When System goes into S4 State Initiating S4 having the Windows* operating system on a single HDD on either the SATA or ssata controller may result in a NSOD D Intel RSTe 5.0 PV Release Notes 25

26 8 Issues Fixed on Release Beta Int./Ext. Reference No: / NSD-2239 Description Hot plugging an NVME drive to rebuild a RAID 1 May Cause BSOD and System Reboot. In a configuration where a RAID 1 volume is in Degraded status, hotplugging a different clean NVMe disk in order to rebuild the degraded volume may result in a BSOD. Consequently, the system will automatically reboot. Details: NVMe drive on Port 1 works correctly but when NVMe drive on port 2 is surprise removed nothing will happen in Windows Disk Management. The drive still appears. In the RSTe software the drive is removed. But when drive is re-inserted the system will wait and then reboot itself / Device manager may not Show Hot-removed and/or Inserted NVMe disks While booted into the operating system, disconnecting or removing an NVMe disk will not be shown In Windows* Device manager. The NVMe disk will still appear of removed. An NVMe disk that is inserted will not be shown in Windows* Device Manager / Even Viewer may List RSTe Service errors After installing RSTe 4.3 PV, the event viewer may list errors relating to the RSTe driver service IAStordataMgrSvc 26 Intel RSTe 5.0. PV Release Notes