Dell EMC ME4084 Owner's Manual page 78

Number Severity
163 Warning
166 Warning
167 Warning
170 Info.
171 Info.
172 Warning
78 Events and event messages
Description/Recommended actions
• If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN
information for this controller module on all hosts that access it.
The host WWNs (node and port) previously presented by the partner controller module, which is currently
offline, are unknown.
This event has two possible causes:
• The online controller module reporting the event was replaced or moved while the system was powered
off.
• The online controller module had its flash configuration (where previously used WWNs are stored)
cleared.
The online controller module recovers from this situation by generating a WWN based on its own serial
number for the other controller module.
Recommended actions:
• If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN
information for the other controller module on all hosts that access it.
The RAID metadata level of the two controllers does not match, which indicates that the controllers have
different firmware levels.
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.
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.
The last rescan detected that the indicated enclosure was added to the system.
Recommended actions:
• No action is required.
The last rescan detected that the indicated enclosure was removed from the system.
Recommended actions:
• No action is required.
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.