HP StorageWorks 9100 Extreme Data Storage System administration guide V1.0.2 (AN540-96018, February 2010)

8. Wait until all sever-segment displays show "on" then power on all server blades.
9. If the HP P700m still cannot access the fabric, replace it on affected server blades and run
exds_stdiagagain.
Management database is inaccessible according to exdsmgr command (or ExDS
monitoring daemons)
If the exdsmgr command (or HP ExDS monitoring daemons) reports that the management database
is inaccessible and this situation persists for several minutes, then the admin service may have been
disabled. Perform the following steps:
1. Verify that the admin filesystem is active and accessible on all servers.
2. Ping theexdsadmin alias as follows: ping -c 3 exdsadmin
3. f you cannot ping the exdsadmin alias, execute the following command:
/opt/hp/mxso/bin/mxso_clear_service
Wait a few seconds, then try again to ping exdsadmin. If exdsadmin is responsive, try to run
the exdsmgr command again.
ExDS9100cc battery fails after replacement
It is possible for a controller cache battery for the ExDS9100cc battery module to exceed its shelf life.
This situation could occur when a battery that has been stored in a minimum charge mode for a period
of time is installed in an active controller. The voltage will remain under a threshold limit and not
properly hold a charge. The battery might at first appear to charge properly but will lose the charge
within several hours. If, when replacing a controller cache battery on the ExDS9100cc battery module,
the battery appears to charge properly, then after several hours the amber LED fault light illuminates,
the battery might not properly be holding a charge due to the issue explained above. Replacing the
battery with a new battery will resolve this issue. Replacement of the controller is not necessary.
LUN status is failed
A LUN status of failed indicates that the logical drive has failed. This is usually the result of failure of
three or more disk drives. This can also happen if you remove the wrong disk drive when replacing
a failed disk drive.
Workaround:
1. Carefully record any recent disk removal or reinsertion actions. Make sure you track the array,
box, and bay numbers and know which disk drive was removed or inserted.
2. Immediately run the exds_escalate command to gather log information that is useful in
diagnosing whether the data can be recovered. Generally, if the failure is due to real disk failures,
the data cannot be recovered. However, if the failure is due to an inadvertent removal of a
working disk drive, it may be possible to restore the LUN to operation.
3. Contact HP Support as soon as possible. The exdsmgr syscheck command tells you which
filesystem is affected by the failed LUN. Look for the "Impacts" message.
9100 Extreme Data Storage System administration guide 141