Number Severity Description/Recommended actions
543 Critical A data block in a volume was fenced by the controller due to lost data.
This event describes volume information for a fenced data block. It is logged in conjunction with event 542,
which describes disk group and disk information for the data block.
Recommended actions:
• Perform recovery procedures, which may include restoring from backups.
544 Info. A disk group scrub operation exceeded its duration goal by 20%.
The system will attempt to meet the scrub duration goals by adjusting system resources, but factors such as
the amount of data or abnormally high host activity may cause scrub operations to exceed the requested
duration.
Recommended actions:
• If this event occurs repeatedly, the scrub duration goal should be increased to increase the likelihood that
the goal can be met.
545 Warning A controller module is connected to a legacy enclosure midplane, resulting in degraded performance.
Recommended actions:
• To achieve better performance, replace the enclosure’s legacy chassis FRU with the latest version of the
FRU.
546 Error The controller that logged this event killed the partner controller which has an incompatible host port
configuration.
Recommended actions:
• Replace the killed controller module with a controller module that has the same host port configuration as
the surviving controller module.
547 Warning The system determined that the indicated disk is degraded because it experienced a number of disk errors in
excess of a configured threshold. The system has failed the disk, as specified by the configured policy.
Recommended actions:
• Replace the failed disk.
548 Warning Disk group reconstruction failed.
When a disk fails, reconstruction is performed using a spare disk. In this case, the reconstruction operation
failed because unreadable data (uncorrectable media error) exists in at least one other disk in the disk group.
Because of this, a portion of the data cannot be reconstructed.
Recommended actions:
• If you do not have a backup copy of the data in the disk group, make a backup.
• Note the configuration of the disk group, such as its size and host mappings.
• Look for another event logged at approximately the same time that indicates a disk failure, such as event
8, 55, 58, or 412. Follow the recommended actions for that event.
• Remove the disk group.
• Re-add the disk group.
• Restore the data from the backup to a new disk group.
549 Critical The indicated controller module detected that it recovered from an internal processor fault.
Recommended actions:
• Replace the controller module.
116 Events and event messages
To Next Page
Loading...
