scsi parity error

kev82 · 09-14-2004, 05:51 PM

i know almost nothing about scsi so dont assume the obvious

<edit>im using the sym53c8xx driver in 2.6.8</edit>

i have two scsi drives, both on the same cable, if i connect either on its own then everything works fine, but when i connect them together i get scsi parity errors and only 1 works. attached is a copy of the relevant part of my dmesg

i found quite a few threads with similar questions but none with answers, thats why i posted.

Code:

sym0: <896> rev 0x7 at pci 0000:00:0a.0 irq 18
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18j
sym1: <896> rev 0x7 at pci 0000:00:0a.1 irq 19
sym1: No NVRAM, ID 7, Fast-40, SE, parity checking
sym1: SCSI BUS has been reset.
sym1: SCSI BUS mode change from SE to SE.
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.18j
sym1:0: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 31)
  Vendor: COMPAQ    Model: MAB3045SP         Rev: 0814
  Type:   Direct-Access                      ANSI SCSI revision: 02
sym1:0:0: tagged command queuing enabled, command queue depth 16.
scsi(1:0:0:0): Beginning Domain Validation
sym1:0: asynchronous.
sym1:0: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 31)
scsi(1:0:0:0): Domain Validation skipping write tests
scsi(1:0:0:0): Ending Domain Validation
sym1:10: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 15)
  Vendor: COMPAQ    Model: HD00431731        Rev: 3208
  Type:   Direct-Access                      ANSI SCSI revision: 02
sym1:10:0: tagged command queuing enabled, command queue depth 16.
scsi(1:0:10:0): Beginning Domain Validation
sym1:10: asynchronous.
sym1:10: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 15)
scsi(1:0:10:0): Domain Validation skipping write tests
scsi(1:0:10:0): Ending Domain Validation
sda: Spinning up disk...............<6>sym1:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 31)
ready
sym1: SCSI parity error detected: SCR1=3 DBC=11000000 SBCL=29
sym1: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29
sym1:0:control msgout: c.
sym1: TARGET 0 has been reset.
sym1:0:0: ABORT operation started.
sym1:0:0: ABORT operation complete.
sym1: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29
sym1:0:0: DEVICE RESET operation started.
sym1:0:0: DEVICE RESET operation complete.
sym1:0:control msgout: c.
sym1: TARGET 0 has been reset.
sym1:0:0: ABORT operation started.
sym1:0:0: ABORT operation complete.
sym1:0:0: BUS RESET operation started.
sym1:0:0: BUS RESET operation complete.
sym1: SCSI BUS reset detected.
sym1: SCSI BUS has been reset.
sym1: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29
sym1:0:0: HOST RESET operation started.
sym1: SCSI BUS has been reset.
sym1:0:0: HOST RESET operation complete.
sym1: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29
scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
sym1:0:control msgout: c.
sym1: TARGET 0 has been reset.
scsi1 (0:0): rejecting I/O to offline device
scsi1 (0:0): rejecting I/O to offline device
sda : READ CAPACITY failed.
sda : status=1, message=00, host=7, driver=04 
sda : sense not available. 
scsi1 (0:0): rejecting I/O to offline device
sda: asking for cache data failed
sda: assuming drive cache: write through
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
sdb: Spinning up disk.............<6>sym1:10: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
ready
SCSI device sdb: 8386000 512-byte hdwr sectors (4294 MB)
SCSI device sdb: drive cache: write through
 /dev/scsi/host1/bus0/target10/lun0: p1
Attached scsi disk sdb at scsi1, channel 0, id 10, lun 0

michaelk · 09-14-2004, 06:12 PM

Is the SCSI bus terminator configured properly?
Have you verified the SCSI bus IDs are correct?
How long is the SCSI cable?
Are these internal or external drives?

kev82 · 09-14-2004, 06:35 PM

by michaelk
Is the SCSI bus terminator configured properly?

i assume thats the thing on the end of the cable, it has no jumpers so i dont know if its configured correctly or how to configure it if it isnt

<edit2>its always the one furthest from the host adapter that doesnt work when both are plugged in, this(and what ive read) leads me to believe that both drives are acting as terminators so whichever drive is first terminates the the other one, but i cant see an obvious jumper to change this</edit2>

Have you verified the SCSI bus IDs are correct?

i believe so, in one of the drives i have no jumpers in id0-4 which should be id=0, in the other i have 1 jumper in id0 which should be id=1
<edit>ive just confirmed this in /proc/scsi/scsi</edit>

How long is the SCSI cable?

about 2ft, maybe a little longer

Are these internal or external drives?

internal

one of the drives has a 68pin connector, the other has an 80pin connector, i am using a 68-80pin converter thing with this drive, if i unplug the drive but keep that connected i still get parity errors