From owner-freebsd-stable Thu Sep 20 10: 8: 5 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 5D86C37B401 for ; Thu, 20 Sep 2001 10:08:01 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.11.3/8.9.3) id f8KH77l96638; Thu, 20 Sep 2001 10:07:07 -0700 (PDT) (envelope-from richw) Date: Thu, 20 Sep 2001 10:07:07 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: ad0: WRITE command timeout Message-ID: <20010920170128.96306.richw@wyattearp.stanford.edu> 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 Jason Andresen wrote: > > Have you tried checking for a loose cable? "Tenebrae" replied: > Yessir, I have. I suppose the cable could be going bad . . . > But I just wanted to eliminate any other possibilities. Another possibility might be overheating. I had one hard drive that started reporting timeout errors fairly often. I remounted it upside down (so the heat from the circuit board would rise away from the drive mechanism), and that helped some, but the errors still happened every so often. I later moved the drive to another machine with a larger case and more fans, and I haven't had any timeouts since. 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