Novell LINUX ENTERPRISE SERVER 10 SP2 - STORAGE ADMINISTRATION GUIDE 05-15-2009 Administration Manual page 94

The following table identifies RAID events and indicates which events trigger e-mail alerts. All
events cause the program to run. The program is run with two or three arguments: the event name,
the array device (such as
Active, the second device is the relevant component device. For MoveSpare, the second device is
the array that the spare was moved from.
RAID Events in mdadm
Table 6-8
RAID Event
Device Disappeared
Rebuild Started
Rebuild NN
Rebuild Finished
Fail
Fail Spare
Spare Active
New Array
Degraded Array
Move Spare
Spares Missing
Test Message
94 SLES 10 SP2: Storage Administration Guide
), and possibly a second device. For Fail, Fail Spare, and Spare
/dev/md1
Trigger
E-Mail Description
Alert
No An md array that was previously configured appears to no longer be
configured. (syslog priority: Critical)
If mdadm was told to monitor an array which is RAID0 or Linear, then
it reports DeviceDisappeared with the extra information Wrong-Level.
This is because RAID0 and Linear do not support the device-failed,
hot-spare, and resynchronize operations that are monitored.
No An array started reconstruction. (syslog priority: Warning)
md
No Where NN is 20, 40, 60, or 80. This indicates the percent completed
for the rebuild. (syslog priority: Warning)
No An md array that was rebuilding is no longer rebuilding, either
because it finished normally or was aborted. (syslog priority:
Warning)
Yes An active component device of an array has been marked as faulty.
(syslog priority: Critical)
Yes A spare component device that was being rebuilt to replace a faulty
device has failed. (syslog priority: Critical)
No A spare component device that was being rebuilt to replace a faulty
device has been successfully rebuilt and has been made active.
(syslog priority: Info)
No A new md array has been detected in the
(syslog priority: Info)
Yes A newly noticed array appears to be degraded. This message is not
generated when
degradation. It is generated only when
degraded when it first sees the array. (syslog priority: Critical)
No A spare drive has been moved from one array in a spare group to
another to allow a failed drive to be replaced. (syslog priority: Info)
Yes The mdadm.conf
number of spare devices, but
than this number when it first sees the array. (syslog priority:
Warning)
Yes An array was found at startup, and the
(syslog priority: Info)
/proc/mdstat
notices a drive failure that causes
mdadm
mdadm
file indicates that an array should have a certain
mdadm detects that the array has fewer
--test
file.
notices that an array is
flag was given.