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
208 Info. A scrub-disk job has started for the indicated disk. The result will be logged with event 209.
Recommended actions:
● No action is required.
209 Error A scrub-disk job logged with event 208 has completed and found one or more media errors,
SMART events, or hard (non-media) errors. If this disk is used in a non-fault-tolerant disk group,
data may have been lost.
Recommended actions:
● Replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the
same or greater capacity. For continued optimum I/O performance, the replacement disk
should have performance that is the same as or better than the one it is replacing.
Warning A scrub-disk job logged with event 208 has been aborted by a user, or has reassigned a disk
block. These bad-block replacements are reported as "other errors". If this disk is used in a
non-fault-tolerant disk group, data may have been lost.
Recommended actions:
● Monitor the error trend and whether the number of errors approaches the total number of
bad-block replacements available.
Info. A scrub-disk job logged with event 208 has completed and found no errors, or a disk being
scrubbed (with no errors found) has been added to a disk group, or a user has aborted the job.
Recommended actions:
● No action is required.
210 Info. All snapshots have been deleted for the indicated parent volume when using virtual storage.
Recommended actions:
● No action is required.
211 Warning SAS topology has changed. No elements are detected in the SAS map. The message specifies
the number of elements in the SAS map, the number of expanders detected, the number of
expansion levels on the native (local controller) side and on the partner (partner controller) side,
and the number of device PHYs.
Recommended actions:
● Perform a rescan to repopulate the SAS map.
● If a rescan does not resolve the problem, then shut down and restart both Storage
Controllers.
● If the problem persists, see Troubleshooting and problem solving on page 30.
Info. SAS topology has changed. The number of SAS expanders has increased or decreased. The
message specifies the number of elements in the SAS map, the number of expanders detected,
the number of expansion levels on the native (local controller) side and on the partner (partner
controller) side, and the number of device PHYs.
Recommended actions:
● No action is required.
212 Info. All master volumes associated with a snap pool were deleted.
Recommended actions:
● No action is required.
213 Info. A master volume was converted to a standard volume or a standard volume was converted to a
master volume
Recommended actions:
● No action is required.
214 Info. The creation of snapshots is complete. The number of snapshots is indicated.
94 Events and event messages