From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Stefan G. Weichinger" Subject: Re: raid5+hotspare: request for recommended procedure Date: Wed, 29 Sep 2010 14:42:45 +0200 Message-ID: <4CA33445.7030408@xunil.at> References: <4CA300EB.1070909@xunil.at> <4CA30EF5.8020702@seoss.co.uk> Reply-To: lists@xunil.at Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4CA30EF5.8020702@seoss.co.uk> Sender: linux-raid-owner@vger.kernel.org To: "linux-raid@vger.kernel.org" List-Id: linux-raid.ids 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. I will do that maybe after the repair-action is through ... Could you tell me in detail what you mean by "dd over it" ? Write zeros there or what ...? > 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. You know I really hesitate with such low-level-stuff as the server is far away and I won't be able to just boot from a live-cd or something ... so I am very cautious with my steps. Thanks so far, Stefan