From owner-freebsd-stable Sat Mar 17 16: 7: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171]) by hub.freebsd.org (Postfix) with ESMTP id AB09F37B718 for ; Sat, 17 Mar 2001 16:07:02 -0800 (PST) (envelope-from richw@wyattearp.stanford.edu) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id QAA52864; Sat, 17 Mar 2001 16:06:04 -0800 (PST) (envelope-from richw) Date: Sat, 17 Mar 2001 16:06:04 -0800 (PST) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: "M. L. Dodson" Cc: freebsd-stable@freebsd.org Subject: Re: disk hard read error: anything to be done? In-Reply-To: <200103161406.f2GE6TR00415@histidine.utmb.edu> Message-ID: <20010317234514.52474.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG M. L. (Bud) Dodson wrote: > ad0: HARD READ ERROR blk# 983151 status=59 error=40 > ad0: DMA problem fallback to PIO mode > Should I do anything about this . . . . Make sure the drive isn't getting too hot. Do you have adequate ven- tilation in the computer case? Are the fans working? Is there plenty of air flow around the drive? You might want to remount the drive upside down (with the circuit board on top); this may help keep the drive mechanism from overheating. You should always keep backups, of course, but you should =definitely= make sure you have a good backup of the data on =this= drive. Even if improving air flow makes the errors go away, the drive has given you fair warning that it's likely to die sooner rather than later. I had a drive myself, BTW, that was starting to give hard errors a few months ago. I remounted it upside down, with more space around it, and added another fan, and (touch wood!) I haven't had any more errors from this drive for about three months now. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message