Historical Performance Statistics Were Reset - HP P2000 G3 MSA Reference Manual

485
Warning The indicated vdisk was quarantined to prevent writing invalid data that may exist on the controller that
logged this event.
This event is logged to report that the indicated vdisk has been put in the quarantined offline state (status of
QTOF) to prevent loss of data. The controller that logged this event has detected (via information saved in
the vdisk metadata) that it may contain outdated data that should not be written to the vdisk. Data may be
lost if you do not follow the recommended actions carefully. This situation is typically caused by removal of
a controller module without shutting it down first, then inserting a different controller module in its place. To
avoid having this problem occur in the future, always shut down the Storage Controller in a controller
module before removing it.
Recommended actions
• If event 486 is not logged at approximately the same time, reinsert the removed controller module, shut
it down, then remove it again.
• 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 show redundancy-mode
CLI command or the System Redundancy table in the System Overview panel of the SMU.) 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 vdisks. If any of the vdisks have a status of quarantined offline (QTOF),
dequarantine those vdisks.
• Reinsert the previously removed controller module. It should now restart successfully.
486
Info. A recovery process was initiated to prevent writing invalid data that may exist on the controller that logged
this event.
The controller that logged this event has detected (via information saved in the vdisk metadata) that it may
contain outdated data that should not be written to the vdisks. 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
show redundancy-mode CLI command or the System Redundancy table in the System Overview
panel of the SMU.) 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.
487
Info.

Historical performance statistics were reset.

Recommended actions
• No action is required.
HP P2000 G3 MSA System Event Descriptions Reference Guide 59