Battery:

         A failed battery could ONLY cause this if a system has a power loss/hard shut down
situation and the system will give other errors if the raid battery is having problems.  A PERC
controller would operate normally with a failed battery (in Write-Through mode), the battery is
just there to keep the DIMM (Cache) energized if the system suddenly looses power.
         The battery only keeps a charge for up to 24 hours.  If a site loses power for more than 24
hours or the system has been sitting unplugged, this message would only indicate that the cache
data was lost and there are no hardware issues.

Memory:

         A failed raid DIMM will cause this error.  It will normally be accompanied by the system blue
screening and/or rebooting during the boot process to the OS.  With Linux it could be a kernel
panic.  This does not mean the raid DIMM is failed, but it a possibility, you must then move on to
testing the raid DIMM.

Software:

         Sometimes a damaged OS crashing with good hardware will cause this error.  This is the
hardest issue to identify.  Test hardware first.

Troubleshooting:

         When did this error start?  Was it after a power outage or a server that had been unplugged a
long time? Drives migrated from another machine?  RAID battery unplugged or DIMM removed?
Controller replaced?  This is all NORMAL. 
         If it is the first time, see if the system will boot to OS.  If it does boot to OS, more information
about the frequency and situation of failures will need to be gathered.  If it boots there may be
nothing wrong with the hardware.
         If the OS fails to boot, software is not ruled out, but hardware is a possibility.
         If it is an 8th gen server,  test the raid DIMM in the system memory slot.  Remove the RAID
battery first before ever removing a RAID DIMM.  Remove RAID DIMM and system memory. 
Install raid DIMM in slot one of the system board and post the system.  If the system comes up
with an errors on POST memory test giving read/write errors,  replace RAID DIMM, make sure
you use the right part number.   If no errors come up on post memory test, you will see an error
message about missing raid components on ROMB systems.  Remove all HDDs before
proceeding to change to SCSI mode.  Make sure system is back in RAID mode before HDDs are
reinstalled.  Run MpMemory test on the DIMM.  If it fails, replace it.  If it passes, chances are the
RAID DIMM is good.
         You can’t test the RAID DIMM in 9th gen or newer servers, or PERC 5 and newer controllers.
         If the DIMM passes tests, try reinstalling it, a reseat my fix it.
         A bad slot on the controller/riser could then be a possibility, but this is less common.
         Software can be isolated by using other drives, reinstall, booting to OMSA LIVE, etc.
         If you are unable to isolate, make sure you understand that raid DIMMs fail more often
than controllers/riser.  Raid batteries do NOT cause a no boot situation.
         Also, keep in mind the controller uses the RAID DIMM for it’s own BIOS and functionality. 
Turning the cache policies off may allow the system to boot to the OS, but it could crash later
on.  The load on the DIMM normally directly effects how long it can operate before the
controller “crashes.” 
         For PERC 4s with 256meg DIMM, make sure you send part number 4D554 if dispatching a
DIMM.
2.0 Installation and setup instructions
________________________________________

This package can be used with several of IBM's update management tools,
including IBM UpdateXpress Manager, IBM UpdateXpress System Packs, and
IBM Director.

It can also be used as a standalone package.

To use the package with one of IBM's update management tools, follow the
instructions that came with your specific management tool.

2.1 Standalone usage instructions

---------------------------------

As a standalone package, this executable can be used in the following ways:

- to update the SAS controller BIOS and FW on the local system
- to create a DOS based bootable diskette that can be used to update the
firmware in an offline fashion

Updating the local system:

1) Run the executable by double clicking on the file icon, or by typing
'ibm_fw_sraidmr_10i-10is-11.0.1-0033_windows_32-64.exe' at a command
prompt.
2) Select "Perform Update" and then click "Next".
3) Click "Update".
4) To perform another function, click "Back", otherwise click "Exit" to
exit the utility.

Creating a diskette
1) Run the executable by double clicking on the file icon, or by typing
'ibm_fw_sraidmr_10i-10is-11.0.1-0033_windows_32-64.exe' at a command
prompt.
2) Select "Extract to Floppy" and then click "Next".
3) Insert a blank diskette into the diskette drive.
4) To perform another function, click "Back", otherwise click "Exit" to
exit the utility.

NOTE: If you are running the update on a system where the diskette drive
is not mapped to A:, you will need to type, at a command prompt:
'ibm_fw_sraidmr_10i-10is-11.0.1-0033_windows_32-64.exe -xd <diskette
drive>'
where, <diskette drive> is something like 'b:'.

2.2 Troubleshooting tips

------------------------
None

3.0 Configuration information

______________________________

For detailed setup instructions for your controller, refer to the

documentation on the "IBM ServeRAID MR Support" CD.

4.0 Unattended Mode

____________________

To run this package in unattended mode, use the following command:

ibm_fw_sraidmr_10i-10is-11.0.1-0033_windows_32-64.exe -s