From owner-freebsd-current Mon Nov 29 23:43:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DAFB814D02 for ; Mon, 29 Nov 1999 23:43:31 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA07638; Tue, 30 Nov 1999 00:43:29 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA00649; Tue, 30 Nov 1999 00:43:47 -0700 (MST) Message-Id: <199911300743.AAA00649@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: AHC0 fireworks ? Cc: Gianmarco Giovannelli , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 25 Nov 1999 15:16:08 MST." <199911252216.PAA00144@narnia.plutotech.com> References: <199911252216.PAA00144@narnia.plutotech.com> Date: Tue, 30 Nov 1999 00:43:46 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911252216.PAA00144@narnia.plutotech.com> "Justin T. Gibbs" writes: : Parity errors indicate that data integrity is compromised on your SCSI : cable. Perhaps you bumped a connector, or a connector had been loose : for a long time and has just shifted to the point of causing a failure. : Open your case, reseat everything and see if the problem clears up. I've also seen parity errors where the drive generated '0' for its parity bit and needed a jumper setting changed. I've had three tape drives and one cd player do this to me over the years. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message