bad days with scsi ...

[UseWhatEver]

this is my second problem with scsi for this week !! though this one is mayb solvabel :D ,
i have 2 scsi hd , linux (slackware 9) cant access the second one , the log is as follows

scsi0 : sym-2.1.17a
scsi1 : sym-2.1.17a
blk: queue cff2a174, I/O limit 4095Mb (mask 0xffffffff)
Vendor: SEAGATE Model: ST39140W Rev: 1498
Type: Direct-Access ANSI SCSI revision: 02
blk: queue cff2a274, I/O limit 4095Mb (mask 0xffffffff)
Vendor: SEAGATE Model: ST39173W Rev: 6244
Type: Direct-Access ANSI SCSI revision: 02
blk: queue cff2a374, I/O limit 4095Mb (mask 0xffffffff)
sym0:0:0: tagged command queuing enabled, command queue depth 16.
sym0:1:0: tagged command queuing enabled, command queue depth 16.
PCI: Assigned IRQ 11 for device 00:0d.0
PCI: Assigned IRQ 10 for device 00:0d.1
PCI: Sharing IRQ 10 with 00:12.2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
sym0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
SCSI device sda: 17783240 512-byte hdwr sectors (9105 MB)
Partition check:
sda: sda1 sda2 sda3 < sda5 >
sym0:1: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
sym0: SCSI parity error detected: SCR1=1 DBC=1100000e SBCL=ae
sdb : READ CAPACITY failed.
sdb : status = 4, message = 00, host = 0, driver = 00
sdb : sense not available.
sdb : block size assumed to be 512 bytes, disk size 1GB.
sdb:SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 0
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 2
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 4
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 6
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 0
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 2
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 4
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 6
ldm_validate_partition_table(): Disk read failed.
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 0
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 2
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 4
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 6
unable to read partition table

... whats the prob?

[mdwatts]

Originally posted by UseWhatEver

sym0: SCSI parity error detected: SCR1=1 DBC=1100000e SBCL=ae
sdb : READ CAPACITY failed.
sdb : status = 4, message = 00, host = 0, driver = 00
sdb : sense not available.
sdb : block size assumed to be 512 bytes, disk size 1GB.
sdb:SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8
I/O error: dev 08:10, sector 0
SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8


Did it work before without error?

Is the drive properly terminated, other jumpers set correctly and the scsi adapter bios configured for hdb?

Do you have a SCSI HD utility that can scan the drive for errors?

[DMR]

I'm with Mike on that one; check your cables and terminations carefully before anything else.

[banzaikai]

Howdy.

Make that three "look at the terminators" answers. I'll go a bit further, though...

The two Barracudas are "W" series, and have the terminators set differently than you'd think. Head over to

http://www.seagate.com/support/disc/scsi/st39173w.html

to see what I'm talking about. There are three different jumper blocks on this drive model (the 140 and 173 are the same series). The rear block only allows setting of the drive ID and activity LED. The front can be set to turn on/off termination, but it's actually the bottom block (J2) that you want to use. Not only do you need to know if the drive gets termed or not (the first and last devices get termed, the others do not), but you also need to know what device is supplying the power for the terms. If you know that the SCSI card isn't sending power to the bus, then each drive usually supplies it's own power for termination (but you can also have one of the drives supply for the whole bus). I'd double-check with the seagate website and report back.

Hope this helps...

banzai "narrow scsi" kai

[UseWhatEver]

im taking a look at the sites , thanx ppl ! but i just checked if winblows detects both scsi , and it deoes , disk managemnt shows also linux partions ! or is it that linux treats the scsi diffrently ...

[UseWhatEver]

i dont know about if it worked fine in the past with linux , its the first time the machine gets linux installed , and about a utility , i have no idea , ill gogle for one !

[banzaikai]

Momma said there'd be days like this...

Okay, let's see if Windows ignores that parity error (which might make sense, as the list of errors reported all seem to be on even-numbered sectors):

Go back to jumper block J2 on the sdb drive (the 39173W, if I read it correctly), and check the fourth one in from the right (labeled "PD" on the seagate diagram). If it's set, then pull it, if open, then set it (in other words, flip that bit).

We'll get this thing going eventually...

banzai "parroty error" kai