Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Apr 2001 09:23:27 -0600
From:      "Justin T. Gibbs" <gibbs@scsiguy.com>
To:        Cor Bosman <cor@xs4all.net>
Cc:        freebsd-scsi@FreeBSD.ORG
Subject:   Re: parity error 
Message-ID:  <200104081523.f38FNRs98477@aslan.scsiguy.com>
In-Reply-To: Your message of "Sun, 08 Apr 2001 16:03:06 %2B0200." <200104081403.QAA04705@xs4.xs4all.nl> 

next in thread | previous in thread | raw e-mail | index | archive | help
>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




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