Number Severity Description/Recommended actions
• No action is required.
401 Warning The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a log-collection
system.
Recommended actions:
• Transfer the log file to the log-collection system.
402 Error The indicated log has wrapped and has started to overwrite its oldest diagnostic data.
Recommended actions:
• Investigate why the log-collection system is not transferring the logs before they are overwritten. For
example, you might have enabled managed logs without configuring a destination to send logs to.
412 Warning One disk in the indicated RAID-6 disk group failed. The disk group is online but has a status of FTDN (fault
tolerant with a down disk).
If a dedicated spare (linear only) or global spare of the proper type and size is present, that spare is used to
automatically reconstruct the disk group. Events 9 and 37 are logged to indicate this. If no usable spare disk is
present, but an available disk of the proper type and size is present and the dynamic spares feature is
enabled, that disk is used to automatically reconstruct the disk group and event 37 is logged.
Recommended actions:
• If event 37 was not logged, a spare of the proper type and size was not available for reconstruction.
Replace the failed disk with one of the same type and the same or greater capacity and, if necessary,
designate it as a spare. Confirm this by checking that events 9 and 37 are logged.
• Otherwise, reconstruction automatically started and event 37 was logged. Replace the failed disk and
configure the replacement as a dedicated spare (linear only) or global spare for future use.
• For continued optimum I/O performance, the replacement disk should have the same or better
performance.
• Confirm that all failed disks have been replaced and that there are sufficient spare disks configured for
future use.
413 Info. A request to create a replication set completed successfully.
Recommended actions:
• No action is required.
414 Error A request to create a replication set failed.
This operation is not permitted if the specified volume is already in a replication set or is not a master volume.
Recommended actions:
• If the volume is a master volume and is not in a replication set, retry the operation.
415 Info. A request to delete a replication set completed successfully.
Recommended actions:
• No action is required.
416 Error A request to delete a replication set failed.
This can occur if an invalid identifier was specified for the replication set, or if the specified primary volume is
not in the local system.
Recommended actions:
• Repeat the deletion using a valid replication-set identifier, or on the local system for the primary volume.
417 Info. A snapshot was deleted.
• To make space for a remote snapshot proxy volume.
• To make space for a new snapshot.
• While changing a secondary volume to a primary volume.
• To make space for a new snapshot because the maximum number of snapshots per volume was reached.
98 Events and event messages
To Next Page
Loading...
