
Event
Number
(dec/hex)
Event
Name
Logged?
Predictive
Maintenance
Implication
Suspected
Components
Mf
g Fail?
Description
51/0x33
Offline firmware download
with disk size derating
N
Ignore
None
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.
52/0x34
Concurrent downloads
attempted
Y
Ignore - Host
Problem
None
Y
A host attempted to start a controller firmware
download operation while another was already in
progress.
53/0x35
Feature capability exceeded
N
Ignore - Host
Porblem
None
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.
54/0x36
Incompatible Image family
N
Ignore - Normal
for some cases of
firmware
None
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.
55/0x37
Configuration change occurred
during discover subsystem
N
Ignore - should
be handled by
host
None
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.
56/0x38
Download Image Checksum
Failure
Y
Ignore - Likely
image
distribution
problem
None
Y
The firmware image that was sent contained defects
such that the checksum verification failed.
57/0x39
Unavailable Data Detected By
RAID1 Read
Y
Ignore - See
accompanying
errors
None
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.
58/0x3a
Unavailable Data Detected By
RAID1 Write
Y
Ignore - See
accompanying
errors
None
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.
59/0x3b
Disk Interface Error
Y
N.A.
None
Y
An error occurred on a disk interface command.
60/0x3c
Unsupported feature
N
Ignore. Device
Management
error
None
Y
An attempt was made to install a license for a
feature that this product does not support.
61/0x3d
LUN specified exceeds
maximum
N
N.A.
None
Y
An 8-byte hierarchic LUN reference specified a
LUN value that exceeds the maximum specified by
the LUN creation limit mode parameter.
62/0x3e
Reassign Failed
Y
Single
Occurrance
Disk Drive
Y
The PDD’s attempts to reassign a bad block failed
due to device errors.
63/0x3f
Reassign Out Of Resources
Y
Single
Occurrance
Disk Drive
Y
The PDD was unable to complete a Reassign Blocks
command because the sparing buffer is too small.
64/0x40
Optimal Space Error In RAID
5
Y
Ingore
None
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.
65/0x41
Optimal Space Error In RAID
1
Y
Ignore
None
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.
66/0x42
No Shutdown Image Posted
N
N.A.
None
Y
CFM could not shutdown subsystem because no
volume set members was successfully posted with
the NVRAM image.
67/0x43
Bad Disk Drive State During
Add Physical Drive
N
N.A.
None
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.
68/0x44
Disk Interface Data Underrun
Y
N.A.
None
N
A backend device sent/received less data than
expected.
69/0x45
Disk Interface Data Overrun
Y
N.A.
None
N
A backend device sent/received more data than
expected.