Lenovo ThinkServer RD650 User Manual page 358

12Gb/s MegaRAID SAS Software User Guide
March 2014
Number
0x003f Warning
0x0040 Warning
0x0041 Progress
0x0042 Information
0x0043 Warning
0x0044 Critical
0x0045 Progress
0x0046 Information
0x0047 Information
0x0048 Information
0x0049 Information
0x004a Information
0x004b Fatal
0x004c Fatal
0x004d Progress
0x004e Information
0x004f Fatal
0x0050 Information
0x0051 Information
0x0052 Information
0x0053 Critical
0x0054 Progress
0x0055 Information
0x0056 Information
0x0057 Warning
Severity
Event Text
Level
Consistency Check found
inconsistent parity on %s at strip %lx
Consistency Check inconsistency
logging disabled on %s (too many
inconsistencies)
Consistency Check progress on %s is
%s
Consistency Check started on %s
Initialization aborted on %s
Initialization failed on %s
Initialization progress on %s is %s
Fast initialization started on %s
Full initialization started on %s
Initialization complete on %s
LD Properties updated to %s (from
%s)
Reconstruction complete on %s
Reconstruction of %s stopped due to
unrecoverable errors
Reconstruct detected uncorrectable
double medium errors (%s at %lx on
%s at %lx)
Reconstruction progress on %s is %s Logs reconstruction progress, the progress is logged only if
Reconstruction resumed on %s
Reconstruction resume of %s failed
due to configuration mismatch
Reconstruction started on %s
State change on %s from %s to %s
Drive Clear aborted on %s
Drive Clear failed on %s (Error %02x) Logged when drive clear is failed and the even is logged
Drive Clear progress on %s is %s
Drive Clear started on %s
Drive Clear completed on %s
Error on %s (Error %02x)
Generic Conditions when Each Event Occurs
Logged when consistency check finds inconsistency parity
on a strip.
Logged when consistency check finds too many inconsistent
parity (greater than 10) and the inconsistency parity logging
is disabled.
Logs Consistency Check progress, the progress is logged only
if the progress is greater than 1% at an interval of every
15 seconds.
Logged when consistency check has started
Logged when consistency check is aborted by you or for
some other reason.
Logged when initialization has failed.
Logs initialization progress, the progress is logged only if the
progress is greater than 1% at an interval of every
15 seconds.
Logged when quick initialization has started on a LD. The
parameter to decide Quick init or Full init is passed by you.
Logged when full initialization has started.
Logged when initialization has completed successfully.
Logged when LD properties has been changed.
Logged when reconstruction has completed successfully.
Logged when reconstruction has finished because of failure
(unrecoverable errors).
Logged while reconstructing if an unrecoverable double
medium error is encountered.
the progress is greater than 1% at an interval of every
15 seconds.
Logged when reconstruction resumes after a power cycle.
Logged when reconstruction resume failed due to
configuration mismatch.
Logged on start of reconstruction on a LD.
Logged when there is change in LD state. The event gives the
new and old state. The state could be one of the following,
LDS_OFFLINE, LDS_PARTIALLY_DEGRADED, LDS_DEGRADED,
LDS_OPTIMAL.
Logged when PD clear is aborted.
along with error code.
Logs drive clear progress, the progress is logged only if the
progress is greater than 1% at an interval of every 15 seconds.
Logged when drive clear started on a PD.
Logged when PD clear task is completed successfully on a PD.
Logged if Read returns with Uncorrectable error or same
errors on both the drives or write long returns with an error
(ie. puncture operation could failed).
LSI Corporation
- 358 -
Appendix A: Events and Messages