On 10/25/2013 06:47 AM, yuji_touya@xxxxxxxxxxxxxxxxxxxx wrote: > Phil, > >>> Device Model: ST2000DM001-9YN164 >> >> If I recall correctly, this model doesn't support error recovery >> control. If you haven't fixed your driver timeouts, it explains your >> situation. > > I had been believing that nowadays all hdd drive can reallocate bad sectors. > It is wrong, right? Yes and no. Yes, all modern hard drives can reallocate bad sectors. No, they can't do so until that sector is *written*. Since you can't read the data, and you need to write it to fix it, you need to get that data from a redundant location. The kernel MD module will do this on a running array when it encounters a read error. Your problem is that your drives do not report read errors before the low level kernel driver (not MD) times out (30 seconds). Non-raid drives typically take over two minutes to report a read error. When the kernel driver times out, it attempts to reset the connection to the drive. But the drive is still trying to read, and ignores the reset. So when MD tries to write the sector to repair it, the drive appears to be disconnected. *BOOM* When you look at it a little later, it appears to be fine (and it probably is). > I had not fixed driver timeouts. It's a new word to me. > I wonder these settings are required to use rest Seagate drives (sdd and sde). Please search the list archives. I've explained in detail many times in the past few years. And yes, you need to deal with the problem for all of your drives. > I'll use RAID-capable drives when exchanging kicked out disks. > Thank you for your advice. > > I'm learnning a lot through my problem and really thank to linux-raid community, > people helped me, and of course software RAID system. ;-) You're welcome. Phil -- 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
