From owner-freebsd-current Sat Dec 11 9: 3:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 86B6114F6B for ; Sat, 11 Dec 1999 09:02:59 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA17909; Sat, 11 Dec 1999 12:02:52 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA04015; Sat, 11 Dec 1999 12:02:22 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 11 Dec 1999 12:02:22 -0500 (EST) To: Cc: freebsd-current@freebsd.org Subject: Re: Errors from the ata disk driver In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14418.32732.945550.170250@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: 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