This morning I found a frozen box. On the console was this: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ata0-slave: ATA identify retries exceeded done After reboot, those messages were found in /var/log/messages. I'm running FreeBSD 4.8-RC from Apr 4 10:45:49 EST 2003. Any ideas? -- Dan Langille : http://www.langille.org/
On Sun, 18 May 2003, Dan Langille wrote:> This morning I found a frozen box. On the console was this: > > ad0: READ command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. ata0-slave: ATA identify retries exceeded > done > > After reboot, those messages were found in /var/log/messages. > > I'm running FreeBSD 4.8-RC from Apr 4 10:45:49 EST 2003. > > Any ideas?Hey dvl, I've had similar problems. This has come up a few times on the mailing list in the past, especially regarding certain lines of IBM drives. Suggestions include replacing your IDE cable, making sure it's not longer than 18 inches...and replacing the drive as it's probably on its last leg. Back it up while you can. -Tenebrae. --- The sending of any unsolicited email advertising messages to this domain may result in the imposition of civil liability against you in accordance with Cal. Bus. & Prof. Code Section 17538.45.
On 19 May 2003 at 8:42, Tenebrae wrote:> On Sun, 18 May 2003, Dan Langille wrote: > > > This morning I found a frozen box. On the console was this: > > > > ad0: READ command timeout tag=0 serv=0 - resetting > > ata0: resetting devices .. ata0-slave: ATA identify retries exceeded > > done > > > > After reboot, those messages were found in /var/log/messages. > > > > I'm running FreeBSD 4.8-RC from Apr 4 10:45:49 EST 2003. > > > > Any ideas? > > Hey dvl, > I've had similar problems. This has come up a few times on the mailing > list in the past, especially regarding certain lines of IBM drives.ad0: 516MB <QUANTUM MAVERICK 540A> [1049/16/63] at ata0-master PIO3 For what it's worth, it's been in there since the box was put together in November 2000 and this is the first indication of a problem. It's probably getting old.> Suggestions include replacing your IDE cable, making sure it's not longer > than 18 inches...and replacing the drive as it's probably on its last leg. > Back it up while you can.Luckily, it's not really an important drive (from a data point of view) in this system: $ df | grep ad0 /dev/ad0s1a 99183 50162 41087 55% / /dev/ad0s1e 413695 1 380599 0% /slow I'll get a new drive in there ASAP. I'm glad it's not the SCSI drives which are failing: $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 99183 50162 41087 55% / /dev/da1s1f 17130052 15553651 205997 99% /home /dev/ad0s1e 413695 1 380599 0% /slow /dev/da0s1e 17130052 10675758 5083890 68% /usr /dev/da1s1e 254063 156203 77535 67% /var procfs 4 4 0 100% /pro -- Dan Langille : http://www.langille.org/
On Fri, May 23, 2003 at 05:19:54PM -0400, Chuck Swiger wrote:> Thomas Nystrom wrote: > [ ... ] > >The message I see on the console is: > > ad1: READ command timeout tag=0 serv=0 - resetting > > ata0: resetting devices.... > > > >and the machines hangs there with the disk indicator LED turned on but > >without any disc activity. > > Ditto. Problem seemed to appear sometime after 4.7p10.This and other problems appeared after 4.5R (after MFC new ATA driver) -- Vladislav V. Zhuk (06267)3-60-03 admin@dru.dn.ua 2:465/197@FidoNet.org