HP StorageWorks Virtual Array 7100 Appendix A. Disk Array Controller Log - Page 7

Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description Logged? Mfg Fail? 89/0x59 90/0x5a 91/0x5b 92/0x5c 93/0x5d 94/0x5e 95/0x5f 96/0x60 97/0x61 98/0x62 99/0x63 100/0x64 101/0x65 102/0x66 for LUN operation. controllers to complete the requested LUN operation. More memory must be installed before the requested operation can be completed successfully. Undefined N N.A. None N Undefined event code. Host Read Collision With Y ignore - see None N A host write was flushed from cache but ended with Failed Cache Post accompanying a non-SUCCESS status; this caused cache to mark errors the write cache entry as RETRY which means it is stuck in cache. A new host read partially hits the same address which normally causes the write to flush but the write is stuck in cache. The response is to fail the read. Ambiguous Volume Set Y ignore - operator None Y A volume set ID referenced in a recover command Reference error was ambiguous. If a null (wild card) volume set was used in a recover command then this error means that the controller found drives from multiple volume sets present. If a non-null volume set uas used then this error means that the contoller is already attached to a volume set other than the one referenced in the recover command. Recovery From RAM Loss Y Single Disk Drive, Y This error indicates that the controller was unable to Failed Occurrance Disk Interface, recover an NVRAM image from any disk in the Controller, volume set. This could be because none of the disks Operator present have images, or the disks that did have images were removed, or failed before the images could be fully uploaded into the controller. Multiple Failures Suspected Y ignore - see None Y Conditions detected during recovery indicate that at During Recovery accompanying least one failure or hot plug event occurred in errors addition to the loss of NVRAM that prompted the recovery. This implies that data integrity is likely to have been compromised in ways that are not detectable outside of the occurrance of this log entry or sense data report. It is likely that the controller does not have sufficient information to determine the extent of the damage. Volume Set Missing During Y ignore - operator None Y The volume set referenced in a recover command is Recovery error not present in the subsystem. If a NULL volume set was referenced then this error indicates that no members of any volume set were present. This error can also result from imcompatible stamp versions RAM Configuration Mismatch Y Single Controller Y An attempt was made to recover an image after During Recovery Occurrance SIMM, operator RAM loss but the image would not fit in the non- error failing memory available on the controller. Either the SIMM configuration has been modified, or one or more SIMMs have failed. Recovery may be possible using the another controller as the primary. Read Recovered With RAID 5 Y Ignore - See None N Retries were used by the R5 module in the Retries accompanying successful completion of a read. errors Write Recovered With RAID 5 Y Ignore - See None N Retries were used by the R5 module in the Retries accompanying successful completion of a write. errors Read Recovered With RAID 5 Y Ignore - See None N Redundancy was used by the R5 module in the Redundancy accompanying successful completion of a read. errors Write Recovered With RAID 5 Y Ignore - See None N Redundancy was used by the R5 module in the Redundancy accompanying successful completion of a write. errors Read Recovered With RAID 1 Y Ignore - See None N Redundancy was used by the R1 module in the Redundancy Accompanying successful completion of a read. Errors Write Recovered With RAID 1 Y Ignore - See None N Redundancy was used by the R1 module in the Redundancy Accompanying successful completion of a write. Errors Disk drive reported a SMART Y Signals internal Disk Drive Y The disk drive reported a SMART event. The event event drive errors is logged and the common sense data is updated for threshold all regular read/write and passthru commands. The exceeded, precedence for SMART event data in the common area is low, so that other errors that occur during the same I/O are reported back to the host. A SMART event does not affect the I/O except that it does