Owners Manual

Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
Usually, the controller at the higher firmware level can read metadata written by a controller at a
lower firmware level. The reverse is typically not true. Therefore, if the controller at the higher
firmware level failed, the surviving controller at the lower firmware level cannot read the
metadata in disks that have failed over.
Recommended actions:
● If this occurs after a firmware update, it indicates that the metadata format changed, which
is rare. Update the controller with the lower firmware level to match the firmware level in the
other controller.
167 Warning A diagnostic test at controller bootup detected an abnormal operation, which might require a
power cycle to correct.
Recommended actions:
● Download the debug logs from your storage system and contact technical support. A service
technician can use the debug logs to determine the problem.
170 Info. The last rescan detected that the indicated enclosure was added to the system.
Recommended actions:
● No action is required.
171 Info. The last rescan detected that the indicated enclosure was removed from the system.
Recommended actions:
● No action is required.
172 Error or
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.
90
Events and event messages