RAID Fail Events

From GigaTux Wiki
Revision as of 09:34, 22 April 2009 by Cocodude (talk | contribs) (Created page with '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...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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.

It could be related to component device /dev/sda4.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] 
md3 : active raid1 sda4[2](F) sdb4[0]
      970944384 blocks [2/1] [U_]
     
md2 : active raid1 sdb3[0] sda3[1]
      979840 blocks [2/2] [UU]
     
md1 : active raid1 sdb2[0] sda2[1]
      4586432 blocks [2/2] [UU]
     
md0 : active raid1 sdb1[0] sda1[1]
      248896 blocks [2/2] [UU]
     
unused devices: <none>
  1. Log in as root on the relevant dom0 server
  2. Type mdadm --remove /dev/md3 /dev/sda4, replacing md3 and sda4 with the array name and failed device
  3. Type mdadm --add /dev/md3 /dev/sda4, replacing md3 and sda4 with the array name and failed device
  4. Keep an eye on the rebuild status by regularly typing cat /proc/mdstat