From owner-freebsd-fs@FreeBSD.ORG Tue Aug 10 02:03:41 2004 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 E597116A4CE for ; Tue, 10 Aug 2004 02:03:40 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEEC143D1F for ; Tue, 10 Aug 2004 02:03:40 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id B154272DF2; Mon, 9 Aug 2004 19:03:40 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id AC71B72DB5; Mon, 9 Aug 2004 19:03:40 -0700 (PDT) Date: Mon, 9 Aug 2004 19:03:40 -0700 (PDT) From: Doug White To: DH In-Reply-To: <20040803185856.28834.qmail@web20423.mail.yahoo.com> Message-ID: <20040809185545.K80973@carver.gumbysoft.com> References: <20040803185856.28834.qmail@web20423.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-fs@freebsd.org Subject: Re: How to read bad blocks error message & marking of same 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: Tue, 10 Aug 2004 02:03:41 -0000 On Tue, 3 Aug 2004, DH wrote: > I've begun rec'ing these error messages: > ad0s1a: hard error reading fsbn 141935 of 70848 - 71103 (ad0s1 bn > 141935; cn 8 tn 212 sn 59 ) status=59 error=40 > > Got about 7 of these with varying values. Yay disk errors. The interesting number is the 'fsbn' which is the block number. > I ran Seagate's diag utility and it reported only 1 bad block. > Unfortunately ad0s1a happens to my / dir so allowing the utility to > write zeros to that block hasn't sat well with me. Odd it only found one when the fsbn changes. Unfortunately you don't have much choice in the matter; you either get the bad block errors and "Input/Output error" messages when accessing the file, or if you zero it, the block will be remapped but whatever file is there is corrupted. That file is already corrupted is zeroing part of it is probably an improvement. :) A backup is recommended, if you can get one. That may identify where the faulty file is. If its non-critical, then zero the block with the Seagate tool, then delete the file afterward. I stronly suggest a full fsck afterwards on the affected volume after any repair operation. Boot single user and use fsck -y. If it is / thats affected you may need to boot off a CD so you can write the root volume for the fsck. > ad0s1 bn 141935 ? This is the device and offset into the device. In this case ATA disk 0, slice 1. The stuff after this is mostly interesting to developers. > cn 8 ? > > tn 212 ? > > sn 59 ? Cylinder, track, and sector, I think. > status = 59 ? > error = 40 ? ATA status and error registers. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org