Chapter 9: Troubleshooting
301
Synchronization is
stopped
Synchronization stopped because of user
intervention, schedule or the logical drive was deleted
or went critical or offline.
Synchronization is
aborted due to an internal
error.
System resources are low. Reduce system load or
restart the VessRAID. See page 94 (WebPAM PROe)
or page 207 (CLU).
Synchronization is
queued
Synchronization is already running on another logical
drive in the same array.
Synchronization is
stopped internally
Synchronization stopped because the disk array was
deleted or removed.
System (VessRAID)
The system is started The VessRAID has been started.
The system is stopped The VessRAID was shut down.
Transition
Transition is started Result of settings or user action. Normal.
Transition is completed Normal.
Transition is paused Transition paused because of user intervention,
schedule or a higher priority background activity.
Transition is resumed Transition has resumed again after a pause.
Transition is stopped Transition stopped because of user intervention or
the logical drive was deleted.
Transition was switched
to rebuild
Transition changed to rebuild because the logical
drive went critical.
Watermark
Migration has detected/
cleared stale NV
Watermark
Watermarks are progress markers left as the result of
interrupted RAID migrations. If the watermark was
cleared, migration should finish.
Array was incomplete due
to missing NV Watermark
RAID migration was interrupted by a shutdown.
If array is online, try migration again. See page 122
(WebPAM PROe) or page 165 (CLU).
If array is offline, delete and recreate array. See
page 119 and page 114 (WebPAM PROe) or
page 162 and page 158 (CLU).
Reported Event Corrective Action
To Next Page
Loading...
Need help?
General
