ESRT2_Windows_signed_DRV_v17.01.2016.0216_Readme.txt Driver File Contents (ESRT2_Windows_signed_DRV_v17.01.2016.0216_r3.zip)

This release note and the software that accompanies it are copyright (c) 2015, Intel Corporation or its suppliers, and may only be installed and used in accordance with the license that accompanies the software.

This Software is furnished under license and may only be used or copied in accordance with the terms of that license. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. The Software is subject to change without notice, and should not be construed as a commitment by Intel Corporation or its suppliers to market, license, sell or support any product or technology. Unless otherwise provided for in the license under which this Software is provided, the Software is provided AS IS, with no warranties of any kind, express or implied. Except as expressly permitted by the Software license, neither Intel Corporation nor its suppliers assumes any responsibility or liability for any errors or inaccuracies that may appear herein. Except as expressly permitted by the Software license, no part of the Software may be reproduced, stored in a retrieval system, transmitted in any form, or distributed by any means without the express written consent of Intel Corporation.

==========================
Supported RAID Controllers
==========================
This download provides support for Intel(R) C232, C236, C600, ICH9R, ICH10R, S5000 (ESB2), and 3420 PCH chipsets on both AHCI Capable SATA Controller and SATA/SAS Capable Controller in Intel(R) Embedded Server RAID Technology 2 (ESRT2) mode.   
To determine if your server system is compatible with ESRT2, go to https://serverconfigurator.intel.com/  and review the THOL (Tested Hardware Operating System) for RAID/ RAID SW. 

Please verify that this package has been tested with the RAID Controller and Operating System combination you have chosen to use by checking the drivers web page for your controller at http://support.intel.com.

===================
Package Information
===================
Driver Version = v17.01.2016.0216 
OS supported = Microsoft* Windows* 10, Windows* Server 2012R2 (x64), Windows* 8.1 (x86 & x64), Windows* Server 2012 (x64), Windows* 8 (x86 & x64), Windows* 2008R2 (x64), Windows* 7 (x86 & x64), Windows* 2008 (x86 & x64), and Windows* Vista (x86 & x64).

These drivers are WHQL certified, and all required .cat files for installation are included in the appropriate directories. 

==========
Attention!
==========
None

=======================
Contents in the package
=======================
This package includes subdirectories for each version of Windows* that is supported. Each of these directories contains the files necessary to support installation for that version of the Windows* operating system. 


==================
Known Restrictions
==================
1. Intel(R) ESRT2 support UEFI functionality on only Intel Grantley generation servers and later products.  UEFI is not supported on Intel Romley and older generation server products.

2. The C600 chipset SATA/SAS Capable Controller does not support ODD devices. No Optical Devices should be connected to the SATA/SAS controller at any time (ODD devices are not supported in any mode), but the onboard AHCI capable ports do support ODD devices (in all modes).

3. RAID 5 feature is enabled only if the appropriate Intel(R) RAID Upgrade Key is present in the system. 

4. A RAID 5 logical drive can recover from a single drive failure by reconstructing missing data from the data and parity contained on the remaining drives. The assumption underlying this ability is that the data in the remaining drives is consistent. This assumption becomes invalid if there is a power loss during write operation(s). If there is a loss of power during a write operation, data inconsistencies may occur because data and parity writes may have completed only partially. After subsequent reboot the logical drive has inconsistent data on that particular stripe. If a drive were to fail at this point, missing data (for the inconsistent stripe alone) cannot be reconstructed from remaining drives. To correct an inconsistency, the drivers starts a back ground initialization (BGI) at reboot. While BGI is in progress, the inconsistent stripe(s) are vulnerable to drive failure. One way to avoid this window of vulnerability is to run check consistency on the logical drive using the BIOS utility. Another way is to prevent an unplanned shutdown (e.g. using UPS).

5. The LITE-ON SH S752K model CD/DVD ROM device does not respond to 0x55 & 0x51 MMC commands properly. The device hangs when these commands are issued multiple times. The driver resets the device when it hangs; but the reset adversely affects DVD burning. This behavior can be consistently observed using K3B DVD burning software. K3B aborts DVD writes when 0x55 is failed and device is reset.

6. RAID 5, by its very nature, cannot tolerate double failures. The double failure can be a combination of a single drive failure and either additional drive failures or an unplanned power failure in the RAID system. Unplanned power failures can include but be not limited to, loss of power source or an unusual system shutdown. Unplanned power failures while there are medium errors on the drives is also considered as a double failure condition.

7. Multiple drive failures would result in a data loss condition. A single drive failure combined with any additional unplanned failure can cause loss of data integrity. To avoid loss of data integrity for the power failure case, it is highly recommended to provide an uninterrupted power supply to the server to protect the RAID 5 subsystem during the event of a degraded or rebuilding state. Medium errors on the disks, combined with an unplanned power failure can also cause loss of data integrity, but this occurrence would be very unlikely.

8. Hotplug limitation in runtime 
If the user pulls out or plugs in a drive when the Intel(R) ESRT2 OpROM has completed its execution, and before the OS driver is loaded (like DOS shell, or AHCI?Ctrl-M screen, etc), the OpROM's runtime code displays a message and force reboot the system to avoid configuration losses or data corruption. 

9. Maximum two storage controllers supported 
If the user tries to enable SATA/SAS Capable Controller and AHCI Capable SATA Controller on the C600 chipset in Intel(R) ESRT2 mode concurrently, and then inserts any external storage controller (for example, a Hardware RAID adapter), the last controller in the boot sequence might not be able to POST due to limitations in pre-OS memory utilization. 

10. Windows installation limitation in RAID Mode: 
If Windows installation is done on a drive connected through the AHCI capable SATA Controller, make sure SATA/SAS Capable Controller is disabled in BIOS. After completion of installation, the SATA/SAS Capable Controller can be enabled in BIOS. If both controllers are enabled in Intel(R) ESRT2 mode, the installation may fail.

11. BIOS communicates the presence/absence of specific Intel(R) RAID C600 Upgrade key (RKSATA4R5, RKSATA8R5, RKSAS4R5 and RKSAS8R5) using configuration data on disk (DDF) and through device registers from BIOS. If driver does not read a valid DDF, it will disable R5 creation. The driver may not see valid DDF if (A) user does not configure using BIOS Ctrl+M; or (B) if no drives were present at the boot time and all the drives were hot-inserted after OS is booted. In both cases, the user must create an initial configuration using BIOS Ctrl+M utility.


=========================
Installation Instructions
=========================
This updated driver can be applied using the normal OS installation options.

The following procedure describes how to install Windows 2008r2/2008/7/Vista system onto RAID logical disk:

1. Copy the driver files to a removable media, such as USB flash drive, CD-ROM, or floppy disk
2. Create RAID logical disk(s) using ESRT2 OpROM Config Utility (during POST).
3. Boot Windows installation disk. Follow instructions on screen until below step is reached.
4. At "Which type of installation do you want?" screen, select "Custom (advanced)"
5. At "Where do you want to install Windows?" screen, select "Load Driver"
6. Install the removable media with the driver files (extracted in step 1)
7. Select "Browse" and locate the folder with the driver files and then select "OK"
8. Select "Next". There may be a 1-2 minute delay as drivers are loaded.
9. Select "Drive options (advanced)" to customize partitions - if necessary
10. Select "Next" to continue with the installation
11. There are several reboots during installation - ensure that the selected RAID array is the boot device during every reboot.

================

Installation of the driver after the operating system is installed:

1. Boot into applicable Windows OS. Click the Windows Start button and select Settings.
2. Click Control Panel.
3. Select Adapter.
4. Select the Drivers tab.
5. Scroll down the list until the appropriate selection for your system which contains the Intel(r) Embedded RAID Technology II and for your operating system displays, then click <OK>.
6. Select it, then remove it by clicking the Remove button.
7. Click the Add button.
8. Select the Have Disk button.
9. Insert the diskette into the floppy drive.
10. Select drive letter A: and click on <OK>.
11. Select Intel(r) Embedded RAID Technology II and click OK.
12. After Windows* copies the driver, reset the system.


=============
Fixes/Updates
=============
Version 17.01.2016.0216 (SWR 1.50 patch2)
  Defects (12)
	SCGCQ00907674 - (Resolved) - Restore fault LED state after wake up from sleep in Linux
	SCGCQ00917933 - (Closed) - MSM on SWR Reading Temperature of 0C for SATA SSDs and HDDs
	SCGCQ00940998 - (Resolved) - Creating a VD from an offline DG from SWRAID is allowed
	SCGCQ00941811 - (Resolved) - Win10 WHQL TEST SCSI_COMPLAINCE TEST 2.0 failure on SWr
	SCGCQ00993098 - (Closed) - MegaSR: IO Program fails with Data Compare Error on drive E.
	SCGCQ01015748 - (Resolved) - 4K Vd created in uEFI version 04080000 and 17.01.2015.1228 OS driver not detected in previous versions.
	SCGCQ00934949 - (Resolved) - SWRAID : Setting Controller time using storcli returns Failure
	SCGCQ00926280 - (Resolved) - pd firmware download for >2mb images fails in linux.
	SCGCQ00929514 - (Resolved) - Not detect SMART error again after disconnecting SMART occurred HDD once
	SCGCQ00939840 - (Resolved) - SWRAID : Two messages in MSM for BGI resumed after reboot
	SCGCQ00916736 - (Resolved) - Rebuild resume from the way after making force offline and online of source disk during rebuild
	SCGCQ01030238 - (Resolved) - Rebuild started on PD log doesn't appear
  EnhancementRequests (1)
	SCGCQ00980249 - (Closed) - Addressed the Bad Block Table Migration Issue in SWR from non 4K supported configs to 4K supported configs
  CSETActivities (1)
	SCGCQ00933317 - (Port_Complete) - CSCuw39376: SWRAID : When a PR is aborted AEN displayed as PR complete
  BaseCMActivities (11)
	SCGCQ00990180 - (Completed) - UndoActivityChangeSet: Subtractive merge of BaseCMActivity SCGCQ00990169
	SCGCQ01004741 - (Active) - 1.50 driver release checkins. ver: 17.01.2016.0108
	SCGCQ00923282 - (Completed) - 1.50 SLES 11 sp4 patch release checkin.
	SCGCQ00942212 - (Completed) - 1.50 Window 10 release checkin.
	SCGCQ00990888 - (Completed) - UndoActivityChangeSet: Subtractive merge of BaseCMActivity SCGCQ00990182
	SCGCQ00997998 - (Completed) - SWR-1.50- 12192015 Driver version change
	SCGCQ01000514 - (Active) - 1.50 driver release checkins
	SCGCQ01030507 - (Completed) - SWR OS driver version 17.01.2016.0216
	SCGCQ00927124 - (Completed) - 1.50 Linux patch release checkin.
	SCGCQ00952922 - (Completed) - SWR-1.50- 11182015 -Driver version change
	SCGCQ00990169 - (Completed) - SWR-1.50- 12082015 Driver version change

Version 17.01.2015.0915 (SWR 1.50p)
  Defects (8)
	SCGCQ00853141 - (Resolved) - WG: Patrol Read GET in SWR does not fetch the latest data, issue related to events
	SCGCQ00912382 - (Resolved) - RAID 1 VD is offline with 4K drives when auto Resume Disabled in Ctrl Proprieties
	SCGCQ00828858 - (Closed) - Cannot update WD FW in ESRT2 using CMDTool2 8.07.16 with ESRT2 driver version 15.04.2013.1016
	SCGCQ00871357 - (Closed) - Software RAID buffer IO error observed when initialization started on VD
	SCGCQ00852496 - (Closed) - SWR controller is not detected even after providing driver during OS installation
	SCGCQ00883797 - (Closed) - Display wrong controller name with one of device ID (GreenGem2 ID)
	SCGCQ00841482 - (Resolved) - Hundreds of entries are filling up dmesg with message: unable to retrieve proper sense data. For particular SATA DVD
	SCGCQ00878934 - (Closed) - blinking amber in HD slot 2 and 3 after wake up from Windows 7 with ESRT2 RAID
  EnhancementRequests (8)
	SCGCQ00882009 - (Closed) - Enabling R5 in uEFI mode by default for Intel Greenlow server
	SCGCQ00902264 - (Implemented) - Enabled RAID 5 key detection feature in uEFI
	SCGCQ00840761 - (Implemented) - Add PNP ID for OEM SunrizePoint system
	SCGCQ00840764 - (Implemented) - Add PCI IDs for FTS skylake server
	SCGCQ00859715 - (Opened) -
	SCGCQ00840766 - (Implemented) - Add PNP ID for Intel "Greenlow Silver Pass"
	SCGCQ00862701 - (Implemented) - RAID key detection changes based on new Greenlow PCH GPIO changes
	SCGCQ00869190 - (Implemented) - PNP ids for NEC Grantley and Greenlow Servers
  CSETActivities (2)
	SCGCQ00905415 - (Port_Complete) - SWR: Storcli: Able to delete the OS VD without force.
	SCGCQ00887371 - (Active) - Software RAID buffer IO error observed when initialization started on VD
  BaseCMActivities (13)
	SCGCQ00846227 - (Active) - API changes to support write verify during cache flush
	SCGCQ00866841 - (Completed) - 1.50 Pre-Alpha Release check-ins
	SCGCQ00869457 - (Completed) - add comment in device id list.
	SCGCQ00882633 - (Completed) - Script change to accommodate new Driver signature.
	SCGCQ00887708 - (Completed) - 1.50 RC build check-in
	SCGCQ00910095 - (Completed) - 1.50 -Driver Version change [0901-2015]
	SCGCQ00905460 - (Completed) - 1.50 win 10 release check-in
	SCGCQ00882614 - (Completed) - 1.43 point release version check in.
	SCGCQ00867122 - (Active) - Changing the uEFI TimeStamp from 14.x to 15.x
	SCGCQ00869408 - (Completed) - controller type wrongly checked in as PCI-X instead of PCI-E
	SCGCQ00917472 - (Completed) - 1.50 0915 release checkins
	SCGCQ00842296 - (Completed) - 1.50 test build check ins
	SCGCQ00880287 - (Completed) - 1.50 beta release check-in

Version 16.03.2015.0703 (SWR 1.43 patch3)
	SCGCQ00871357 (DFCT) - Software RAID buffer IO error observed when initialization started on VD
	
Version 16.03.2015.0519 (SWR 1.43 patch2)
	SCGCQ00695917 (DFCT) - For Grantley server the sata controller should display host interface type as PCI_E
	SCGCQ00861206 (DFCT) - On hot plugging, SAS SSD gets detected as normal SAS HDD drive

Version 16.03.2015.0324 (SWR 1.43 patch)
	SCGCQ00823666 (DFCT) - STOP ERROR happens after deleting LD by RAID utility
	SCGCQ00833143 (DFCT) - While creating second DG on SWR, getting BSOD and system restarts
	SCGCQ00837456 (DFCT) - PD failed when medium error is detected during Check Consistency

Version 16.03.2014.1127 (SWR 1.43)
 Defects (25)
	SCGCQ00653283 - (Resolved) - While PR is running on degraded VD , IF We start the Rebuild on OFFLINE/FAILED pd from MSM, getting error message
	SCGCQ00674890 - (Closed) - 1.42 EFI Dual Controller reconnect issue
	SCGCQ00681772 - (Closed) - SWR_1.42_pa1: Using SLT we are able to set the PR Rate to more than 100
	SCGCQ00712585 - (Closed) - SWR_1.43: Implement Hibernation
	SCGCQ00715773 - (Closed) - Different sector size PDs can be hot-plugged in to a VD
	SCGCQ00718392 - (Closed) - While PR is running Rebuild can be started, PR goes to pause
	SCGCQ00657407 - (Closed) - SWR_1.42 - BIOS version differs in OPROM and HII
	SCGCQ00713085 - (Closed) - Remove PnP ID which was added as workaround to support 4K Drives
	SCGCQ00720583 - (Closed) - For 4TB Drive Used Capacity was showing Wrong value in MSM As well as Cli application
	SCGCQ00655451 - (Resolved) - SWR 1.42 Driver version change
	SCGCQ00655724 - (Closed) - SWR driver coverity defects fixes
	SCGCQ00666911 - (Closed) - Under certain condition Hot plugged SATA DVD ROM drive not displayed properly
	SCGCQ00718448 - (Closed) - R5 and SAS PD support enabled by default for development
	SCGCQ00712657 - (Closed) - Post boot VDs created using 512 sector size PDs disappears
	SCGCQ00712581 - (Closed) - Degraded R5 VD with 4K sector size PDs results in data corruption
	SCGCQ00713096 - (Closed) - Review comments
	SCGCQ00724011 - (Closed) - blank cursor blinking when perform the delete vd and start init operations using EFI_cli application
	SCGCQ00724004 - (Closed) - If we create a VD in Ctrl-m and that Vd was missing in HII
	SCGCQ00733234 - (Closed) - In R5 after fast init VD is go offline and R5 configured drive are failed. (HII/Uefi)
	SCGCQ00686229 - (Closed) - error msg during pd discovery path
	SCGCQ00720428 - (Closed) - 4K SATA Drives support in SWR driver
	SCGCQ00722671 - (Closed) - R10 fast init results in OS driver crash
	SCGCQ00686268 - (Closed) - "Event log wrapped" msg is seen even before the expected interval of 100 events getting printed in MSM.
	SCGCQ00725006 - (Closed) - Rebuild starts on 512 and 4k sector size PD combination
	SCGCQ00735203 - (Closed) - SWR_1.43_PA2: file system getting corrupted on R10 vd for 4k drives across the reboot
 EnhancementRequests (9)
	SCGCQ00669084 - (Implemented) - SCGCQ00664757(PR ID) - Add PnP ID to SWR
	SCGCQ00653725 - (Closed) - Add PnP IDs of Sata and sSata
	SCGCQ00752456 - (Implemented) - SWR crashes when intel_iommu=on set at the Linux boot command line
	SCGCQ00653719 - (Closed) - Add new sSATA DID to MegaSR OProm for Grantley
	SCGCQ00653722 - (Closed) - Add Wellsburg PCH sSATA device ID for OEM
	SCGCQ00763378 - (Opened) -SCGCQ00653671 - (Implemented) - EFI Dual Controller support, changes in common driver code.
 CSETActivities (16)
	SCGCQ00669052 - (Port_Complete) - BIOS Version# in HII does not update after system BIOS update.
	SCGCQ00669143 - (Port_Complete) - hot plug PD was not happening with 4tb drives in HII on Intel grantly
	SCGCQ00734493 - (Port_Complete) - Rebuild once started can't be aborted
	SCGCQ00685496 - (Port_Complete) - 1.42 EFI Dual Controller reconnect issue
	SCGCQ00742038 - (Port_Complete) - StoreLib: SATA READ LOG PAGE Data Corrupted on SWR
	SCGCQ00742042 - (Port_Complete) - StoreLib: TUR Passthru Returns 0x8017 for 0 data length command
	SCGCQ00705046 - (Port_Complete) - Unable to recover the media error on RAID 5
	SCGCQ00705050 - (Port_Complete) - Defining INTEL flag
	SCGCQ00705045 - (Port_Complete) - 4 drives R5 rebuild doesn't work expected for some VD sizes in HII
	SCGCQ00719636 - (Port_Complete) - After Flashing 4TB SATA PD firmware, it doesn't reflecting  instantly in EFI shell.
	SCGCQ00726475 - (Port_Complete) - Windows megasr driver causing system to crash in Jefferson Pass.
	SCGCQ00736118 - (Port_Complete) - System reboots when we select "Apply" while creating VD with 512/512e/4k drives connected.
	SCGCQ00760275 - (Port_Complete) - SMART READ DATA command to be supported in AHCI
	SCGCQ00729387 - (Port_Complete) - Write Performance is not increased by enabling WC on HII/uEF

Version 16.01.2014.0318
1. SWR 1.41 Release Package
2. Package includes WHQL
3. SCGCQ00642532 (DFCT) - unable to stop the rebuild.  Fixed by minor update to code files
4. SCGCQ00645982 (DFCT) - Error when creating a RAID1 with Toshiba drive model.  Fixed by modifying the CDB when doing configuration.

Version 15.04.2013.1016 update
1. Package updated to include WHQL

Version 15.04.2013.1016
1. SWR 1.34 release package.
2. PnP ID's added for several platforms
3. Several minor issues resolved

Version 15.02.2013.0414
1. SWR 1.32 release package.
2. PnP ID's added for several platforms
3. Several minor issues resolved

Version 15.01.2013.0115
1. Several issues resolved, including a Patrol Read issue when global spares were present, some power state functionality (up and down), and issues with some large capacity drives
2. PnP ID's added for several platforms

Version 15.00.1205.2012
1. Several bug fixes, including issues with >2TB drives on both AHCI and SCU controllers
2. PnP ID's added for several platforms
3. Unified code stream to include prior chipset generations
4. WHQL certification across all Windows variants

Version 15.00.0927.2012
1. Issue resolved with PnP ID for S2600CP2 board

Version 15.00.0811.2012
1. Quarterly maintenance release, with several minor issues resolved
2. WHQL completed for all supported Windows releases
3. Support added for new Windows releases (to full package)
4. PnP ID's added for several platforms

Version 15.00.0528.2012
1. Resolved an issue with a large number of events being reported by BMC during rebuild
2. PnP ID's added for several platforms

Version 15.00.0329.2012
1. PnP ID's added for several platforms

Version 15.00.0224.2012
1. Bug fixes - including a hot add situation and several corner case test issues
2. PnP ID's added for several platforms

Version 15.00.0120.2012
1. Bug fixes - primarily for WHQL compliance - first production release for ESRT2 C600 chipset support

Version 15.00.0120.2012
1. baseline for this readme

*Other names and brands may be claimed as the property of others.
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web1, load: 1.51