Hi Ramon, On 07/02/2012 06:12 AM, Ramon Hofer wrote: > On Die, 2012-06-26 at 15:23 -0500, Stan Hoeppner wrote: > >> Regardless, unless the dd commands hung in some way, they should not >> show up in top right now. So it's probably safe to assume they completed. >> >> So at this point you can try creating the RAID5 array again. If the dd >> command did what we wanted, /dev/sdk should have remapped the bad >> sector, and you shouldn't get the error kicking that drive. If you >> still do, you may need to replace the drive. > > I have successfully run dd for all the four drives. > > But because I couldn't create the raid I ran smartctl again for all of > them. It seems that sdk has to be replaced. Here are the outputs: > > sdj: > http://pastebin.com/raw.php?i=V60FJ4wC > > sdk: > http://pastebin.com/raw.php?i=cgfq3202 > There are some pre-fail and one FAILING_NOW messages. Absolutely take this drive back to your dealer. It has re-allocated over a thousand sectors. In my opinion, a drive should be put on a short-term (~3month) replacement list for the next convenient opportunity as soon as the first sector gets relocated. If you get more relocations in quick succession, replace immediately. > sdl: > http://pastebin.com/raw.php?i=tipjbpxu Interesting. This drive claims to support SCTERC. I was under the impression the EARS drives didn't. Could you please show the output of "smartctl -l scterc /dev/sdl" ? Regards, 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
