on 12/20/05 5:08 PM, Hauke Fath at hauke@Espresso.Rhein-Neckar.DE wrote:

> At 11:11 Uhr -1000 20.12.2005, Dan Wood wrote:
>> I've been getting beaten over the head with the following errors:
>> 
>> sd0(sbc0:0:0:0): Check Condition on CDB: 0x0a 13 <eight hex groups which
>> change>
>> SENSE KEY: Aborted Command
>> ASE/ASCQ: SCSI Parity Error
> 
> Is that with your SE/30? Which scsi driver do you use, ncrscsi or sbc?
> 
> I have a SUN branded Seagate 420 Meg disk that will produce an endless
> stream of parity errors with sbc, and phase errors with ncrscsi on a IIvx
> with netbsd-3...
> 
> hauke
> 
> --
> "It's never straight up and down"     (DEVO)
> 
> 
This is probably a stupid question, but have you played with the jumpers?
Have you journeyed over to the manufacturer's website?

I had a parity problem with a two gig Apple drive that I stuck in my Indy
earlier today.  kept getting SCSI failure and parity errors with NetBSD 2.1.
The solution was to tackle the jumpers and disable parity on the drive.

Works just fine now!