Number
Severity
Description/Recommended actions
Recommended actions:
•
No action is required.
172
Warning
The indicated disk group was quarantined for one of the following reasons:
•
Not all of its disks are accessible. While the disk group is quarantined, in linear storage any attempt to
access its volumes in the disk group from a host will fail. In virtual storage, all volumes in the pool will be
forced read-only. If all of the disks become accessible, the disk group will be dequarantined automatically
with a resulting status of FTOL. If not all of the disks become accessible but enough become accessible to
allow reading from and writing to the disk group, it will be dequarantined automatically with a resulting
status of FTDN or CRIT. If a spare disk is available, reconstruction will begin automatically. When the disk
group has been removed from quarantine, event 173 is logged. For a more detailed discussion of
dequarantine, see the SMC or CLI documentation.
CAUTION:
– Avoid using the manual dequarantine operation as a recovery method when event 172 is logged
because this causes data recovery to be more difficult or impossible.
– 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 above 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 the above steps, 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.
96
Events and event messages
Содержание PowerVault ME484
Страница 1: ...Dell EMC ME4 Series Owner s Manual ...
Страница 64: ...3 4 5 64 Module removal and replacement ...