From owner-freebsd-stable@FreeBSD.ORG Sat Jun 25 18:32:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 8C6B516A41C for ; Sat, 25 Jun 2005 18:32:36 +0000 (GMT) (envelope-from richw@richw.org) Received: from smtp3.Stanford.EDU (smtp3.Stanford.EDU [171.67.16.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 721D743D48 for ; Sat, 25 Jun 2005 18:32:36 +0000 (GMT) (envelope-from richw@richw.org) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp3.Stanford.EDU (8.12.11/8.12.11) with ESMTP id j5PIWZ2N027766 for ; Sat, 25 Jun 2005 11:32:35 -0700 Received: from whodunit.richw.org (localhost [127.0.0.1]) by whodunit.richw.org (8.13.1/8.13.1) with ESMTP id j5PIWXFF081339; Sat, 25 Jun 2005 11:32:33 -0700 (PDT) (envelope-from richw@whodunit.richw.org) Received: (from richw@localhost) by whodunit.richw.org (8.13.1/8.13.1/Submit) id j5PIWXF7081338; Sat, 25 Jun 2005 11:32:33 -0700 (PDT) (envelope-from richw) Date: Sat, 25 Jun 2005 11:32:33 -0700 (PDT) From: Rich Wales To: freebsd-stable@freebsd.org In-Reply-To: <42BD0926.8000804@earthmagic.org> Message-ID: <20050625182203.R79928.richw@whodunit.richw.org> References: <8d02aed00506181404642100b9@mail.gmail.com> <42BC5353.1090807@earthmagic.org> <8d02aed005062412001c7903b3@mail.gmail.com> <42BD0926.8000804@earthmagic.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: ATA_DMA errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jun 2005 18:32:36 -0000 I had a READ_DMA timeout situation which I'm pretty sure was related to a drive problem. I'm running 5.3-RELEASE-p5 on an older machine (333 MHz AMD K6). The 20 GB hard drive in this system periodically, but only occasionally, gave READ_DMA timeout errors. These errors sometimes cited identical block (LBA) numbers from one time to the next. I tried running the system with the case open, in case it was an overheating problem, but this had no effect. I considered replacing the power supply, but I never got around to doing this. Finally, about a week ago, I copied the entire system to a new hard drive. So far, I haven't had even one READ_DMA error since going to the new hard drive. At least in this one case, it seems fairly certain that the problem has something to do with a particular hard drive. Curiously, I did =not= get any READ_DMA errors while I was making a full backup of the old drive in preparation for copying the data onto the new drive. Rich Wales richw@richw.org http://www.richw.org