From owner-freebsd-questions@FreeBSD.ORG Fri Jan 6 20:02:35 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 21FCD106566B for ; Fri, 6 Jan 2012 20:02:35 +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 AD4BE8FC08 for ; Fri, 6 Jan 2012 20:02:34 +0000 (UTC) X-Footer: b3NlLm5s Received: from localhost ([127.0.0.1]) by mail.ose.nl (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Fri, 6 Jan 2012 21:02:31 +0100 Date: Fri, 6 Jan 2012 21:02:18 +0100 From: Bas Smeelen To: Warren Block Message-ID: <20120106210218.2f131d50@mpw> In-Reply-To: References: <20120105144204.d419cca4.web@3dresearch.com> <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> <4F069A44.7020600@ose.nl> <4F070CA6.5050803@ose.nl> <4F072484.9070100@ose.nl> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; i386-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org 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 20:02:35 -0000 On Fri, 6 Jan 2012 12:32:14 -0700 (MST) Warren Block wrote: > On Fri, 6 Jan 2012, Bas Smeelen wrote: > > > 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. > > > > I could use dd if=/dev/random of=file seek=blocks_to_skip bs=100M > > the next time > > Yes, if you're not worried about existing data. But use /dev/zero > (faster and you can verify the value) and bs=1M count=100 (ties up > only 1M of buffer space). Thanks a lot. This was always confusing me, now I know! Cheers Disclaimer: http://www.ose.nl/email