Topic: broken system after power fail

[jameswilson]

i mean i should be able to boot it in a degraded state

[_alex]

You should backup your data now, a degraded raid may not survive a reboot.
Once done, check all your disks condition with smartctl (and maybe badblocks if You want to double check)

You may try to rebuild your failed raid (add the ficked disk), but personnaly, I would rebuild the whole thing.
Ah, and don't forget to setup a daily backup and upsd

[jameswilson]

well i use hdparm to identify the bad sdb. replaced drive and use the recusecd to resync md1. Rebooted, it came up into sme and added the hot spare (sdg) into the array. its now resyncing. I have other issues but in 2000 mins i should have a stable md2

[stephdl]

you should setup a wiki page on your adventure for the next man concerned  with this kind of issues.

[jameswilson]

good shout

Its far from  finished yet, ive never had this happen before, but the arrays are wierd atm

[jameswilson]

[root@sme-big ~]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid1]
md1 : active raid1 sdb[1]
      104320 blocks [7/1] [_U_____]

md127 : active raid1 sda1[0] sdc1[2] sdd1[3] sde1[4] sdf1[5] sdg1[6]
      104320 blocks [7/6] [U_UUUUU]
        resync=DELAYED

md2 : active raid6 sdg2[6] sdf2[5] sde2[4] sdd2[3] sdc2[2] sda2[0]
      7813629952 blocks level 6, 256k chunk, algorithm 2 [6/5] [U_UUUU]
      [================>....]  recovery = 82.3% (1609272576/1953407488) finish=326.8min speed=17546K/sec

unused devices: <none>

Need to sort out the sdb mistake i made