From owner-freebsd-fs@FreeBSD.ORG Fri Feb 25 00:31:18 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDEB316A4CE for ; Fri, 25 Feb 2005 00:31:18 +0000 (GMT) Received: from S2.cableone.net (smtp2.cableone.net [24.116.0.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C5EA43D1F for ; Fri, 25 Feb 2005 00:31:18 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.local.lan (unverified [24.119.123.70]) by S2.cableone.net (CableOne SMTP Service S2) with ESMTP id 11526121 for multiple; Thu, 24 Feb 2005 17:39:29 -0700 Date: Thu, 24 Feb 2005 18:30:29 -0600 From: Vulpes Velox To: "Poul-Henning Kamp" Message-ID: <20050224183029.4617e852@vixen42.local.lan> In-Reply-To: <8879.1109263777@critter.freebsd.dk> References: <53844.194.225.42.20.1109263952.squirrel@ce.sharif.edu> <8879.1109263777@critter.freebsd.dk> X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IP-stats: Incoming Last 2, First 53, in=8, out=0, spam=0 X-External-IP: 24.119.123.70 X-Abuse-Info: Send abuse complaints to abuse@cableone.net cc: freebsd-fs@freebsd.org Subject: Re: badsect X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 00:31:19 -0000 On Thu, 24 Feb 2005 17:49:37 +0100 "Poul-Henning Kamp" wrote: > In message <53844.194.225.42.20.1109263952.squirrel@ce.sharif.edu>, > falaki@ce.s harif.edu writes: > >Hello; > > > >I have a hard disk that seems to have some limitted number of bad > >sectors. I want to use badsect to avoid these errors. > > > > ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=27546816 > > ad0: FAILURE - READ_DMA timed out > > > >I tried this: > > > > #badsect /mnt/data 27546816 > > > >and got: > > > > block 27546816 out of range of file system > > don't forget to run fsck ... > > > >What should I do? > > You should let your disk deal with it. > > Try booting single user and: > > dd if=/dev/ad0 of=/dev/null bs=1m > > and see how much damage there actually is. > > If there is much damage, you may want to use > src/tools/tools/recoverdisk > instead Hmm, when might this make it into releng_5?