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
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.
Recommended actions:
● No action is required.
414 Error A request to create a replication set failed.
This operation is not permitted if the specified volume is already in a replication set or is not a
master volume.
Recommended actions:
● If the volume is a master volume and is not in a replication set, retry the operation.
415 Info. A request to delete a replication set completed successfully.
Recommended actions:
● No action is required.
416 Error A request to delete a replication set failed.
This can occur if an invalid identifier was specified for the replication set, or if the specified
primary volume is not in the local system.
Recommended actions:
● Repeat the deletion using a valid replication-set identifier, or on the local system for the
primary volume.
417 Info. A snapshot was deleted.
● To make space for a remote snapshot proxy volume.
● To make space for a new snapshot.
● While changing a secondary volume to a primary volume.
● To make space for a new snapshot because the maximum number of snapshots per volume
was reached.
● To make space for a new snapshot because the maximum number of replication snapshots
per system was reached.
● To make space for an unknown reason.
A virtual snapshot was deleted because the user-specified snapshot space limit was exceeded.
Recommended actions:
● No action is required.
418 Warning A remote snapshot operation failed.
● Because the remote pool volume limit was reached.
● Because the remote controller volume limit was reached.
Events and event messages 109