On Monday December 18, lists@xxxxxxxxxxxxxx wrote: > Hello, > > tonight the unthinkable happend and two drives in a four drive raid 5 > went offline within one hour. > I deactivated the raid, turned the computer off and rebooted. I checked > both drives and they are fine. > > The raid consists of sdb1, sdc1, sdd1 and sde1. > sdd1 failed first, then sde1. > I use kernel 2.6.18.2 with raidtools 1.00.3-r6. > > After reading through the howtos and archives the following should be > the proper way to rescue the raid 5: > > mark first failed drive as failed-disk, so my new raidtab entry should > look like this: > ==== > raiddev /dev/md10 > raid-level 5 > nr-raid-disks 4 > nr-spare-disks 0 > persistent-superblock 1 > chunk-size 64k > parity-algorithm left-symmetric > > device /dev/sdb1 > raid-disk 0 > device /dev/sdc1 > raid-disk 1 > device /dev/sdd1 > failed-disk 2 > device /dev/sde1 > raid-disk 3 > ==== > > #mkraid --force /dev/md10 > > mark failed-disk as raid-disk and raidhotadd it. > > > Is this the right way to do it without screwing the array up? That should work (providing the chunk-size etc match your original array). However you would be much better off getting mdadm and using mdadm -A /dev/md10 --force /dev/sd[bcde]1 mdadm will automatically choose the best drives and force them to be up-to-date. Much less room for error. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
