Novell LINUX ENTERPRISE SERVER 10 - STORAGE ADMINISTRATION GUIDE FOR EVMS Administration Manual page 72

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
1 At a terminal console, log in as the root user.
2 Edit the /etc/mdadm/mdadm.conf file to add your e-mail address for receiving alerts. For
72 SLES 10 Storage Administration Guide for EVMS
RAID Events in mdadm
Trigger
E-Mail
Alert
No
No
No
No
Yes
Yes
No
No
Yes
No
Yes
Yes
example, specify the MAILADDR value (using your own e-mail address, of course):
DEVICE partitions
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=1c661ae4:818165c3:3f7a4661:af475fda
devices=/dev/sdb3,/dev/sdc3
Description
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 will report 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.
An md array started reconstruction. (syslog priority: Warning)
Where NN is 20, 40, 60, or 80. This indicates the percent completed
for the rebuild. (syslog priority: Warning)
An md array that was rebuilding is no longer rebuilding, either
because it finished normally or was aborted. (syslog priority:
Warning)
An active component device of an array has been marked as faulty.
(syslog priority: Critical)
A spare component device that was being rebuilt to replace a faulty
device has failed. (syslog priority: Critical)
A spare component device which was being rebuilt to replace a faulty
device has been successfully rebuilt and has been made active.
(syslog priority: Info)
A new md array has been detected in the /proc/mdstat file.
(syslog priority: Info)
A newly noticed array appears to be degraded. This message is not
generated when mdadm notices a drive failure that causes
degradation. It is generated only when mdadm notices that an array is
degraded when it first sees the array. (syslog priority: Critical)
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)
The mdadm.conf file indicates that an array should have a certain
number of spare devices, but mdadm detects that the array has fewer
than this number when it first sees the array. (syslog priority:
Warning)
An array was found at startup, and the --test flag was given.
(syslog priority: Info)