VessRAID Setup - Promise Technology, Inc.

Reported Event Corrective Action
299
Chapter 9: Troubleshooting
Rebuild is resumed Rebuild has resumed again after a pause.
Rebuild is stopped Rebuild stopped because of user intervention,
schedule or the logical drive was deleted or the target
disk drive encountered an error.
If rebuild stopped by the user, restart the rebuild. See
page 123 (WebPAM PROe) or page 164 (CLU).
Rebuild stopped internally The logical drive is offline. See page 302.
Rebuild is aborted due to System resources are low. Reduce system load or
an internal error. restart the VessRAID. See page 94 (WebPAM PROe)
or page 207 (CLU).
Rebuild is queued Rebuild has been set manually or by schedule.
Rebuild marks logical Result of successful rebuild. Normal.
drive synchronized upon
rebuild completion
Redundancy Check
Redundancy Check is
started
Redundancy Check is
completed
Redundancy Check is
paused
Redundancy Check is
resumed
Redundancy Check is
stopped
Redundancy Check is
aborted due to internal
error
Redundancy Check
encountered inconsistent
block(s)
Redundancy Check task
is queued
Redundancy Check task
is stopped internally
Redundancy Check has started manually or by
schedule.
Redundancy Check has finished.
Redundancy Check paused because of user
intervention, schedule or a higher priority background
activity.
Redundancy Check has resumed again after a
pause.
Redundancy Check stopped because of user
intervention, schedule or the logical drive was deleted
or went critical or offline. See page 302.
System resources are low. Reduce system load or
restart the VessRAID. See page 94 (WebPAM PROe)
or page 207 (CLU).
Check the logical drive’s inconsistent block table. See
page 131. Rebuild the disk array if necessary. See
page 114 (WebPAM PROe) or page 158 (CLU).
Redundancy Check has been set manually or by
schedule.
The logical drive is offline. See page 302.