From owner-freebsd-stable Mon Aug 3 10:52:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06972 for freebsd-stable-outgoing; Mon, 3 Aug 1998 10:52:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06962 for ; Mon, 3 Aug 1998 10:52:18 -0700 (PDT) (envelope-from btman@ugcs.caltech.edu) Received: from localhost (btman@localhost) by lionking.org (8.9.1/8.9.1) with SMTP id KAA21858; Mon, 3 Aug 1998 10:51:59 -0700 (PDT) X-Authentication-Warning: lionking.org: btman owned process doing -bs Date: Mon, 3 Aug 1998 10:51:59 -0700 (PDT) From: Brian Tiemann X-Sender: btman@lionking.org To: Mike Smith cc: Chris , freebsd-stable@FreeBSD.ORG Subject: Re: WD errors In-Reply-To: <199808031612.JAA14148@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Aug 1998, Mike Smith wrote: > Your disk seems to be struggling with a bad block. The best thing to do > at this point is throw the disk out and get a new one, as with any > modern IDE disk you will only get to this point once all of the > available spare sectors have been used up. Be sure to test the disk, though, before pitching it... as I said earlier, in my experience with this particular problem I took the supposedly hosed disk home, ran the WD diags on it, and got a clean bill of health. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message