From owner-freebsd-scsi Sun Apr 8 8:24:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 77FAC37B424 for ; Sun, 8 Apr 2001 08:24:12 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f38FNRs98477; Sun, 8 Apr 2001 09:23:38 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104081523.f38FNRs98477@aslan.scsiguy.com> To: Cor Bosman Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: parity error In-Reply-To: Your message of "Sun, 08 Apr 2001 16:03:06 +0200." <200104081403.QAA04705@xs4.xs4all.nl> Date: Sun, 08 Apr 2001 09:23:27 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >And then im suddenly able to revive the vinum mirror again, and no more >parity errors occur. Reboot into 4.2, and i immediately get parity errors >again. And so on. Anyone seen this before? Bad disk or cable even though >4.1 doesnt complain? Or maybe go to stable? IIRC, 4.1R did not run the U160 controllers in U160 mode. By booting back to 4.1, you effectively reduce the negotiated transfer speed and avoid stressing the bus to the point of failure. The moral of the story is that some part of your bus is not up to running at 160MB/s. It could be the cable, or the terminator, or the bus length. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message