*********************************************
LSI Logic Driver MegaSR Release
*********************************************
Release Date: 08/18/08
===================
Supported Controllers
==================
MegaRAID SAS 8208ELP
MegaRAID SAS 8208XLP
MegaRAID SAS 8204ELP
MegaRAID SAS 8204XLP
Component:
=========
MegaSR Driver Red Hat 4
Release Date: 08/18/2008
Changes / Defects resolved:
LSID100096806 (CO) CR_Ref# LSID100071184: Log event when double medium error is detected.
LSID100098198 (CO) CR_Ref# LSID100096600: SWR new ID support
LSID100097577 (CO) CR_Ref# LSID100097560: Please add following Device IDs to Augusta.
LSID100093834 (CO) CR_Ref# LSID100092706: New SubsystemVendor/Subsystem ID for SWR driver.
LSID100096214 (DFCT) SWR5: Needs modification in dpinst.xml file (Windows driver)
LSID100097455 (DFCT) Error messages
LSID100097881 (DFCT) OS RMU reports specific OEM controller Product Name incorrect
LSID100093892 (DFCT) To supply the MegaSR driver on CD/DVD during installation of SLES10SP1 is impossible
LSID100094710 (DFCT) SWR5: WHQL "Common Scenario Stress with IO" test hangs in BIOS posting with " inconsistent time stamp Message"
LSID100095928 (DFCT) Savannah SWR Windows driver doesn't fail the no-response SAS HDD from OnlineDD in RAID1 by read command.
LSID100096405 (DFCT) SWR5: Drive release notes file needs modification
LSID100077762 (DFCT) SWR: During BGI, it shows the "Cancel Check Conistency" option in MSM
LSID100095067 (DFCT) cannot write on DVD-RAM if LSI SATA RAID is configured
LSID100094499 (DFCT) SWR5 Drivers, I2C LED functions are not working on MPT
LSID100095280 (DFCT) SWR5: Allows to modify/save data on offline VD
Version Numbers:
===============
Includes Current Version:
megasr-11.02.0626.2008-1-rhel40-u5-all.img
megasr-11.02.0626.2008-1-rhel40-u6-all.img
Heading: Known Restrictions
Contents:
• Type "brokenmodules=ahci" line at kernel parameter line during SLES 9 & 10 installations
• RHEL 3.0 64-bit versions are not supported on AMD systems. Only Intel systems are supported.
• RAID 5 is not supported on VMWARE ESX Servers.
• In SWR5 driver, RAID 5 feature is enabled only if iButton is present in the system. BIOS communicates the presence/absence of iButton using configuration data on disk (DDF) and through device registers from BIOS version 06.10111923. So if IButton is present then any driver version later than 10.02.1001.2007 with BIOS version later than 06.10111923 should be able to create a R5 logical drive using an operating system application. The following limitation is applicable for any driver (version less than 10.02.1001.2007) and BIOS (version less than 06.10111923) combination:-
If driver does not read a valid DDF, it will disable R5 creation. 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, user must create initial configuration using BIOS Ctrl+M utility.
• A RAID 5 logical drive withstands single drive failure by reconstructing missing data from the data and parity from 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 inconsistency, drivers starts 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 BIOS utility. Another way is to prevent an unplanned shutdown (e.g. using UPS).
• 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 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.
• RHEL5 installation does not automatically prefer the driver in DUD to native driver. Run replace_ahci script inside the DUD before rebooting during the last stage of installation. Refer to readme.txt under in the DUD for more details
• RAID 5, by its very nature, cannot tolerate double failures. The double failure can be a combination of a single drive failure and either; more drive(s) failure or an unplanned power failure, in the RAID system. Unplanned power failure can be including but 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.
Download Driver Pack
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.