From owner-freebsd-questions@FreeBSD.ORG Fri Jan 6 16:42:47 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08164106574D for ; Fri, 6 Jan 2012 16:42:47 +0000 (UTC) (envelope-from b.smeelen@ose.nl) Received: from mail.ose.nl (mail.ose.nl [212.178.134.164]) by mx1.freebsd.org (Postfix) with ESMTP id 8D2708FC08 for ; Fri, 6 Jan 2012 16:42:46 +0000 (UTC) X-Footer: b3NlLm5s Received: from localhost ([127.0.0.1]) by mail.ose.nl (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)) for freebsd-questions@freebsd.org; Fri, 6 Jan 2012 17:42:44 +0100 Message-ID: <4F072484.9070100@ose.nl> Date: Fri, 06 Jan 2012 17:42:44 +0100 From: Bas Smeelen User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20120105144204.d419cca4.web@3dresearch.com> <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> <4F069A44.7020600@ose.nl> <4F070CA6.5050803@ose.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Apparently conflicting smartctl output X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2012 16:42:47 -0000 On 01/06/2012 04:37 PM, Warren Block wrote: > On Fri, 6 Jan 2012, Bas Smeelen wrote: > >> On 01/06/2012 03:39 PM, Warren Block wrote: >>> On Fri, 6 Jan 2012, Bas Smeelen wrote: >>> >>>> I have had this with a drive and multiple read errors would not >>>> remap the >>>> sector. >>>> With write errors the sector would be remapped. This was a new Samsung >>>> laptop drive though, not a Western Digital. >>> >>> That's standard. Sectors are only remapped to spares on a write error. >>> >>>> To get the sector remapped I had to fully write the drive and it >>>> was ok >>>> after that. >>> >>> Just writing to the sector should be enough. Of course, when one >>> sector >>> goes bad, others often follow. >> >> I just hope it does not develop more bad sectors. > > That's the worrying thing. Was it just a loose flake of oxide, or was > it a strip that peeled off the disk? No way to know I guess > >>> From what I read on the "Bad block HOWTO for smartmontools" on >>> sourceforge >> it's not trivial to just write to that sector and also it would >> destroy the >> filesystem? > > Finding the right block may not be too hard. /var/log/messages should > show the block number, but then I don't know what tool is available to > write to that specific block. Tools like that are not common because > generally, growing bad sectors means the drive is starting to fail > anyway. I could use dd if=/dev/random of=file seek=blocks_to_skip bs=100M the next time > >> So I just copied a big iso file several times untill the sector got >> remapped, the disk was almost full then. >> This is a brand new disk, maybe I should return it under warranty then, >> though it did not develop more bad sectors? > > If possible, yes. It already lost some data. > I'll talk to the supplier anyway when more bad sectors occur Cheers Disclaimer: http://www.ose.nl/email