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
○ If you clear unwritten cache data while a disk group is quarantined or offline,
that data will be permanently lost.
● It contains data in a format that is not supported by this system. The controller does not
support linear disk groups.
Recommended actions:
● If the disk group was quarantined because not all of its disks are accessible:
○ If event 173 has subsequently been logged for the indicated disk group, no action is
required. The disk group has already been removed from quarantine.
○ Otherwise, perform the following actions:
■ Check that all enclosures are powered on.
■ Check that all disks and I/O modules in every enclosure are fully seated in their slots
and that their latches are locked.
■ Reseat any disks in the quarantined disk group that are reported as missing or failed
in the user interface. (Do NOT remove and reinsert disks that are not members of the
disk group that is quarantined.)
■ Check that the SAS expansion cables are connected between each enclosure in the
storage system and that they are fully seated. (Do NOT remove and reinsert the
cables because this can cause problems with additional disk groups.)
■ Check that no disks have been removed from the system unintentionally.
■ Check for other events that indicate faults in the system and follow the
recommended actions for those events. But, if the event indicates a failed disk and
the recommended action is to replace the disk, do NOT replace the disk at this time
because it may be needed later for data recovery.
■ If the disk group is still quarantined after performing the steps, shut down both
controllers and then power down the entire storage system. Power it back up,
beginning with any disk enclosures (expansion enclosures), then the controller
enclosure.
■ If the disk group is still quarantined after performing these recommended actions,
contact technical support.
● If the disk group was quarantined because it contains data in a format that is not supported
by this system:
○ Recover full support and manageability of the quarantined disk groups and volumes by
replacing your controllers with controllers that support this type of disk group.
○ If you are sure that the data on this disk group is not needed, simply remove the disk
group, and thus the volumes, using the currently installed controllers.
173
Info. The indicated disk group has been removed from quarantine.
Recommended actions:
● No action is required.
174 Info. Enclosure or disk firmware update has succeeded, been aborted by a user, or failed.
If the firmware update fails, the user will be notified about the problem immediately and should
take care of the problem at that time, so even when there is a failure, this event is logged as
Informational severity.
Recommended actions:
● No action is required.
175 Info. The network-port Ethernet link has changed status (up or down) for the indicated controller.
Recommended actions:
● If this event is logged indicating the network port is up shortly after the Management
Controller (MC) has booted up (event 139), no action is required.
● Otherwise, monitor occurrences of this event for an error trend. If this event occurs more
than 8 times per hour, it should be investigated.
○ This event is probably caused by equipment outside of the storage system, such as faulty
cabling or a faulty Ethernet switch.
Events and event messages 89