Hi Mathias On Fri, Jan 27, 2012 at 12:30:36PM +0000, Mathias Burén wrote: [snip] > Hi, > > (this caters to question 1 & 2) > I run a 7x 2TB array myself, which has had 2 drive failure the last ~2 > years (the age of the array). The first time went smooth, MD kicked > out the bad drive almost immediately, and when I got the new drive it > rebuilt happily and everything was fine. The other time (see the last > few days on this mailing list) the drive wasn't kicked out straight > away - it kept retrying to read/write those bad sectors, and stalling > the entire system. I was unable to sync or anything, so I had to pull > the power, pull the bad disk, then power on the system again and > perform a RAID6 check (which turned out fine). > > Lesson learned, you'll want a drive to get kicked out ASAP if it's > reporting errors. When it's kicked out, you can test it yourself while > your RAID6 still chugs along, and if you can fix the errors, stick it > back into the array. If not, RMA the drive. Thank you for replying (you're the only one who has replied to these two questions). But it doesn't actually answer the question I have. The problem is that a disk has failed fully, and during rebuild, >1 disks among the remaining members are reporting read errors which were not known previously -> latent errors (see the figure in the email which started this topic). This is not an unlikely situation with RAID-6 and modern "end-user" SATA disks. How do we then go about fully or partially recovering data in the array? Kind regards, Mukund -- 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
