Number Severity Description/Recommended actions
586 Error Resuming the replication was unsuccessful due to the condition specied within the event. Reasons for
replication failure include but are not limited to shutdown of the secondary system, a loss of communication
across the peer connection (which may be due to CHAP conguration changes), or a pool out-of-space
condition.
Recommended actions:
• Resolve the issue specied by the error message included with this event.
Info. A replication was resumed.
Recommended actions:
• No action is required.
587 Info. A pending replication was removed from the queue.
Recommended actions:
• No action is required.
590 Error A disk group has been quarantined.
This condition resulted from a controller ush/restore failure.
Recommended actions:
• To restore the disk group, use the CLI dequarantine command to dequarantine the disk group. If more
than one disk group is quarantined you must individually dequarantine each disk group, whether it is fault
tolerant or not. When dequarantine is complete, the disk group will return to the state it was in before
being quarantined. For example, if the disk group was reconstructing before being quarantined, the disk
group will resume reconstructing where it stopped
•
For a linear disk group, if you want to nd where parity is incorrect, use the CLI scrub vdisk command
with the fix parameter disabled. This step is optional and not required to x data integrity issues
• For a fault tolerant disk group, run either scrub disk-groups for a virtual disk group or scrub
vdisk
with the fix parameter enabled for a linear disk group. This step will make the parity consistent
with the existing user data, and is required to x data integrity issues.
• For a reconstructing disk group, let reconstruction nish, then run either scrub disk-groups for a
virtual disk group or scrub vdisk with the fix parameter enabled for a linear disk group. This step will
make the parity consistent with the existing user data, and is required to x data integrity issues.
• Restore the data to the disk group from a backup copy.
593 Info. A PCIe bus has transitioned to a dierent speed.
Recommended actions:
• No action is required.
594 Info. The indicated disk in the indicated disk group is missing and the disk group is quarantined. While the disk group
is quarantined, in linear storage any attempt to access its volumes 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 WBI or CLI documentation.
134 Events and event messages
To Next Page
Loading...
