[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Using an HSZ50

You definitely need to use the Qlogic differential card.  The other ones
won't work.

HVD (high-voltage differential) is electrically different from
single-ended or low-voltage differential.  It is designed to allow for
longer scsi cable lengths, something that bug servers in big data
centers need.

It has largely been replaced by fiber channel these days.  I don't know
of any other HVD card that I supported by Linux.

The SCSI-Ethernet combo is most likely a single-ended low voltage
device.  It won't work on your HSZ50.  HVD scsi signals can damage
non-HVD disks, so be careful.

In order to use your HSZ50 you need to configure it using a serial
terminal connected directly to the controller (needs a RJ11
(phone-plug)-terminated serial cable.  Configuration is kinda
complicated - you can find some pointers if you do a google search on
'HSZ50 HSOF'.  Once you get the storagesets configured, you should see
them at boot.

I think you probably have some storagesets already configured (that's
what the boot messages indicate), but there might be some errors in the
configuration.

Also, you have to make sure both ends of the scsi bus are properly
terminated.

Good Luck

-----Original Message-----
From: Bill MacAllister
[mailto:post+alpha-linux@macallister.grass-valley.ca.us] 
Sent: Monday, November 03, 2003 12:53 AM
To: Michael Mackey
Cc: debian-alpha@lists.debian.org
Subject: Re: Using an HSZ50


Michael,

Thanks for the pointer.

The reason that there are errors reading the partition table is because 
there is none at this point.  fdisk does cannot read the device.  How
did 
you create a partition table on your hsz70?

I have a couple of other questions is you don't mind.  The HSZ50 is 
differential scsi.  I got a qlogic controller that supports differential

scsi mostly because I was not sure if I could use my Adaptec 3940uw with

it.  (I don't need to boot off of the HSZ so it does not need to be
visible 
from SRM.)  Is differential scsi electrically different enough that you 
can't mix differential and non-differential?

Finally, there is a scsi/tulip como card in the system that I have
ignored 
up to this point except to use the ethernet interface.  Can you tell me 
anything about this card?  Should I try plugging the HSZ50 into it?

Again, thanks for you help,

Bill

--On Sunday, November 02, 2003 06:19:01 PM -0600 Michael Mackey 
<michael-mackey@uiowa.edu> wrote:

> I have used an HSZ70 with RedHat 7.2.
>
> On boot, I got the same kernel log messages, up to the error reading 
> sdg's partition table.
>
> I also saw a lot of unhandled interrupts, especially while any mmapped

> file io was going on (typically whilst running dump or fsck).
>
> You can find a more complete description at  http://alpha.crl.dec.com 
> in the Bugzilla database (bug #40).
>
> I think it is a problem in the interrupt handling code for the qlogic 
> driver - the HSZ controllers use some undocumented interrupts.
>
> Bill MacAllister wrote:
>
>> Hello,
>>
>> I am working on using an HSZ50 on my a Redhat 7.2 system.  Linux see 
>> that there is a SCSI drive there, and even reads manufacturer and 
>> model information.  But, it does not recognize the drive type.  Here 
>> is a snap shot from dmesg
>>
>>
>> isp0: Ultra Mode Capable
>> isp0: Board Type 1040B, Chip Revision 0x5, loaded F/W Revision 4.66.0
>> isp0: Last F/W revision was 5.57.1
>> isp1: Differential Mode
>> isp1: Ultra Mode Capable
>> isp1: Board Type 1040B, Chip Revision 0x5, loaded F/W Revision 4.66.0
>> isp1: Last F/W revision was 5.57.1
>> scsi0 : Driver for a Qlogic ISP 1020/1040 Host Adapter
>> scsi1 : Driver for a Qlogic ISP 1020/1040 Host Adapter
>>  Vendor: SEAGATE   Model: ST34371W          Rev: 0860
>>  Type:   Direct-Access                      ANSI SCSI revision: 02
>>  Vendor: SEAGATE   Model: ST336938LW        Rev: 0003
>>  Type:   Direct-Access                      ANSI SCSI revision: 03
>>  Vendor: SEAGATE   Model: ST373405LW        Rev: 0003
>>  Type:   Direct-Access                      ANSI SCSI revision: 03
>>  Vendor: DEC       Model: RZ2DC-PA (C) DEC  Rev: 5520
>>  Type:   Direct-Access                      ANSI SCSI revision: 02
>>  Vendor: DEC       Model: RZ2DC-PA (C) DEC  Rev: 5520
>>  Type:   Direct-Access                      ANSI SCSI revision: 02
>>  Vendor: DEC       Model: RZ2DC-PA (C) DEC  Rev: 5520
>>  Type:   Direct-Access                      ANSI SCSI revision: 02
>>  Vendor: DEC       Model: HSZ50-AX          Rev: V50Z
>>  Type:   Direct-Access                      ANSI SCSI revision: 02
>> scsi: unknown type 31
>>  Vendor: DEC       Model: HSZ50-AX          Rev: V50Z
>>  Type:   Unknown                            ANSI SCSI revision: 02
>> scsi: unknown type 31
>>  Vendor: DEC       Model: HSZ50-AX          Rev: V50Z
>>  Type:   Unknown                            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 1, lun 0 Attached scsi disk sdc at 
>> scsi0, channel 0, id 2, lun 0 Attached scsi disk sdd at scsi0, 
>> channel 0, id 3, lun 0 Attached scsi disk sde at scsi0, channel 0, id

>> 4, lun 0 Attached scsi disk sdf at scsi0, channel 0, id 5, lun 0
>> Attached scsi disk sdg at scsi1, channel 0, id 0, lun 0
>> resize_dma_pool: unknown device type 31
>> resize_dma_pool: unknown device type 31
>> SCSI device sda: 8388315 512-byte hdwr sectors (4295 MB)
>> Partition check:
>> sda: sda1 sda2
>> SCSI device sdb: 72176567 512-byte hdwr sectors (36954 MB)
>> sdb: sdb1 sdb2 sdb3
>> SCSI device sdc: 143374741 512-byte hdwr sectors (73408 MB)
>> sdc: sdc1 sdc3
>> SCSI device sdd: 17773524 512-byte hdwr sectors (9100 MB)
>> sdd: sdd1
>> SCSI device sde: 17773524 512-byte hdwr sectors (9100 MB)
>> sde: sde1 sde3
>> SCSI device sdf: 17773524 512-byte hdwr sectors (9100 MB)
>> sdf: sdf1 sdf3
>> sdg: Spinning up
>> disk...........................................................
>> ............................................not responding...
>> sdg : READ CAPACITY failed.
>> sdg : status = 1, message = 00, host = 0, driver = 08
>> Current sd00:00: sense key Not Ready
>> Additional sense indicates Logical unit not ready,initializing cmd.
>> required
>> sdg : block size assumed to be 512 bytes, disk size 1GB.
>> sdg:<6>Device 08:60 not ready.
>> I/O error: dev 08:60, sector 0
>> unable to read partition table
>>
>> I have seen other says that HSZ50's can be used.  It there some trick

>> that I am missing?  Any suggestions gratefully accepted.
>>
>> Thanks,
>>
>> Bill

+---------------------------------------------------
| Bill MacAllister
| 14219 Auburn Road
| Grass Valley, CA 95949
| 530-272-8555


-- 
To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: