Date: Wed, 23 Jan 2002 12:31:08 -0700 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: Dave Hayes <dave@jetcafe.org> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 29160 woes Message-ID: <200201231931.g0NJV8u77642@aslan.scsiguy.com> In-Reply-To: Your message of "Wed, 23 Jan 2002 10:11:36 PST." <200201231811.KAA17997@hokkshideh.jetcafe.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>I get SCSI parity errors trying to disklabel the last drive on the >2nd card (da5). These are actually CRC errors. >Suspecting the disk, I checked and scanned da5 by the BIOS verify >utility. It's perfectly fine. The Adaptec BIOS may have negotiated down to a speed that allowed the verify to proceed. FreeBSD's SCSI layer doesn't have any speed fallback support yet. The BIOS won't tell you if it has done this. >Interestingly enough, the following: > > dd if=/dev/zero of=/dev/rda5s1 It is the target's responsibility to check the CRC or parity during a write. This just means that the target is able to read what we are writing to it okay, but we are not always able to read what the target is writing to us. >Anyone have any clues as to what is going on...before I completely >replace these controller cards? ;) I doubt it is the controller. I would suspect the drive has a bad connector. Do you get the same behavior if you force narrow-async on this drive via SCSI-Select? -- 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?200201231931.g0NJV8u77642>