Filter
Top Products
92 Event code reference
59 Warning or
informational
The controller detected an error while
communicating with the specified SCSI
device. The error was detected by the
controller, not the disk. This event is logged
as a warning for parity errors, and as
informational for other errors.
• For warning events that indicate a disk is
bad, replace that disk.
• For warning events that indicate an
expansion module is bad, replace that
expansion module.
60 Informational A disk channel was reset from another
initiator or target.
61 Critical A serious error, which might indicate
hardware failure, occurred while
communicating on the specified disk
channel. The controller will attempt to
recover.
• If the controller recovers, no action is
required.
• View other logged events to determine
other action to take.
62 Informational A spare disk has failed. Replace the failed disk.
65 Critical An uncorrectable ECC error occurred on the
buffer memory on startup. The controller is
automatically restarted and—if it was
operating in active-active mode (i.e.,
independent cache performance mode was
disabled)—its cache data is restored from the
partner controller’s cache.
67 Informational The controller has identified a new disk or
group of disks that constitute a vdisk and has
taken ownership of the vdisk. This can
happen when disks containing data have
been inserted from another enclosure. This
event only applies to non-Active-Active
controllers.
68 Informational Controller is in a shut-down state.
69 Critical Enclosure reported a general failure. Check the controller module or expansion
module for problems such as not being fully
inserted, and for bad cables.
71 Informational The controller has started or completed
failing over.
72 Informational (Active-active environment)
After failover, recovery has started or has
completed.
73 Informational (Active-active environment)
The two controllers are communicating with
each other and cache redundancy is
enabled.
74 Informational The FC loop ID for the specified vdisk was
changed to be consistent with the IDs of
other vdisks. This can occur when disks
containing a vdisk are inserted from an
enclosure having a different FC loop ID.
This event is also logged by the new owning
controller after vdisk ownership is changed.
Table 14 Event code descriptions and recommended actions (continued)
Event
code
Event type Description Recommended action