IBM DS4800 Storage

[Dan Nelson]

In the last episode (Mar 01), Omer Faruk Sen said:
> Is there anyone here that have used SAN against IBM DS4800 (Fiber). I
> can see disk but i can't fdisk it.
> 
> fdisk /dev/da0
> fdisk: could not detect sector size
> 
> and dmesg output when system boots:
> 
> registered firmware set <isp_1040>
> registered firmware set <isp_1040_it>
> registered firmware set <isp_1080>
> registered firmware set <isp_1080_it>
> registered firmware set <isp_12160>
> registered firmware set <isp_12160_it>
> registered firmware set <isp_2100>
> registered firmware set <isp_2200>
> registered firmware set <isp_2300>
> registered firmware set <isp_2322>
> registered firmware set <isp_2400>
> isp0: <Qlogic ISP 2432 PCI FC-AL Adapter> port 0x6000-0x60ff mem 0xc7efc000-0xc7efffff irq 17 at device 0.0 on pci36
> isp0: [ITHREAD]
> isp0: Board Type 2422, Chip Revision 0x3, loaded F/W Revision 4.0.20
> isp1: <Qlogic ISP 2432 PCI FC-AL Adapter> port 0x7000-0x70ff mem 0xc5ffc000-0xc5ffffff irq 18 at device 0.0 on pci7
> isp1: [ITHREAD]
> isp1: Board Type 2422, Chip Revision 0x3, loaded F/W Revision 4.0.20
> vgapci0: <VGA-compatible display> port 0x4000-0x40ff mem 0xd0000000-0xd7ffffff,0xdfff0000-0xdfffffff irq 22 at device 6.0 on pci1
> isp1: 0.0.2 FCP RESPONSE: 0x2
> isp1: 0.0.2 FCP RESPONSE: 0x2
> 
> and afterwards:
> 
> (da0:isp1:0:0:6): Vendor Specific ASC
> (da0:isp1:0:0:6): Unretryable error
> (da0:isp1:0:0:6): READ(10). CDB: 28 0 0 0 0 10 0 0 1 0
> (da0:isp1:0:0:6): CAM Status: SCSI Status Error
> (da0:isp1:0:0:6): SCSI Status: Check Condition
> (da0:isp1:0:0:6): ILLEGAL REQUEST asc:94,1
> (da0:isp1:0:0:6): Vendor Specific ASC
> (da0:isp1:0:0:6): Unretryable error

According to the "DS4000 Problem Determination Guide" at
ftp://ftp.software.ibm.com/systems/support/system_x_pdf/gc27207600.pdf#page=104
, ASC/ASCQ 94/01 corresponds to "Invalid Request Due to Current Logical Unit
Ownership".  Maybe the DS4800 thinks that the lun has been assigned to a
different host, and that's why it won't let the FreeBSD machine access it. 

Other web searches indicate that this may be an attempt to access the
passive path of multipathed device on an active/passive RAID array.  If
that's the case, FreeBSD should have found another disk (da1 possibly?) that
you should be able to use.


-- 
	Dan Nelson
	dnelson at allantgroup.com