Goat needed
David Lesher
SCSI is NOT magic. There are fundamental technical reasons why it is
necessary to sacrifice a young goat to your SCSI chain now and then.
John Woods
So I've got an existing LVD SCSI chain with a Quantum - Adic tape
jukebox. I went to add 4 IBM DHRS drives to the picture.
These drives use the simple SCA to 68 pin adapters to feed the drive and
set the ID. [You can find them on eBay.]
So we set their addresses [8/9/10/11], connected up the 68 pin cable, put
a differential term on the end, and connected it to the other channel on
the Adaptec in the SPARC.
No joy; no drives appear. So we pull the terminator from the other
channel, with a LVD DLT silo on ID's 0 & 1; hooked the cable to it and
rebooted again. Still no joy, but the tape was still happy.
We swapped out the cable; no change. Both the cables and the channels
work on the silo.
I can believe one disk would be bad and invisible, but not all four.
Suggestions, or do I start lookng for a goat?
--
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433
Michael Baeuerle
>
> So I've got an existing LVD SCSI chain with a Quantum - Adic tape
> jukebox. I went to add 4 IBM DHRS drives to the picture.
>
> These drives use the simple SCA to 68 pin adapters to feed the drive and
> set the ID. [You can find them on eBay.]
Have you checked that the adapters work with a known good disk?
> So we set their addresses [8/9/10/11], connected up the 68 pin cable, put
> a differential term on the end, and connected it to the other channel on
> the Adaptec in the SPARC.
Which Adaptec in which machine?
> No joy; no drives appear. So we pull the terminator from the other
> channel, with a LVD DLT silo on ID's 0 & 1; hooked the cable to it and
> rebooted again. Still no joy, but the tape was still happy.
>
> We swapped out the cable; no change. Both the cables and the channels
> work on the silo.
>
> I can believe one disk would be bad and invisible, but not all four.
If other devices work on the bus your disks should at least be detected.
IMHO most likely the adapters are bad.
Micha
David Lesher
>> These drives use the simple SCA to 68 pin adapters to feed the drive and
>> set the ID. [You can find them on eBay.]
>Have you checked that the adapters work with a known good disk?
Yes, they worked on other drives with an Intel-based Debian distro.
>> So we set their addresses [8/9/10/11], connected up the 68 pin cable, put
>> a differential term on the end, and connected it to the other channel on
>> the Adaptec in the SPARC.
>Which Adaptec in which machine?
Enterprise Sparc 250; I don't know the Adaptec adapter model but it
reports back as:
$ cat /proc/scsi/sym53c8xx/2
Chip sym53c875, device id 0xf, revision id 0x14
On PCI bus 0, device 4, function 0, IRQ 4,7d8
Min. period factor 12, Wide SCSI BUS
Max. started commands 1022, max. commands per LUN 64
>> I can believe one disk would be bad and invisible, but not all four.
>If other devices work on the bus your disks should at least be detected.
>IMHO most likely the adapters are bad.
They are rather simple
<http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3D140327919407> or
very similar; and I'm at a loss to explain how 4 would be "dead"...
I'm going to move cables & term around so that the drives come before the
tape BU; that way we can least confirm the cables are 100% intact.
Michael Baeuerle
> Michael Baeuerle writes:
> >
> > Have you checked that the adapters work with a known good disk?
>
> Yes, they worked on other drives with an Intel-based Debian distro.
Are these "other drives" also LVD?
> > Which Adaptec in which machine?
>
> Enterprise Sparc 250; I don't know the Adaptec adapter model but it
> reports back as:
>
> $ cat /proc/scsi/sym53c8xx/2
> Chip sym53c875, device id 0xf, revision id 0x14
> On PCI bus 0, device 4, function 0, IRQ 4,7d8
> Min. period factor 12, Wide SCSI BUS
> Max. started commands 1022, max. commands per LUN 64
Looks like you run Linux instead of Solaris and that your HA is from LSI
(aka Symbios Logic) not Adaptec.
> > If other devices work on the bus your disks should at least be detected.
> > IMHO most likely the adapters are bad.
>
> They are rather simple
> <http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3D140327919407> or
> very similar; and I'm at a loss to explain how 4 would be "dead"...
What does the SPARC machine report for the IBM disks, really _nothing_
in 'dmesg'?
Micha
Cydrome Leader
> Michael Baeuerle <michael....@gmx.net> writes:
>
>>> These drives use the simple SCA to 68 pin adapters to feed the drive and
>>> set the ID. [You can find them on eBay.]
>
>>Have you checked that the adapters work with a known good disk?
>
> Yes, they worked on other drives with an Intel-based Debian distro.
It sounds like you're mixing HVD and LVD drives/tape
changes/cable/controllers. If the drives work fine in a PC it's unlikely
they're HVD. Anything that connects to the back of a 1000 year old sparc
will be HVD, unless you recently bought a modern SCSI card for it.
David Lesher
>> > Have you checked that the adapters work with a known good disk?
>>
>> Yes, they worked on other drives with an Intel-based Debian distro.
>Are these "other drives" also LVD?
Hmm I believe the Barracuda's I had were SE/LVD, but they had SE
controllers and terms. I suppose it's possible the SCA-68 pin adapters
are SE only, but they claimed to be either when I bought them.
[If you have drives that are SE/LVD; do they change in any way frm
one mode to the other; and what provokes same?]
>> > Which Adaptec in which machine?
>>
>> Enterprise Sparc 250; I don't know the Adaptec adapter model but it
>> reports back as:
>>
>> $ cat /proc/scsi/sym53c8xx/2
>> Chip sym53c875, device id 0xf, revision id 0x14
>> On PCI bus 0, device 4, function 0, IRQ 4,7d8
>> Min. period factor 12, Wide SCSI BUS
>> Max. started commands 1022, max. commands per LUN 64
>Looks like you run Linux instead of Solaris and that your HA is from LSI
>(aka Symbios Logic) not Adaptec.
Yes, the box runs Debian; I believe at least two of the cards are marked
"Adaptec" but all 4 channels report sym53c875 chips.
>What does the SPARC machine report for the IBM disks, really _nothing_
>in 'dmesg'?
Yep. Nada.
Michael Baeuerle
> Michael Baeuerle wrote:
> > David Lesher wrote:
> > > >
> > Are these "other drives" also LVD?
>
> Hmm I believe the Barracuda's I had were SE/LVD, but they had SE
> controllers and terms. I suppose it's possible the SCA-68 pin adapters
> are SE only, but they claimed to be either when I bought them.
>
> [If you have drives that are SE/LVD; do they change in any way frm
> one mode to the other; and what provokes same?]
Yes, they switch to SE if SE-only equipment (device or terminator) is
present on the bus. This works by sensing the DIFFSENS line.
> > > > Which Adaptec in which machine?
> > >
> > > Enterprise Sparc 250; I don't know the Adaptec adapter model but it
> > > reports back as:
> > >
> > > $ cat /proc/scsi/sym53c8xx/2
> > > Chip sym53c875, device id 0xf, revision id 0x14
> > > On PCI bus 0, device 4, function 0, IRQ 4,7d8
> > > Min. period factor 12, Wide SCSI BUS
> > > Max. started commands 1022, max. commands per LUN 64
>
> > Looks like you run Linux instead of Solaris and that your HA is from LSI
> > (aka Symbios Logic) not Adaptec.
>
> Yes, the box runs Debian; I believe at least two of the cards are marked
> "Adaptec" but all 4 channels report sym53c875 chips.
The SYM53C875 has an SE interface but can control external transceivers.
If your SCA-adapters work for SE on the Intel machine then Cydrome
Leader should be right and the Busses (and Tapes) on the SPARC are HVD.
To be sure, look at the HA: Search for external transceivers (3 small
chips, probably SN75976) between the SYM53C875 and the bus connector.
Micha
David Lesher
>> [If you have drives that are SE/LVD; do they change in any way frm
>> one mode to the other; and what provokes same?]
>Yes, they switch to SE if SE-only equipment (device or terminator) is
>present on the bus. This works by sensing the DIFFSENS line.
Thanks..
>> Yes, the box runs Debian; I believe at least two of the cards are marked
>> "Adaptec" but all 4 channels report sym53c875 chips.
>The SYM53C875 has an SE interface but can control external transceivers.
>If your SCA-adapters work for SE on the Intel machine then Cydrome
>Leader should be right and the Busses (and Tapes) on the SPARC are HVD.
The LVD busses are via a card I added. It's labeled LVD on the
bracket and talks to two tape silos also labeled LVD. Well, it did;
one silo stopped working so I pulled it. I first tried the drives
there, then sharing the other channel with the silo.
The original internal and external busses seem to be SE, as is another
card I added.
Michael Baeuerle
> Michael Baeuerle wrote:
> >
> > If your SCA-adapters work for SE on the Intel machine then Cydrome
> > Leader should be right and the Busses (and Tapes) on the SPARC are HVD.
>
> The LVD busses are via a card I added. It's labeled LVD on the
> bracket and talks to two tape silos also labeled LVD.
And the card labeled "LVD" is really the one with the SYM53C875 onboard?
Hard to believe ... Fast20 as maximum transfer mode on a LVD card would
be very uncommon.
> Well, it did;
> one silo stopped working so I pulled it. I first tried the drives
> there, then sharing the other channel with the silo.
Hmm, the card has two channels? ... but the SYM53C875 only have one.
> The original internal and external busses seem to be SE, as is another
> card I added.
You should give us more information about your system: Model numbers or
pictures of the cards, a 'dmesg' dump with _all_ SCSI related
information.
Micha
David Lesher
>And the card labeled "LVD" is really the one with the SYM53C875 onboard?
>Hard to believe ... Fast20 as maximum transfer mode on a LVD card would
>be very uncommon.
>> there, then sharing the other channel with the silo.
>Hmm, the card has two channels? ... but the SYM53C875 only have one.
Yep, 2 channels... I assumed it reported as two separate controllers..
>You should give us more information about your system: Model numbers
>or pictures of the cards, a 'dmesg' dump with _all_ SCSI related
>information.
The disks are internal, chan 0. The Fastor+Quantum are on one LVD.
The DLT2000's etc. are the other SE card.
[LONG!!!!]
:~$ dmesg
PROMLIB: Sun IEEE Boot Prom 3.16.1 1999/04/19 07:55
Linux version 2.4.23md (root@minnie) (gcc version 3.3.2 (Debian)) #3 SMP Fri Dec 26 01:28:08 EST 2003
[...]
SCSI subsystem driver Revision: 1.00
sym.0.3.0: setting PCI_COMMAND_INVALIDATE.
sym.0.3.1: setting PCI_COMMAND_INVALIDATE.
sym.0.4.0: setting PCI_COMMAND_INVALIDATE.
sym.0.4.1: setting PCI_COMMAND_INVALIDATE.
sym0: <875> rev 0x14 on pci bus 0 device 3 function 0 irq 4,7e0
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
sym1: <875> rev 0x14 on pci bus 0 device 3 function 1 irq 4,7e6
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
sym2: <875> rev 0x14 on pci bus 0 device 4 function 0 irq 4,7d8
sym2: No NVRAM, ID 7, Fast-20, SE, parity checking
sym2: SCSI BUS has been reset.
sym3: <875> rev 0x14 on pci bus 0 device 4 function 1 irq 4,7d9
sym3: No NVRAM, ID 7, Fast-20, SE, parity checking
sym3: SCSI BUS has been reset.
scsi0 : sym-2.1.17a
scsi1 : sym-2.1.17a
scsi2 : sym-2.1.17a
scsi3 : sym-2.1.17a
Vendor: FUJITSU Model: MAG3182L SUN18G Rev: 1111
Type: Direct-Access ANSI SCSI revision: 02
Vendor: HP Model: C1537A Rev: L706
Type: Sequential-Access ANSI SCSI revision: 02
Vendor: TOSHIBA Model: XM6201TASUN32XCD Rev: 1103
Type: CD-ROM ANSI SCSI revision: 02
Vendor: SEAGATE Model: ST318203LSUN18G Rev: 034A
Type: Direct-Access ANSI SCSI revision: 02
Vendor: FUJITSU Model: MAA3182S SUN18G Rev: 1705
Type: Direct-Access ANSI SCSI revision: 02
Vendor: FUJITSU Model: MAA3182S SUN18G Rev: 1705
Type: Direct-Access ANSI SCSI revision: 02
Vendor: FUJITSU Model: MAA3182S SUN18G Rev: 1705
Type: Direct-Access ANSI SCSI revision: 02
Vendor: FUJITSU Model: MAA3182S SUN18G Rev: 1705
Type: Direct-Access ANSI SCSI revision: 02
sym0:0:0: tagged command queuing enabled, command queue depth 16.
sym0:8:0: tagged command queuing enabled, command queue depth 16.
sym0:9:0: tagged command queuing enabled, command queue depth 16.
sym0:10:0: tagged command queuing enabled, command queue depth 16.
sym0:11:0: tagged command queuing enabled, command queue depth 16.
sym0:12:0: tagged command queuing enabled, command queue depth 16.
Vendor: DEC Model: DLT2000 Rev: 8832
Type: Sequential-Access ANSI SCSI revision: 02
Vendor: ADIC Model: VLS DLT Rev: 0305
Type: Medium Changer ANSI SCSI revision: 02
Vendor: DEC Model: DLT2000 Rev: 8832
Type: Sequential-Access ANSI SCSI revision: 02
Vendor: ADIC Model: VLS DLT Rev: 0305
Type: Medium Changer ANSI SCSI revision: 02
Vendor: QUANTUM Model: DLT7000 Rev: 1624
Type: Sequential-Access ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 8, lun 0
Attached scsi disk sdc at scsi0, channel 0, id 9, lun 0
Attached scsi disk sdd at scsi0, channel 0, id 10, lun 0
Attached scsi disk sde at scsi0, channel 0, id 11, lun 0
Attached scsi disk sdf at scsi0, channel 0, id 12, lun 0
sym0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
SCSI device sda: 35378533 512-byte hdwr sectors (18114 MB)
Partition check:
sda: sda1 sda2 sda3 sda4 sda5 sda6
[...]
sym0:12: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
SCSI device sdf: 35378533 512-byte hdwr sectors (18114 MB)
[...]
scsi singledevice 0 0 2 0
scsi singledevice 0 0 3 0
scsi singledevice 0 0 5 0
scsi singledevice 0 0 7 0
scsi singledevice 1 0 1 0
scsi singledevice 1 0 5 0
scsi singledevice 1 0 6 0
scsi singledevice 1 0 7 0
scsi singledevice 2 0 0 0
scsi singledevice 2 0 1 0
scsi singledevice 2 0 2 0
scsi singledevice 2 0 3 0
scsi singledevice 2 0 4 0
Vendor: ADIC Model: FastStor DLT Rev: D116
Type: Medium Changer ANSI SCSI revision: 02
scsi singledevice 2 0 5 0
Vendor: QUANTUM Model: DLT7000 Rev: 2255
Type: Sequential-Access ANSI SCSI revision: 02
scsi singledevice 2 0 6 0
scsi singledevice 2 0 7 0
scsi singledevice 3 0 0 0
scsi singledevice 3 0 1 0
scsi singledevice 3 0 2 0
scsi singledevice 3 0 3 0
scsi singledevice 3 0 4 0
scsi singledevice 3 0 5 0
scsi singledevice 3 0 6 0
scsi singledevice 3 0 7 0
scsi singledevice 0 0 1 0
scsi singledevice 0 0 2 0
scsi singledevice 0 0 3 0
scsi singledevice 0 0 5 0
scsi singledevice 0 0 7 0
scsi singledevice 1 0 1 0
scsi singledevice 1 0 5 0
scsi singledevice 1 0 6 0
scsi singledevice 1 0 7 0
scsi singledevice 2 0 0 0
scsi singledevice 2 0 1 0
scsi singledevice 2 0 2 0
scsi singledevice 2 0 3 0
scsi singledevice 2 0 6 0
scsi singledevice 2 0 7 0
scsi singledevice 3 0 0 0
scsi singledevice 3 0 1 0
scsi singledevice 3 0 2 0
scsi singledevice 3 0 3 0
scsi singledevice 3 0 4 0
scsi singledevice 3 0 5 0
scsi singledevice 3 0 6 0
scsi singledevice 3 0 7 0
scsi singledevice 0 0 1 0
scsi singledevice 0 0 2 0
scsi singledevice 0 0 3 0
scsi singledevice 0 0 5 0
scsi singledevice 0 0 7 0
scsi singledevice 1 0 1 0
scsi singledevice 1 0 5 0
scsi singledevice 1 0 6 0
scsi singledevice 1 0 7 0
scsi singledevice 2 0 0 0
scsi singledevice 2 0 1 0
scsi singledevice 2 0 2 0
scsi singledevice 2 0 3 0
scsi singledevice 2 0 6 0
scsi singledevice 2 0 7 0
scsi singledevice 3 0 0 0
scsi singledevice 3 0 1 0
scsi singledevice 3 0 2 0
scsi singledevice 3 0 3 0
scsi singledevice 3 0 4 0
scsi singledevice 3 0 5 0
scsi singledevice 3 0 6 0
scsi singledevice 3 0 7 0
scsi singledevice 0 0 1 0
scsi singledevice 0 0 2 0
scsi singledevice 0 0 3 0
scsi singledevice 0 0 5 0
scsi singledevice 0 0 7 0
scsi singledevice 1 0 1 0
scsi singledevice 1 0 5 0
scsi singledevice 1 0 6 0
scsi singledevice 1 0 7 0
scsi singledevice 2 0 0 0
scsi singledevice 2 0 1 0
scsi singledevice 2 0 2 0
scsi singledevice 2 0 3 0
scsi singledevice 2 0 6 0
scsi singledevice 2 0 7 0
scsi singledevice 3 0 0 0
scsi singledevice 3 0 1 0
scsi singledevice 3 0 2 0
scsi singledevice 3 0 3 0
scsi singledevice 3 0 4 0
scsi singledevice 3 0 5 0
scsi singledevice 3 0 6 0
scsi singledevice 3 0 7 0
st: Version 20030406, bufsize 1048576, max init. bufs 4, s/g segs 128
Attached scsi tape st0 at scsi0, channel 0, id 4, lun 0
Attached scsi tape st1 at scsi1, channel 0, id 0, lun 0
Attached scsi tape st2 at scsi1, channel 0, id 3, lun 0
Attached scsi tape st3 at scsi1, channel 0, id 8, lun 0
Attached scsi tape st4 at scsi2, channel 0, id 5, lun 0
sym1:3: FAST-10 SCSI 5.0 MB/s ST (200.0 ns, offset 15)
sym0:4: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 16)
sym1:0: FAST-10 SCSI 5.0 MB/s ST (200.0 ns, offset 15)
sym1:8: FAST-10 WIDE SCSI 20.0 MB/s ST (100.0 ns, offset 15)
sym2:5: FAST-10 WIDE SCSI 20.0 MB/s ST (100.0 ns, offset 15)
Attached scsi generic sg9 at scsi1, channel 0, id 2, lun 0, type 8
Attached scsi generic sg11 at scsi1, channel 0, id 4, lun 0, type 8
Attached scsi generic sg13 at scsi2, channel 0, id 4, lun 0, type 8
sym0:6: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 16)
st4: Block limits 2 - 16777214 bytes.
st2: Block limits 1 - 16777215 bytes.
[...]
st1: Block limits 1 - 16777215 bytes.
st1: Error with sense data: Info fld=0x10000, Current st09:01: sns = f0 3
ASC=80 ASCQ= 1
Raw sense data:0xf0 0x00 0x03 0x00 0x01 0x00 0x00 0x15 0x00 0x00 0x00 0x00 0x80 0x01 0x00 0x00 0x00 0x00 0x81 0x1c 0xfc 0x00 0x00 0xdb 0x0c 0x00 0x00 0x00 0x00
st1: Error with sense data: Info fld=0x1, Current st09:01: sns = f0 3
ASC=80 ASCQ= 1
Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x15 0x00 0x00 0x00 0x00 0x80 0x01 0x00 0x00 0x00 0x00 0x81 0x1c 0xfc 0x00 0x00 0xdb 0x0c 0x00 0x00 0x00 0x00
st1: Error on write filemark.
:~$ cat /proc/scsi/sym53c8xx/0
Chip sym53c875, device id 0xf, revision id 0x14
On PCI bus 0, device 3, function 0, IRQ 4,7e0
Min. period factor 12, Wide SCSI BUS
Max. started commands 1022, max. commands per LUN 64
:~$ cat /proc/scsi/sym53c8xx/1
Chip sym53c875, device id 0xf, revision id 0x14
On PCI bus 0, device 3, function 1, IRQ 4,7e6
Min. period factor 12, Wide SCSI BUS
Max. started commands 1022, max. commands per LUN 64
:~$ cat /proc/scsi/sym53c8xx/2
Chip sym53c875, device id 0xf, revision id 0x14
On PCI bus 0, device 4, function 0, IRQ 4,7d8
Min. period factor 12, Wide SCSI BUS
Max. started commands 1022, max. commands per LUN 64
:~$ cat /proc/scsi/sym53c8xx/3
Chip sym53c875, device id 0xf, revision id 0x14
On PCI bus 0, device 4, function 1, IRQ 4,7d9
Min. period factor 12, Wide SCSI BUS
Max. started commands 1022, max. commands per LUN 64
Scott Lurndal
> Vendor: DEC Model: DLT2000 Rev: 8832
> Type: Sequential-Access ANSI SCSI revision: 02
> Vendor: ADIC Model: VLS DLT Rev: 0305
> Type: Medium Changer ANSI SCSI revision: 02
> Vendor: DEC Model: DLT2000 Rev: 8832
> Type: Sequential-Access ANSI SCSI revision: 02
> Vendor: ADIC Model: VLS DLT Rev: 0305
> Type: Medium Changer ANSI SCSI revision: 02
> Vendor: QUANTUM Model: DLT7000 Rev: 1624
>st1: Block limits 1 - 16777215 bytes.
>st1: Error with sense data: Info fld=0x10000, Current st09:01: sns = f0 3
>ASC=80 ASCQ= 1
>Raw sense data:0xf0 0x00 0x03 0x00 0x01 0x00 0x00 0x15 0x00 0x00 0x00 0x00 0x80 0x01 0x00 0x00 0x00 0x00 0x81 0x1c 0xfc 0x00 0x00 0xdb 0x0c 0x00 0x00 0x00 0x00
>st1: Error with sense data: Info fld=0x1, Current st09:01: sns = f0 3
>ASC=80 ASCQ= 1
>Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x15 0x00 0x00 0x00 0x00 0x80 0x01 0x00 0x00 0x00 0x00 0x81 0x1c 0xfc 0x00 0x00 0xdb 0x0c 0x00 0x00 0x00 0x00
>st1: Error on write filemark.
ASC=80 is a vendor specific sense code from the DLT drive. You'll need to
find a spec for the DEC DLT2000 to find out what it means.
scott
Michael Baeuerle
> Michael Baeuerle wrote:
> > >
> > And the card labeled "LVD" is really the one with the SYM53C875 onboard?
> > Hard to believe ... Fast20 as maximum transfer mode on a LVD card would
> > be very uncommon.
> >
> > > there, then sharing the other channel with the silo.
> >
> > Hmm, the card has two channels? ... but the SYM53C875 only have one.
>
> Yep, 2 channels... I assumed it reported as two separate controllers..
>
> > You should give us more information about your system: Model numbers
> > or pictures of the cards, a 'dmesg' dump with _all_ SCSI related
> > information.
>
> The disks are internal, chan 0. The Fastor+Quantum are on one LVD.
>
> The DLT2000's etc. are the other SE card.
>
> [LONG!!!!]
> :~$ dmesg
>
> PROMLIB: Sun IEEE Boot Prom 3.16.1 1999/04/19 07:55
> Linux version 2.4.23md (root@minnie) (gcc version 3.3.2 (Debian)) #3 SMP Fri Dec 26 01:28:08 EST 2003
> [...]
> sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym0: SCSI BUS has been reset.
> sym1: <875> rev 0x14 on pci bus 0 device 3 function 1 irq 4,7e6
> sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym1: SCSI BUS has been reset.
> sym2: <875> rev 0x14 on pci bus 0 device 4 function 0 irq 4,7d8
> sym2: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym2: SCSI BUS has been reset.
> sym3: <875> rev 0x14 on pci bus 0 device 4 function 1 irq 4,7d9
> sym3: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym3: SCSI BUS has been reset.
OK, two SYM53C875 chips (PCI functions 0 and 1) on two cards (PCI
devices 3 and 4) respectively. All four busses are reported as SE, but
in the driver there is this statement:
|
| * - For previous generation chips
(825/825A/875),
| * user has to tell us how to check against
HVD,
| * since a 100% safe algorithm is not possible.
|
what means that the driver cannot autodetect external transceivers for
the SYM53C875 in all cases.
Looking at the tapes: There is one DDS3 and four DLT drives. The C1537A
is SE and the DLT2000 and DLT7000 are SE or HVD. The manuals say: None
of them was available with LVD interface.
Looks like your "LVD" labels are faked ... now you really should look at
the cards (for external transceivers between SYM53C875 and bus
connector) to be sure!
Micha
David Lesher
>what means that the driver cannot autodetect external transceivers for
>the SYM53C875 in all cases.
So it sounds as if all that knows is it may, or may not, be LVD.
>Looking at the tapes: There is one DDS3 and four DLT drives. The C1537A
>is SE and the DLT2000 and DLT7000 are SE or HVD. The manuals say: None
>of them was available with LVD interface.
The DDS3 is not used. It's internal.
The DLT2000's are part of VLS DLT's jukeboxes. One of the DLT7000's is
standalone. All SE.
The other changer is a Dell PowerVault 120T DLT7000 which is a rebadged
ADIC FastStor/ Quantum.
>Looks like your "LVD" labels are faked ... now you really should look
>at the cards (for external transceivers between SYM53C875 and bus
>connector) to be sure!
The Dell specs:
<http://support.dell.com/support/edocs/storage/adic7000/ug/specs.htm>
says:
SCSI-2 Fast/Wide, differential, 68-pin
Cydrome Leader
> Michael Baeuerle <michael....@stz-e.de> writes:
>
>>what means that the driver cannot autodetect external transceivers for
>>the SYM53C875 in all cases.
>
> So it sounds as if all that knows is it may, or may not, be LVD.
>
>
>>Looking at the tapes: There is one DDS3 and four DLT drives. The C1537A
>>is SE and the DLT2000 and DLT7000 are SE or HVD. The manuals say: None
>>of them was available with LVD interface.
>
> The DDS3 is not used. It's internal.
>
> The DLT2000's are part of VLS DLT's jukeboxes. One of the DLT7000's is
> standalone. All SE.
>
> The other changer is a Dell PowerVault 120T DLT7000 which is a rebadged
> ADIC FastStor/ Quantum.
>
>
>>Looks like your "LVD" labels are faked ... now you really should look
>>at the cards (for external transceivers between SYM53C875 and bus
>>connector) to be sure!
>
> The Dell specs:
>
> <http://support.dell.com/support/edocs/storage/adic7000/ug/specs.htm>
>
> says:
>
> SCSI-2 Fast/Wide, differential, 68-pin
That thing is 100% HVD.
I've used those autoloaders before. They came with their own SCSI card when purchased from
Dell.
Here are better docs from dell, they mention the adaptec 2944 card:
http://support.dell.com/support/edocs/storage/adic7000/ug/notes.htm
David Lesher
>> SCSI-2 Fast/Wide, differential, 68-pin
>That thing is 100% HVD.
>I've used those autoloaders before. They came with their own SCSI card when purchased from
>Dell.
>Here are better docs from dell, they mention the adaptec 2944 card:
>http://support.dell.com/support/edocs/storage/adic7000/ug/notes.htm
Ugh. So either I cooked the LVD drives or not; but that card won't
work. And I passed up a bunch of PCI SCSI cards at the last hamfest, and
now, I don't recall if any others I have are SE/LVD.
Cydrome Leader
> Cydrome Leader <pres...@MUNGEpanix.com> writes:
>
>>> SCSI-2 Fast/Wide, differential, 68-pin
>
>>That thing is 100% HVD.
>
>>I've used those autoloaders before. They came with their own SCSI card when purchased from
>>Dell.
>
>>Here are better docs from dell, they mention the adaptec 2944 card:
>
>>http://support.dell.com/support/edocs/storage/adic7000/ug/notes.htm
>
>
> Ugh. So either I cooked the LVD drives or not; but that card won't
the drives are probably OK- I'm not aware of any SCSI bus mixups that
actually broke a drive.
Jeff Jonas
>> reports back as:
>> $ cat /proc/scsi/sym53c8xx/2
>> Chip sym53c875, device id 0xf, revision id 0x14
>> On PCI bus 0, device 4, function 0, IRQ 4,7d8
>> Min. period factor 12, Wide SCSI BUS
>> Max. started commands 1022, max. commands per LUN 64
>Looks like you run Linux instead of Solaris and that your HA is from LSI
>(aka Symbios Logic) not Adaptec.
The 53cxx chips were originally by NCR, then Symbios, then LSI,
so all names may historically apply for the drivers, device names,
man pages & documentation.
And "device id 0xf": is that the PCI ID or SCSI ID?
(both PCI and SCSI parameters are reported there).
The SCSI BUS id for the HA is usually 7,
even for wide, for compatibility with narrow devices.
David Lesher
I'm still trying to scrape up a LVD card to talk to those Compaq
drives....
So now I'm wondering... Are any SCSI devices really LVD only?
I found a paper on the SCSI Trade Assoc site
<28b7h6-...@micha.freeshell.org> and it seemed to imply that LVD was
a superset of SE; if any device on a LVD chain pulled a h DIFFSENS low,
all devices on the chain would follow along to the land of SE.
If so, I can tolerate the lower speed of SE & stop looking for a LVD card.
David Lesher
>I found a paper on the SCSI Trade Assoc site
><28b7h6-...@micha.freeshell.org> and it seemed to imply that LVD was
try:
<http://www.scsita.org/aboutscsi/SCSI_Termination_Tutorial.html>