--- On Wed, 29/9/10, Stefan G. Weichinger <lists@xxxxxxxx> wrote:
> From: Stefan G. Weichinger <lists@xxxxxxxx>
> Subject: Re: raid5+hotspare: request for recommended procedure
> To: "linux-raid@xxxxxxxxxxxxxxx" <linux-raid@xxxxxxxxxxxxxxx>
> Date: Wednesday, 29 September, 2010, 15:25
> Am 2010-09-29 12:03, schrieb Tim
> Small:
>
> > Run smartctl -t long, and see what the LBA of the
> errors are (smartctl
> > -a when finished, and look at the error log) - it may
> be that it is
> > outside of the used space (e.g. right at the end of
> the drive - I've
> > seen this in the past) if this is the case, you can
> just dd over it.
> >
> > If the test completes without error then the
> unreadable sector is either
> > not user-addressable, or doesn't really exist, in
> which case I'd ignore
> > it (or perhaps a security-erase will get the drive
> back into a sensible
> > state). Some of the earlier firmwares for the
> ST3250310NS were a little
> > buggy in my experience, so you might want to look at
> upgrading it
> > (latest Seagate non-OEM firmware is SN06), which can
> be done with hdparm.
>
> Yep, it finished without error!
>
> Does that mean I could ignore that safely?
>
> Or should I rebuild the raids onto the spare-disk and then
> swap drive?
>
> S
> --
Personally I would trust nothing less than a dammed good thrashing from badblocks -svw ideally or -svn if the drive has data on it. Then an smart offline check to be sure the pending/reallocated sector counts have no increased.
Before commissioning a new drive a do a badblocks -svw atleast 3 times without any counters increasing (something there are bad sectors I just want to flush them out early) then I do some short, long and offline smart tests.
Then I add to the array, then I run check a couple of times.
--
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
