Table 28. Event descriptions and recommended actions (continued)
Number
Severity
Description/Recommended actions
●
The first time this event is logged with Warning severity, if the indicated disk is not running
the latest firmware, update the disk firmware.
●
If this event is logged with Warning severity for the same disk more than five times in one
week, and the indicated disk is running the latest firmware, replace the disk with one of
the same type (SSD, enterprise SAS, or midline SAS) and the same or greater capacity. For
continued optimum I/O performance, the replacement disk should have performance that is
the same as or better than the one it is replacing.
Info.
A disk drive reported an event.
Recommended actions:
●
No action is required.
59
Warning
The controller detected a parity event while communicating with the indicated SCSI device. The
event was detected by the controller, not the disk.
Recommended actions:
●
If the event indicates that a disk or an expansion module is bad, replace the indicated device.
Info.
The controller detected a non-parity error while communicating with the indicated SCSI device.
The error was detected by the controller, not the disk.
Recommended actions:
●
No action is required.
61
Error
The controller reset a disk channel to recover from a communication error. This event is logged
to identify an error trend over time.
Recommended actions:
●
If the controller recovers, no action is required.
●
View other logged events to determine other action to take.
62
Warning
The indicated dedicated spare disk or global spare disk has failed.
Recommended actions:
●
Replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the
same or greater capacity. For continued optimum I/O performance, the replacement disk
should have performance that is the same as or better than the one it is replacing.
●
If the failed disk was a global spare, configure the new disk as a global spare.
●
If the failed disk was a dedicated spare, configure the new disk as a dedicated spare for the
same disk group.
65
Error
An uncorrectable ECC error occurred in cache memory on startup.
The controller is automatically restarted and its cache data are restored from the partner
controller’s cache.
Recommended actions:
●
Replace the controller module that logged this event.
68
Info.
The controller that logged this event is shut down, or both controllers are shut down.
Recommended actions:
●
No action is required.
71
Info.
The controller has started or completed failing over.
Recommended actions:
●
No action is required.
72
Info.
After failover, recovery has either started or completed.
Recommended actions:
●
No action is required.
80
Events and event messages