Number Severity Description/Recommended actions
528 Error Expander Controller firmware detected that the partner Expander Controller (EC) firmware is incompatible
with the enclosure.
As a preventative measure, the Expander Controller (EC) disabled all PHYs and reported the short enclosure
status page in the supported diagnostic list.
Recommended actions:
• Upgrade the partner controller module to the latest supported bundle version.
529 Error The local Expander Controller (EC) is incompatible with the enclosure.
As a preventative measure, the Expander Controller (EC) disabled all PHYs and reported the short enclosure
status page in the supported diagnostic list.
Recommended actions:
• Replace the controller module with one that is compatible with the enclosure.
530 Error The local Expander Controller (EC) firmware detected a level of incompatibility with the partner Expander
Controller (EC). This incompatibility could be due to unsupported hardware or firmware.
As a preventative measure, the local Expander Controller (EC) is holding the partner Expander Controller
(EC) in a reset loop.
Recommended actions:
• Remove the partner controller module from the enclosure. Boot the partner controller module in single-
controller mode in a separate enclosure (without the controller module that reported this event). Load the
latest compatible bundle version. If the version fails to load, replace the partner controller module.
531 Error The indicated controller module was unable to recover from a stall. The system will need to be manually
recovered.
Recommended actions:
• Download the debug logs from your storage system and contact technical support. A service technician
can use the debug logs to determine the problem.
Warning The indicated controller module detected a stall. The system will perform corrective actions.
Recommended actions:
• No action is required.
532 Warning The partner controller module was killed due to encountering a protection information error during a write
operation to disk.
If retries are successful after failover, the controller is deemed at fault. Otherwise, the disk is the likely cause
of failure.
Recommended actions:
• Replace the killed controller if retry is successful after failover. Otherwise (if disk errors are encountered),
replace the disk and bring the controller back into operation.
533 Error This event provides details about the result of the MC test of the indicated component.
If the test succeeded, the message says the component is present and operational. If the test failed, the
message says the component is unavailable.
Recommended actions:
• If the event indicates the test failed, replace the controller module that logged this event.
Info. This event provides details about the result of the MC test of the indicated component.
Recommended actions:
• No action is required.
534 Info. The system determined that the indicated disk is degraded because it experienced a number of disk errors in
excess of a configured threshold.
114 Events and event messages
To Next Page
Loading...
