Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
Warning An uncorrectable ECC error occurred in Storage Controller CPU memory.
This event is logged with Warning severity to provide information that may be useful to technical
support, but no action is required now. It will be logged with Error severity if it is necessary to
replace the controller module.
Recommended actions:
● No action is required.
400 Info. The indicated log has filled to a level at which it needs to be transferred to a log-collection
system.
Recommended actions:
● No action is required.
401 Warning The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a
log-collection system.
Recommended actions:
● Transfer the log file to the log-collection system.
402 Error The indicated log has wrapped and has started to overwrite its oldest diagnostic data.
Recommended actions:
● Investigate why the log-collection system is not transferring the logs before they are
overwritten. For example, you might have enabled managed logs without configuring a
destination to send logs to.
412 Warning One disk in the indicated RAID-6 disk group failed. The disk group is online but has a status of
FTDN (fault tolerant with a down disk).
If a dedicated spare (linear only) or global spare of the proper type and size is present, that
spare is used to automatically reconstruct the disk group. Events 9 and 37 are logged to indicate
this. If no usable spare disk is present, but an available disk of the proper type and size is present
and the dynamic spares feature is enabled, that disk is used to automatically reconstruct the disk
group and event 37 is logged.
Recommended actions:
RAID-6:
● If event 37 was not logged, a spare of the proper type and size was not available for
reconstruction. Replace the failed disk with one of the same type and the same or greater
capacity and, if necessary, designate it as a spare. Confirm this by checking that events 9
and 37 are logged.
● Otherwise, reconstruction automatically started and event 37 was logged. Replace the failed
disk and configure the replacement as a dedicated spare (linear only) or global spare for
future use.
● For continued optimum I/O performance, the replacement disk should have the same or
better performance.
● Confirm that all failed disks have been replaced and that there are sufficient spare disks
configured for future use.
ADAPT:
● If event 37 was not logged, spare space was not available for reconstruction. Replace the
failed disk with one of the same type and the same or greater capacity. Reconstruction
should start and event 37 should be logged automatically.
● For continued optimum I/O performance, the replacement disk should have the same or
better performance.
● Confirm that all failed disks have been replaced for future fault tolerance.
413
Info. A request to create a replication set completed successfully.
Events and event messages 111