On Fri, Feb 5, 2010 at 1:19 AM, Keld Simonsen <keld@xxxxxxxxxx> wrote: > On Wed, Feb 03, 2010 at 03:57:58AM +0100, Keld Simonsen wrote: > Hi > > > can anybody help me with this? I am stuck with recovering my system here. > is it a sensible thing ro do? > > best regards > keld > >> Hi >> >> I got 2 arrays in error of the raid10 type. >> >> I think this is because my motherboard died, and then the fs were >> corrupted. >> >> My thoughts were that actually one of the copies could be correct. >> So I would like to try out the consistency of each part of the raid10 >> (it is 2-partition arrays), and then if I find one that is consistent, then >> resync the faulty one with the good one. >> >> How do I do this? >> >> it seems that I cannot just assemble an array with a missing part. >> If I assemble the full array, is there then a risk of the bad one >> corrupting the good one? And can I declare one of the disks faulty >> then test the other one, then declare nbr 2 disk for faulty and >> declare the first one as good? >> >> I dont see anything on the wiki on this. >> >> best regards >> keld > -- > 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 > I wish I could help more, but check out this from the mdadm man page: To create a "degraded" array in which some devices are missing, simply give the word "missing" in place of a device name. This will cause mdadm to leave the corresponding slot in the array empty. For a RAID4 or RAID5 array at most one slot can be "missing"; for a RAID6 array at most two slots. For a RAID1 array, only one real device needs to be given. All of the others can be "missing". Hope this helps! -- 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
