Dell EMC ME4084 Owner's Manual page 108

Number Severity
486 Warning
487 Info.
488 Info.
489 Info.
490 Info.
491 Info.
492 Info.
493 Info.
108 Events and event messages
Description/Recommended actions
• If events 485 and 486 are both logged at approximately the same time, wait at least 5 minutes for the
automatic recovery process to complete. Then sign in and confirm that both controller modules are
operational. (You can determine if the controllers are operational with the CLI show controllers
command or with the SMC.) In most cases, the system will come back up and no further action is
required. If both controller modules do not become operational in 5 minutes, data may have been lost.
If both controllers are not operational, follow this recovery process:
• Remove the controller module that first logged event 486.
• Turn off the power for the controller enclosure, wait a few seconds, then turn it back on.
• Wait for the controller module to restart, then sign in again.
• Check the status of the disk groups. If any of the disk groups have a status of quarantined offline
(QTOF), dequarantine those disk groups.
• Reinsert the previously removed controller module. It should now restart successfully
A recovery process was initiated to prevent writing invalid data that may exist in the controller that logged
this event.
The controller that logged this event has detected (using information saved in the disk group metadata) that
it may contain outdated data that should not be written to the disk groups. The controller will log this event,
restart the partner controller, wait 10 seconds, then kill itself. The partner controller will then unkill this
controller and mirror the correct cache data to it. This procedure will, in most cases, allow all data to be
correctly written without any loss of data and without writing any outdated data.
Recommended actions:
• Wait at least 5 minutes for the automatic recovery process to complete. Then sign in and confirm that
both controller modules are operational. (You can determine if the controllers are operational with the CLI
show redundancy-mode command.) In most cases, the system will come back up and no action is
required.
• If both controller modules do not become operational in 5 minutes, see the recommended actions for
event 485, which will be logged at approximately the same time.
Historical performance statistics were reset.
Recommended actions:
• No action is required.
Creation of a volume group started.
Recommended actions:
• No action is required.
Creation of a volume group completed.
Recommended actions:
• No action is required.
Creation of a volume group failed.
Recommended actions:
• No action is required.
Creation of a volume group started.
Recommended actions:
• No action is required.
The volumes in a volume group were ungrouped.
Recommended actions:
• No action is required.
A volume group was modified.
Recommended actions: