From owner-freebsd-questions@FreeBSD.ORG Wed Oct 29 11:08:56 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E85216A4CE for ; Wed, 29 Oct 2003 11:08:56 -0800 (PST) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC5043FB1 for ; Wed, 29 Oct 2003 11:08:49 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 1CCE63AB7; Wed, 29 Oct 2003 14:08:49 -0500 (EST) Sender: lowell@be-well.ilk.org To: Jer References: <6.0.0.22.0.20031028165105.01ba0298@computer.multihaven.org> From: Lowell Gilbert Date: 29 Oct 2003 14:08:48 -0500 In-Reply-To: <6.0.0.22.0.20031028165105.01ba0298@computer.multihaven.org> Message-ID: <44vfq7dfpb.fsf@be-well.ilk.org> Lines: 32 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: questions@freebsd.org Subject: Re: Surface scan for Freebsd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2003 19:08:56 -0000 Jer writes: > I have a feeling one of my disks is going south > Oct 28 11:28:40 computer /kernel: ad1: WRITE command timeout tag=0 > serv=0 - > resetting > Oct 28 11:28:40 computer /kernel: ata0: resetting devices .. done > Oct 28 11:28:55 computer /kernel: ad1: WRITE command timeout tag=0 > serv=0 - > resetting > Oct 28 11:28:55 computer /kernel: ata0: resetting devices .. done > Oct 28 11:29:06 computer /kernel: ad1: WRITE command timeout tag=0 > serv=0 - > resetting > Oct 28 11:29:06 computer /kernel: ata0: resetting devices .. done Actually, this doesn't show any signs of problems with the disk surface itself. The firmware on the drive is failing to report back when the disk controller was execpecting it to. I think the drive cable is the most common problem when this occurs, although the drive or the controller can be reponsible too. I've been getting these messages on my -STABLE machine for the last couple of weeks or so whenever the disk is stressed. I haven't yet gotten around to trying a new drive cable. > how can i do a surgace scan of sorts so I can make them with badblock? Aside from the fact that you're treating the wrong problem, you can't do that within FreeBSD. Modern drives do such sophisticated bad-block mapping internally that it is no longer worthwhile to maintain such facilities in the OS.