Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Dec 1999 12:02:22 -0500 (EST)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        <joeo@nks.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Errors from the ata disk driver
Message-ID:  <14418.32732.945550.170250@grasshopper.cs.duke.edu>
In-Reply-To: <Pine.LNX.4.10.9912110942440.13788-100000@homer.mkintl.com>
References:  <Pine.LNX.4.10.9912110942440.13788-100000@homer.mkintl.com>

next in thread | previous in thread | raw e-mail | index | archive | help

joeo@nks.net writes:
 > I've got a striped vinum partition that is occasionally going stale when
 > I get spurrious errors from the ata driver.
 > 
 > I can setstate the drives and the volume back up and an fsck of the
 > partition doesn't show any obvious corruption.
 > 
 > What do these errors indicate?
 > 
 > ad5: status=51 error=84
 > ad_interrupt: hard error
 > vinum0.p0.s3: fatal read I/O error
 > ad6: status=51 error=84
 > ad_interrupt: hard error
 > vinum0.p0.s4: fatal read I/O error
 > 
 > These drives are hanging off this controller;
 > ata-pci1: <Promise Ultra/33 IDE controller> irq 9 at device 9.0 on pci0
 > ata-pci1: Busmastering DMA supported

These are UDMA CRC errors.  Whatever you do, DO NOT upgrade to a
recent current without reading the ata driver's commit logs very
carefully.

The ata-driver has recently grown recovery code where it will try to
back down to PIO mode to fetch such blocks.  As recently as last week,
the ata driver would lock a machine solid (unpingable, reset or
power-cycle required) when attempting to back down to PIO mode when
the drive in question was attached to a Promise Ultra controller.

Soren knows about the problem & is going to fix it.

------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer	http://www.cs.duke.edu/~gallatin
Duke University				Email: gallatin@cs.duke.edu
Department of Computer Science		Phone: (919) 660-6590





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




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