From owner-freebsd-stable Sun Mar 9 5:29:57 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E96CB37B401 for ; Sun, 9 Mar 2003 05:29:55 -0800 (PST) Received: from aurora.siteplus.com (aurora.siteplus.com [66.129.2.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 736C943FE3 for ; Sun, 9 Mar 2003 05:29:45 -0800 (PST) (envelope-from jim@jwweeks.com) Received: from veager.jwweeks.com (pcp03144169pcs.midval01.tn.comcast.net [68.59.246.106]) by aurora.siteplus.com (8.12.8/8.12.6) with ESMTP id h29DTk1C059989; Sun, 9 Mar 2003 08:29:48 -0500 (EST) (envelope-from jim@jwweeks.com) Date: Sun, 9 Mar 2003 08:29:20 -0500 (EST) From: Jim Weeks To: Barry Irwin Cc: Olivier Saut , Subject: Re: Bad hardware? In-Reply-To: <020f01c2e4b0$bb1d93d0$4508a8c0@Beastie> Message-ID: <20030309082733.L6631-100000@veager.jwweeks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 7 Mar 2003, Barry Irwin wrote: > Quote possibly, however try another IDE cable first, this could be the cause > of the problem. You might carefully consider your cooling also. I have found that Seagate drives run extremely hot and will cause these hard write errors when in that state. -- Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message