Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DMA limited to UDMA33, non-ATA66 cable or device

Status
Not open for further replies.

linuxMaestro

Instructor
Jan 12, 2004
183
0
0
US
I got these errors right before my server crashed, any tips?
Sep 17 08:17:35 rev1 /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting
Sep 17 08:17:35 rev1 /kernel: ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device
Sep 17 08:17:35 rev1 /kernel: done
Sep 17 09:01:29 rev1 /kernel: ad0: READ command timeout tag=0 serv=0 - resetting
Sep 17 09:01:30 rev1 /kernel: ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device
Sep 17 09:01:30 rev1 /kernel: done
Sep 17 09:16:01 rev1 /kernel: ad0: READ command timeout tag=0 serv=0 - resetting
Sep 17 09:16:01 rev1 /kernel: ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device
Sep 17 09:16:02 rev1 /kernel: done
 
linuxMaestro,

In this instance what it's trying to tell you is that the drive is capable of higher transfer than the 40-pin cable allows.

However the READ command timeout may be much, much more serious. Download the drive diagnostic program from the hard drive manufacturer and run it.

The bad news is that your drive is probably dying. The good news is the sooner you run the diagnostic the better chance you have of the drive still being under warranty.

Wishdiak
 
I had similar messages and moved the drive to another machine and had no errors. It turns out that one of my two controllers is bad. Moving to the second controller took care of it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top