Owners Manual
Table Of Contents
- Dell EMC PowerVault ME4 Series Storage System Owner’s Manual
- Contents
- Storage system hardware
- Troubleshooting and problem solving
- Module removal and replacement
- ESD precautions
- Dealing with hardware faults
- Firmware updates
- Continuous operation during replacement
- Shutting down attached hosts
- Shutting down a controller module
- Verifying component failure
- Customer-replaceable units (CRUs)
- Attach or remove the front bezel of a 2U enclosure
- Replacing a drive carrier module in a 2U enclosure
- Replacing a DDIC in a 5U enclosure
- Replacing a controller module or IOM in a 2U or 5U enclosure
- Replacing a power supply unit (PSU) in a 5U enclosure
- Replacing a fan cooling module (FCM) in a 5U enclosure
- Replacing a power cooling module (PCM) in a 2U enclosure
- Completing the component installation process
- Verifying component operation
- Performing updates in PowerVault Manager after replacing an FC or SAS HBA
- Events and event messages
- Connecting to the CLI port using a serial cable
- Technical specifications
- Standards and regulations
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
539 Info. For the indicated disk group, which was corrupted, the 'recreate' step of the group recovery
was not successful or the 'recreate' step of the disk group recovery succeeded.
Recommended actions:
● Verify that expected volumes have been recovered.
● If the expected volumes were not recovered, the "recover volume" command may be used.
● After verifying volume recovery, complete disk group recovery by running the 'recover disk-
group complete' command.
540 Info. The indicated volume, which was corrupted, has been recovered.
Recommended actions:
● After verifying volume recovery, complete disk group recovery by running the 'recover disk-
group complete' command.
541 Info. For the indicated disk group, which was corrupted, the 'complete' step of the disk group
recovery succeeded.
Recommended actions:
● No action is required.
542 Critical A data block was fenced by the controller due to lost data.
Event 543 will also be logged to describe volume information for the fenced data block.
Recommended actions:
● Perform recovery procedures, which may include restoring from backups.
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:
Events and event messages 127