I had to smother a server a couple days ago and it caused my RAID 1 to mark a drive as dirty and it was taking FOREVER so i used
mdadm to mark the dirty drive as faulty. I did this because i had to move and copy a lot (over a TB) of data to the raid and it was taking way to long.
My thoughts were to stop the RAID from rebuilding by marking it faulty. Then when i am done with all of this tell it the drives OK and let the rebuild do its thing over the weekend when performance wouldn't be an issue.
I copied my data, rebooted the server (for other reasons I also did some apt updates) and when it came back up it looked like my simulated failure was rest and that the raid array was not only back but functioning completely normal and in sync. Then I got the "SparesMissing event on /dev/md0" email. Looking at
mdadm -D and
/proc/mdstat everything looks ok. Why am i getting the email and what am i not seeing in the config?
cat /proc/mdstat && mdadm -D /dev/md0 Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sdb1 sdd1(S) sde1 976630336 blocks super 1.2 [2/2] [UU] unused devices: <none> /dev/md0: Version : 1.2 Creation Time : Thu Sep 6 08:45:09 2012 Raid Level : raid1 Array Size : 976630336 (931.39 GiB 1000.07 GB) Used Dev Size : 976630336 (931.39 GiB 1000.07 GB) Raid Devices : 2 Total Devices: 3 Persistence : Superblock is persistent Update Time : Sun Aug 4 04:04:42 2013 State : clean Active Devices : 2 Working Devices : 3 Failed Devices : 0 Spare Devices : 1 Name : data:0 (local to host data) UUID : f53d13a8:c54ba617:1d729713:a087f0dd Events : 3068 Number Major Minor RaidDevice State 0 8 17 0 active sync /dev/sdb1 4 8 65 1 active sync /dev/sde1 3 8 49 - spare /dev/sdd1