Number Severity Description/Recommended actions
• The communication link is busy or experienced an error.
• The snapshot being used for the replication is invalid.
• There was a problem establishing proxy communication.
• The replication is being automatically retried according to policies in place. If the issue is resolved before
retries are exhausted, the replication will continue on its own. Otherwise, it will go into a suspended state
unless the policy is set up to retry forever.
Recommended actions:
• If any of the above problems exist, resolve them.
441 Error A request to add a secondary volume failed. User intervention is needed to remove the volume from the set.
Recommended actions:
• Remove the indicated secondary volume from the replication set.
442 Warning Power-On Self Test (POST) diagnostics detected a hardware error in a UART chip.
Recommended actions:
• Replace the controller module that logged this event.
443 Error The firmware for the indicated enclosure is not supported in this configuration.
The firmware for the indicated enclosure does not support this enclosure for use as an expansion chassis. Its
firmware supports this enclosure only as a direct attached JBOD.
Recommended actions:
• Replace the indicated enclosure. It is not supported.
444 Info. A snap pool is running out of space.
A snap pool reached a capacity threshold and the associated policy completed successfully:
• Delete snapshots
• Halt writes
• Delete oldest snapshot
• Notify only
• Invalidate snapshots
• Auto expand
• Unknown policy
For example, the snap pool was expanded successfully, or the oldest snapshot was deleted, or all snapshots
were deleted. If the policy is Delete Oldest Snapshot, the serial number of the deleted snapshot is reported.
Recommended actions:
• No action is required.
Warning A snap pool is running out of space.
A snap pool reached a capacity threshold and the associated Auto Expand policy failed because there is not
enough available space in the disk group.
Recommended actions:
• Increase the available space in the disk group either by expanding the disk group or by removing any
unneeded volumes.
449 Info. A roll back was aborted because of an error or other internally detected condition.
This can occur if a roll back is in progress and a user selects to roll back a different volume, which will abort
the first roll back and start a new roll back. A user can't explicitly abort a roll back because that would corrupt
the parent volume.
Recommended actions:
• No action is required.
450 Warning The status of a remote volume changed from online to offline.
102 Events and event messages
To Next Page
Loading...
