On Oct 10, 2012, at 8:42 PM, hanguozhong wrote: > > I did not save the outputs of smartctl, but I remember that the “RAW_VALUE” > of the attribute whose name was“Current_Pending_Sector” of sdb was 1. Did that > indicate that the drive was bad? Just one sector is bad. But there are other attributes, maybe the disk isn't spinning up, maybe there are a lot of other read errors or uncorrected ECC errors. So I think we need more data. smartctl -A /dev/sdb > If the drive was not bad, what is the best way to relocate > these bad sectors to spare? I have been using the tool "HDD_Regenerator" running in windows, > which is too slow. Each relocation took dozens of hours. It takes a long time to find the bad sector. > If you have any better idea, please let me know. Bad sectors can be like mice. Chances are, you've got more than one. I would obliterate the disk with Secure Erase. It's faster than writing zeros with dd. But I question why normal usage isn't causing the sectors to be reallocated and you continue to have errors. I personally would replace the disk, and get the array back to normal health, and then futz with the misbehaving drive on a separate system - if this is an important array. Chris Murphy -- 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
