HP A3550A User Manual - A3661-90001 - Page 295
Troubleshooting, Event code, Event code name, Description
View all HP A3550A manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 295 highlights
Troubleshooting Table 6-10 Error Codes (Continued) Event code Event code name 0x910 Cache Recovery Failed 0x920 0x921 Hard Media Error Host Vault Load Failed 0x922 0x923 Host Vault Load Inconsistent Host Vault Load Failed Bitmap OK 0x924 Host Vault Disks Scrambled 0x925 0x926 Single-board Cache; Need PROM Update RAID-3 Unit Cannot Assign, No Memory 0x928 RAID-3 Initialization Failure, No Memory 0x929 0x937 Front End Fibre Link Down Command Failed Description A nonmirrored cache recovery was attempted but failed to recover information for any cached LUNs. It does not apply to a disk array with two SPs. This disk module has reported a media defect that could not be cleared by the SP. The SP encountered multiple errors while attempting to load the cache image from disk. This message can indicate multiple drive failures. The SP found inconsistencies in the cache image on the disk. This can indicate a failure or abort of the cache dump. The SP successfully read the control portion of the cache image on disk, but found the data portion to be incomplete. This means that a failure or abort occurred during the cache dump. Probably any LUNs with write-cached pages are inaccessible and must be rebound. To identify such a LUN, read message 0x90A in this table. The SP found the vault disks containing the cache image to be in a different order than when the cache image was dumped to disk. This means the disks were swapped at power down. The disk modules must be restored to their original order before the SP can load the cache image. This SP, which is operating in nonmirrored caching mode, has too low a PROM revision level. Write caching cannot be enabled. A RAID-3 LUN cannot be enabled because SP memory allocated for RAID-3 processing is not available. This can happen if the disk array is powered up after SP memory has been removed, or when ownership of the LUN is transferred to a peer SP that does not have enough memory. No RAID-3 LUNs can be enabled because SP memory allocated for RAID-3 processing is not available. This can happen if the disk array is powered up after SP memory has been removed, or when the ownership of the LUN is transferred to a peer SP that does not have enough memory. The front end Fibre Channel interface failed or is inoperable. A command failed for the reason explained in the extended status word. Unsolicited Event Log 6-47