HP StorageWorks 7100 - Virtual Array Appendix page 5

Event Event
Number Name
(dec/hex)
51/0x33 Offline firmware download
with disk size derating
52/0x34 Concurrent downloads
attempted
53/0x35 Feature capability exceeded
54/0x36
Incompatible Image family
55/0x37 Configuration change occurred
during discover subsystem
56/0x38 Download Image Checksum
Failure
57/0x39
Unavailable Data Detected By
RAID1 Read
58/0x3a
Unavailable Data Detected By
RAID1 Write
59/0x3b Disk Interface Error
60/0x3c Unsupported feature
61/0x3d LUN specified exceeds
maximum
62/0x3e
Reassign Failed
63/0x3f Reassign Out Of Resources
64/0x40 Optimal Space Error In RAID
5
65/0x41
Optimal Space Error In RAID
1
66/0x42
No Shutdown Image Posted
67/0x43 Bad Disk Drive State During
Add Physical Drive
68/0x44 Disk Interface Data Underrun
69/0x45 Disk Interface Data Overrun
Predictive Suspected
Maintenance Components
Implication
N Ignore None
Y Ignore - Host None
Problem
N Ignore - Host None
Porblem
N Ignore - Normal None
for some cases of
firmware
N Ignore - should None
be handled by
host
Y Ignore - Likely None
image
distribution
problem
Y Ignore - See None
accompanying
errors
Y Ignore - See None
accompanying
errors
Y N.A. None
N Ignore. Device None
Management
error
N N.A. None
Y Single Disk Drive
Occurrance
Y Single Disk Drive
Occurrance
Y Ingore None
Y Ignore None
N N.A. None
N N.A. None
Y N.A. None
Y N.A. None
Description
N An offline controller firmware download was
attempted while disk size derating was in effect.
Derating of the disks causes the shutdown portion of
the offline download to post the shutdown image at
the wrong location on the disk, and, as a result, the
subsystem boots to a No Maps state after the
download. To prevent this error, remove the disk
derating and try the download again.
Y A host attempted to start a controller firmware
download operation while another was already in
progress.
N A host request was found to require more capability
than current feature licensing has enabled. This may
be a request for an operation that is not enabled in a
currently licensed feature.
N The firmware image that was sent is of a family that
is incompatible with the currently executing
firmware. As a result, the download cannot be
performed online.
Y A configuration change or component hot plug was
detected during the execution of the Discover
Subsystem command. As a result, the response that
was built may not reflect the current configuration.
Y The firmware image that was sent contained defects
such that the checksum verification failed.
N R1 detected that the devices necessary for a read
were not available for access before the access was
attempted. This can apply to an initial attempt to
read or to a retry.
N R1 detected that the devices necessary for a write
were not available for access before the access was
attempted. This can apply to an initial attempt to
write or to a retry.
Y An error occurred on a disk interface command.
Y An attempt was made to install a license for a
feature that this product does not support.
Y An 8-byte hierarchic LUN reference specified a
LUN value that exceeds the maximum specified by
the LUN creation limit mode parameter.
Y The PDD's attempts to reassign a bad block failed
due to device errors.
Y The PDD was unable to complete a Reassign Blocks
command because the sparing buffer is too small.
N R5 detected that space allocated for an "optimal
only" migrating write (i.e. rebuild policy) was no
longer optimal after the write had completed. The
write completed in degraded mode but the client
module requires an optimal completion as indicated
by the optimal only allocation hint.
N R1 detected that space allocated for an "optimal
only" migrating write (i.e. rebuild policy) was no
longer optimal after the write had completed. The
write completed in degraded mode but the client
module requires an optimal completion as indicated
by the optimal only allocation hint.
Y CFM could not shutdown subsystem because no
volume set members was successfully posted with
the NVRAM image.
N A drive was in the initialization failed state after the
spin up attempt during an add physical drive
command. The drive is failing initialization, so
information on the nature of the failure should
appear in the log.
N A backend device sent/received less data than
expected.
N A backend device sent/received more data than
expected.