qlogic 2340 and dell cx200

[Matthew Jacob]

> Hi, 
> I have been trying to use a SAN system using Dell CX200 fiber SAN Storage 
> with Qlogic 2340 (PCI-X 133) HBA. But I had lots of error messages and 
> unstable OS behaviour. I have tried different scenarios on that system. This 
> qlogic 2340 card has a qlogic 2312 chipset which is recognized by my kernel: 
> isp0: <Qlogic ISP 2312 PCI FC-AL Adapter> port 0xcc00-0xccff mem 
> 0xfcd00000-0xfcd00fff irq 24 at device 6.0 on pci3 
> But in my test setup I receive following errors: 
>
> (da0:isp0:0:0:0): READ(06). CDB: 8 f 3f 9f 80 0
> (da0:isp0:0:0:0): CAM Status: SCSI Status Error
> (da0:isp0:0:0:0): SCSI Status: Check Condition
> (da0:isp0:0:0:0): UNIT ATTENTION asc:2a,81
> (da0:isp0:0:0:0): Vendor Specific ASCQ
> (da0:isp0:0:0:0): Retrying Command (per Sense Data)


Well, your storage is saying "Retry", so we do.

>
> Sometime I receive following errors: 
> isp0: bad execution throttle of 0- using 16

The DELL CX200 card clearly has a different NVRAM layout.

> (da1:isp0:0:0:2): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
> (da1:isp0:0:0:2): NOT READY asc:4,3
> (da1:isp0:0:0:2): Logical unit not ready, manual intervention required


The unit said it wasn't rready.

> I have enabled ispfw and my system sometime recognizes my LUN's that is 
> smaller than 8 GB (I am not sure about size. I have tried 5GB LUNs). I can 
> format and use it in one of my tries. But after adding a second 5GB LUN my 
> system finds it as da1 but can't format it. I have also added a 30 GB LUN. 
> This LUN can't be formatted to.

You must use ispfw until I rewrite the driver to recognize the 2Klogin 
options- some of the newer cards and f/w have an option for doing 2048 
port logins (instead of 0..255)- the data structures change 
substantially because of this, so in the interim (and its generally a 
good idea anyway), make sure ispfw is either loaded at boot time or 
compiled into your kernel.


>
> (da1:isp0:0:0:2): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
> (da1:isp0:0:0:2): NOT READY asc:4,3
> (da0:isp0:0:0:0): removing device entry
> da1 at isp0 bus 0 target 0 lun 2
> da1: <DGC RAID 5 0207> Fixed Direct Access SCSI-4 device
> da1: 200.000MB/s transfers, Tagged Queueing Enabled
> da1: 30720MB (62914560 512 byte sectors: 255H 63S/T 3916C)
> (da1:isp0:0:0:2): READ(06). CDB: 8 0 0 0 1 0
> (da1:isp0:0:0:2): CAM Status: SCSI Status Error
> (da1:isp0:0:0:2): SCSI Status: Check Condition
> (da1:isp0:0:0:2): NOT READY asc:4,3
> (da1:isp0:0:0:2): Logical unit not ready, manual intervention required
> (da1:isp0:0:0:2): Unretryable error
> (da1:isp0:0:0:2): Invalidating pack
> (da1:isp0:0:0:2): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
> (da1:isp0:0:0:2): NOT READY asc:4,3

All of the "not ready" messages are the RAID box saying "I'm not ready".

>
> Has anyone a clue on what is going on? I am very new to that SAN concepts. 
> But I am thinking that the HBA card is the problem but don't have a chance to 
> try another HBA. 
>
>
> I have also used ISP_TARGET_MODE=1 in my kernel (both 5.3R and 5-STABLE). But 
> that totally disabled isp card.

Don't turn on ISP_TARGET_MODE- that's to make the FreeBSD box a target, 
not an initiator.

Conclusion:

It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.
It's the RAID Box.


-matt