Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Jun 2005 11:32:33 -0700 (PDT)
From:      Rich Wales <richw@richw.org>
To:        freebsd-stable@freebsd.org
Subject:   Re: ATA_DMA errors
Message-ID:  <20050625182203.R79928.richw@whodunit.richw.org>
In-Reply-To: <42BD0926.8000804@earthmagic.org>
References:  <8d02aed00506181404642100b9@mail.gmail.com> <42BC5353.1090807@earthmagic.org> <8d02aed005062412001c7903b3@mail.gmail.com> <42BD0926.8000804@earthmagic.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050625182203.R79928.richw>