LSI_logo Engineering Release Notice
Release Date: 12-18-2009
OEM: ALL_OEM
SWR_Driver_R5_Univ 13.15.1218.2009


SWR_Driver_R5_Univ
Component: SWR_Driver_R5_Univ
Stream: SWR_DRIVER_R5_UNIV_ATHENS_Integration
Version: 13.15.1218.2009
Baseline From: SWR_DRIVER_R5_UNIV_ATHENS_12_9_2009_WINDOWS_RELEASE.1010
Baseline To: SWR_DRIVER_R5_UNIV_ATHENS_12_18_2009_WINDOWS_RELEASE.9956
CHANGE SUMMARY:
LSID100102202 (TASK) Task to make Linux release
LSID100152846 (TASK) LSID100152527 : dvd "deleting media" doesn't work
LSID100152527 (DFCT) "Deleting media" could not complete with error on DVD-RAM drive in Athens environment.
DEFECT RECORDS (Total Defects=1, Number Duplicate=0):
SWR_Driver_R5_Univ DEFECTS
DFCT ID: LSID100152527
Customer DFCT No: SWRAID_PR4078
Headline: "Deleting media" could not complete with error on DVD-RAM drive in Athens environment.
Description: This issue only occurred on Athens.
This issue not occurred on Alpharetta or Augusta.
Version of Bug Reported: 13.11.922.2009(Athens)
Version of Bug Fixed: 13.15.1218.2009
Steps to Reproduce: [Environment]
Server:IPx                    
CPU :Genuine Intel® CPU 000 @ 3.07GHz                     
mem :2GB                    
BIOS :1.0.0010                    
OS : Windows Vista x86 SP2
RAID : SATA SWRAID(IbexPeak)
Driver : MegaSR1.sys(13.11.922.2009(Athens))
HDD : Not depend on HDD.
ODD : MATSHITADVD-RAM UJ870BJ /FW:1.50

[Procedure]
1. Insert rewriteable media to DVD-RAM drive on SWRAID.
2. Execute “Delete disk” by explorer.
Resolution: Fixed
Resolution Description: LSID100152527 : dvd "deleting media" doesn't work
Root Cause: Not setting the correct device type in the inquiry and issuing the ATA_PASSTHRU commands as non-ATAPI commands for ATAPI devices
Fix: Setting the correct device type and issuing as ATAPI command.
Customer Defect Track No: SWRAID_PR4078
Customer List: OEM -- OEM
Fix Impact: Medium
Suggested Testing: Test: Use the correct media for the drives/recorders used and verify that "erase" opeartion completes without any issue.
Also make sure tape device works at intended.
Child Tasks: LSID100152846
UCM ACTIVITY / TASK RECORDS (2):
SWR_Driver_R5_Univ UCM TASKS
Task ID: LSID100102202
Headline: Task to make Linux release
Description: Task to make Linux release
State: Open
Change Set Files: 0
References:  
SWR_Driver_R5_Univ UCM TASKS
Task ID: LSID100152846
Headline: LSID100152527 : dvd "deleting media" doesn't work
Description: LSID100152527 : dvd "deleting media" doesn't work
State: Completed
Change Set Files: 0
References:   LSID100152527(DFCT)    
DEVELOPER NOTES:
SWR_Driver_R5_Univ DEVELOPER NOTES
Heading: Known Restrictions
Contents:                     
• 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.

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

Multiple drive failure 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.