From owner-freebsd-questions Tue Jan 20 14:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13668 for questions-outgoing; Tue, 20 Jan 1998 14:43:56 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from allegro.lemis.com ([192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13655 for ; Tue, 20 Jan 1998 14:43:44 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id JAA09266; Wed, 21 Jan 1998 09:13:32 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id JAA03693; Wed, 21 Jan 1998 09:13:31 +1030 (CST) (envelope-from grog) Message-ID: <19980121091331.40808@lemis.com> Date: Wed, 21 Jan 1998 09:13:31 +1030 From: Greg Lehey To: "Paul T. Root" Cc: questions@FreeBSD.ORG Subject: Re: Hard disk going bad? References: <19980120094523.42131@lemis.com> <199801201348.HAA20395@horton.iaces.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199801201348.HAA20395@horton.iaces.com>; from Paul T. Root on Tue, Jan 20, 1998 at 07:48:56AM -0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Tue, Jan 20, 1998 at 07:48:56AM -0600, Paul T. Root wrote: > In a previous message, Greg Lehey said: >> On Mon, Jan 19, 1998 at 07:59:09AM -0600, Paul T. Root wrote: >>> Hi, >>> From my daily output, I got these messages. I have a 2940UW and >>> sd1 is a SEAGATE ST19171W. sd0 is a SEAGATE ST32550W. There is nothing >>> else on the SCSI bus. I'm running 2.2.5-Release. >>> >>> Is this disk going out? >> >> Quite possibly. Have you changed anything recently? >> >> Greg > > Nope, it's been up for a month. I did a make buildworld, make installworld > on it at that time. It took several tries on the buildworld, I'm told that's > a cache problem, but it did finally succeed. Then I'm afraid it's probably a dying disk. You could check cables, simply because it's a thing to do, but I don't think it'll change anything. Greg