From owner-freebsd-current Sat Dec 11 9:30:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C086B14C97 for ; Sat, 11 Dec 1999 09:30:48 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA04573; Sat, 11 Dec 1999 18:30:35 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912111730.SAA04573@freebsd.dk> Subject: Re: Errors from the ata disk driver In-Reply-To: from "joeo@nks.net" at "Dec 11, 1999 09:49:57 am" To: joeo@nks.net Date: Sat, 11 Dec 1999 18:30:34 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems joeo@nks.net wrote: > 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 These are UDMA CRC errors, if you upgrade to the latest current, ata knows to retry these, only if they persist, something is wrong. However it could indicate cable problems, ie bad connectors or maybe too long cables.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message