https://gigatux.com/wiki/index.php?action=history&feed=atom&title=RAID_Fail_Events 2026-11-06T14:17:57Z Revision history for this page on the wiki MediaWiki 1.46.2 https://gigatux.com/wiki/index.php?title=RAID_Fail_Events&diff=4&oldid=prev 2009-04-22T09:34:23Z

<p>Created page with &#039;You get an email like this: This is an automatically generated mail message from mdadm running on node00002.gigatux.com A Fail event had been detected on md device /dev/md3...&#039;</p> <p><b>New page</b></p><div>You get an email like this:<br /> <br /> This is an automatically generated mail message from mdadm<br /> running on node00002.gigatux.com<br /> <br /> A Fail event had been detected on md device /dev/md3.<br /> <br /> It could be related to component device /dev/sda4.<br /> <br /> Faithfully yours, etc.<br /> <br /> P.S. The /proc/mdstat file currently contains the following:<br /> <br /> Personalities : [raid1] <br /> md3 : active raid1 sda4[2](F) sdb4[0]<br /> 970944384 blocks [2/1] [U_]<br /> <br /> md2 : active raid1 sdb3[0] sda3[1]<br /> 979840 blocks [2/2] [UU]<br /> <br /> md1 : active raid1 sdb2[0] sda2[1]<br /> 4586432 blocks [2/2] [UU]<br /> <br /> md0 : active raid1 sdb1[0] sda1[1]<br /> 248896 blocks [2/2] [UU]<br /> <br /> unused devices: &lt;none&gt;<br /> <br /> # Log in as root on the relevant dom0 server<br /> # Type &#039;&#039;mdadm --remove /dev/md3 /dev/sda4&#039;&#039;, replacing md3 and sda4 with the array name and failed device<br /> # Type &#039;&#039;mdadm --add /dev/md3 /dev/sda4&#039;&#039;, replacing md3 and sda4 with the array name and failed device<br /> # Keep an eye on the rebuild status by regularly typing &#039;&#039;cat /proc/mdstat&#039;&#039;</div>

Cocodude