[I4]
; 3.2.0.1126 
ms_count=2
ms_1_deviceName="Intel C600 SATA AHCI-RAID RST Enterprise"
ms_1_tag="iaStorA"
ms_1_sysFile="iaStorA.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2826&CC_0104,PCI\VEN_8086&DEV_1D02&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k"
;
ms_2_deviceName="Intel C600 SATA RAID RST Enterprise"
ms_2_tag="iaStorS"
ms_2_sysFile="iaStorS.sys"
ms_2_hwids="PCI\VEN_8086&DEV_1D60,PCI\VEN_8086&DEV_1D61,PCI\VEN_8086&DEV_1D64,PCI\VEN_8086&DEV_1D65,PCI\VEN_8086&DEV_1D68,PCI\VEN_8086&DEV_1D69,PCI\VEN_8086&DEV_1D6A,PCI\VEN_8086&DEV_1D6B"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k"

"==========================
Supported RAID Controllers
==========================
This download provides support for the Intel(R) C600/C222/C224/C226 chipsets on both AHCI Capable SATA Controller and SATA/SAS Capable Controller in Intel(R) Rapid Storage Technology Enterprise (RSTe) mode. 
 
Please verify that this package has been tested with the RAID device you have chosen to use by checking the drivers web page for your controller 
at [url]http://support.intel.com[/url].

===================
Package Information
===================
Package Version = 3.5.1.1009
The iaStorA driver version is 3.5.1.1008
The iaStorS driver version is 3.5.1.1008
The iaStorA Win8/Win2012 driver version is 3.5.1.1008
The iaStorS Win8/Win2012 driver version is 3.5.1.1008
OS supported = Microsoft* Windows 2012 (x64), Windows 8 (x86 & x64), Windows 2008R2 (x64), Windows 7 (x86 & x64), Windows 2008 (x86 & x64),
                          Windows Vista (x86 & x64), Windows 2003 R2SP2 (x86 & x64)

==========
Attention!
==========
This release resolves Standby Immediate issue with SSD's.

==================
Known Restrictions
==================
1. SAS features are enabled on SATA/SAS Capable Controller if appropriate Intel(R) RAID C600 Upgrade Key is present in the system.
2. RAID 5 is no longer supported by SATA/SAS Capable Controller when SAS features are enabled.
3. Boot through expander is not supported in legacy mode at this time.
4. MPIO Load Balancing in RAID Mode is unsupported
5. A SAS Wide port spanning SCU0 and SCU1 is not supported.
6. Plugging both SCU into the same expander is not supported
7. Some WD 6G SAS drives (S25/S35 family) are not supported
8. POST messages are displayed only if more than one drive is attached.
9. Performing a RAID Migration/Rebuild may not result in all of the appropriate LEDs blinking correctly.
10. A manual verify/repair may be required after an unexpected shutdown with running heavy I/O on a RAID volume.
11. RAID volume names should be less than 16 characters."

"==================
Known Restrictions
==================
1. Intel(R) ESRT2 based on Intel(R) C600 chipset does not support UEFI functionality. A UEFI driver is planned/expected to be made available post-launch, but there will be no GUI available in UEFI for configuring arrays.

2. The on-board 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 C600 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 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. 

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."