HP StorageWorks 7100 - Virtual Array Appendix page 7

Event Event
Number Name
(dec/hex)
for LUN operation.
89/0x59 Undefined
90/0x5a Host Read Collision With
Failed Cache Post
91/0x5b Ambiguous Volume Set
Reference
92/0x5c
Recovery From RAM Loss
Failed
93/0x5d
Multiple Failures Suspected
During Recovery
94/0x5e Volume Set Missing During
Recovery
95/0x5f RAM Configuration Mismatch
During Recovery
96/0x60
Read Recovered With RAID 5
Retries
97/0x61 Write Recovered With RAID 5
Retries
98/0x62 Read Recovered With RAID 5
Redundancy
99/0x63 Write Recovered With RAID 5
Redundancy
100/0x64 Read Recovered With RAID 1
Redundancy
101/0x65
Write Recovered With RAID 1
Redundancy
102/0x66 Disk drive reported a SMART
event
Predictive Suspected
Maintenance Components
Implication
N N.A. None
Y ignore - see None
accompanying
errors
Y ignore - operator None
error
Y Single Disk Drive,
Occurrance Disk Interface,
Controller,
Operator
Y ignore - see None
accompanying
errors
Y ignore - operator None
error
Y Single Controller
Occurrance SIMM, operator
error
Y Ignore - See None
accompanying
errors
Y Ignore - See None
accompanying
errors
Y Ignore - See None
accompanying
errors
Y Ignore - See None
accompanying
errors
Y Ignore - See None
Accompanying
Errors
Y Ignore - See None
Accompanying
Errors
Y Signals internal Disk Drive
drive errors
threshold
exceeded,
Description
controllers to complete the requested LUN
operation. More memory must be installed before
the requested operation can be completed
successfully.
N Undefined event code.
N A host write was flushed from cache but ended with
a non-SUCCESS status; this caused cache to mark
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.
Y A volume set ID referenced in a recover command
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.
Y This error indicates that the controller was unable to
recover an NVRAM image from any disk in the
volume set. This could be because none of the disks
present have images, or the disks that did have
images were removed, or failed before the images
could be fully uploaded into the controller.
Y Conditions detected during recovery indicate that at
least one failure or hot plug event occurred in
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.
Y The volume set referenced in a recover command is
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
Y An attempt was made to recover an image after
RAM loss but the image would not fit in the non-
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.
N Retries were used by the R5 module in the
successful completion of a read.
N Retries were used by the R5 module in the
successful completion of a write.
N Redundancy was used by the R5 module in the
successful completion of a read.
N Redundancy was used by the R5 module in the
successful completion of a write.
N Redundancy was used by the R1 module in the
successful completion of a read.
N Redundancy was used by the R1 module in the
successful completion of a write.
Y The disk drive reported a SMART event. The event
is logged and the common sense data is updated for
all regular read/write and passthru commands. The
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