ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=xxx
tris at infoeng.flinders.edu.au
Fri Oct 1 04:01:30 PDT 2004
On Thu, 30 Sep 2004 19:14:01 -0600
Scott Long <scottl at FreeBSD.org> wrote:
> Tristan wrote:
> > On Thu, 30 Sep 2004 20:52:27 -0400
> > Ken Smith <kensmith at cse.Buffalo.EDU> wrote:
> >>On Fri, Oct 01, 2004 at 09:35:15AM +0930, Tristan wrote:
> >>>FreeBSD 6.0-CURRENT with GENERIC kernel built 27th Sep.
> >>>On a SunBlade 100 I see these messages regularly when
> >>>dma is enabled. The messages go away when I either use
> >>>atacontrol to set the mode to PIO4 or set hw.ata.ata_dma to 0
> >>>I do get data corruption on the disk if left in DMA mode.
> >>Just FYI my primary test machine is a SunBlade 100, it seems to
> >>be doing OK with a kernel built from this morning's source. I've
> >>been doing most of my builds from an NFS server though, I'll do
> >>a check with a full buildworld which will use the local drive more.
> >>>ad0: 14594MB <ST315310A/3.28> [29651/16/63] at ata2-master UDMA66
> >>>acd0: CDRW <LTN486S/YSU1> at ata2-slave PIO4
> >>>ata3-master: DMA limited to UDMA33, non-ATA66 cable or device
> >>>ad1: 39266MB <IBM-DTLA-305040/TW4OA60A> [79780/16/63] at ata3-master UDMA33
> >>>Mounted root from ufs:/dev/ad0a.
> >>Is the data corruption spread across both drives, or just ad1? That
> >>message about the cable or device being limited could be a clue.
> > nope, its only on ad0. ad1 seems to be fine, however it is hardly used.
> What happens if you remove the CDROM from the ad0 chain?
I still get the errors with the CDROM removed. Perhaps the cable needs
replacing? thats what these symptoms say to me.
More information about the freebsd-current