Thomas Kenyon wrote: > My server at home operates a 4 disk software RAID 5 array which is > normally mounted at /. > > At the moment I am using mdadm v2.6.7.2 (I don't know which version > built the array). Also kernel version. > One of the disks appeared to have developed a fault, an I/O error > would be produced and the array would rebuild to try and mao round it, > and once it had finished there'd be another I/O error and it would > start again. > > I marked the drive as faulty, removed it from the array, replaced it > with a nother drive, replicated the partition map and added it to the > array. > > As expected the drive started being built. Good > I'm not sure if it had finished by this point, but another disk > produced an I/O error which broke the array. During the rebuild? That doesn't make sense since below it's showing 'clean'. Are you sure the rebuild didn't finish? If not then you may need expert support (probably from Neil on monday). I suggest digging out the logs to see. > Now I'm trying to recover any data I can from it. Normally with the data you describe below the /dev/sd[abd]1 partitions would happily create a degraded array. However if you are sure sdb is broken then I'd wait. > When I first try to assemble the array, this message appears in kernel messages. command? David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- 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
