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

Re: difficulty connecting to SAN storage with qlogic 2200
thanx for putting me on the right track. when i compiled my kernel initially, i selected anything that said "qlogic", and then compiled in the qla2x00 module. at boot time, it loaded something i didn't need, which conflicted with the qla2x00 module. i have since been able to successfully see the disk across the san, but only on lun 0. 

i think i have the right stuff in the kernel to probe all luns:
jarocki@ptah:/usr/src/kernel-source-2.4.27$ grep -i scsi .config | grep -v "#" 
CONFIG_SCSI=y
CONFIG_SCSI_DEBUG_QUEUES=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=4
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20


anyone know the magical incantation to find lun numbers higher than 0?




On Mon, 2006-01-09 at 11:16 -0600, Jim Jarocki wrote:

hiya matt.  thanx for taking a look at this.  comments/answers are
below.  also, check out my 2nd email to the debian users list, its a bit
more informative.


jim, you should reply to the list, that way the results are archived on
the internet for others to search.




On Wed, 2006-01-04 at 11:11 -0600, Jim Jarocki wrote:

hello all,

i'm having some difficulties getting a debian system to connect to our san
storage.  some quick system info:


so the san disk is the boot device? or an secondary disk?


secondary.


jarocki@ptah:~$ uname -a
Linux ptah 2.4.27 #1 SMP Tue Jan 3 12:54:05 CST 2006 i686 GNU/Linux
jarocki@ptah:~$ lsmod
Module                  Size  Used by    Not tainted
qla2200_conf          300796   0 (autoclean)


what is the full listing of lsmod, qla2200_conf is not the fiber card
driver (per se), it gives you the ability to do some configuring of the
driver.


i think that was the full listing.  the machine in question is
inaccessable at the moment.


so it would appear that i have the module to support the card successfully
compiled and loaded.  however, when i boot up, the system hangs while it
tries to connect.  even the console hangs.  from 'dmesg':

qlogicfc0 : Loop Reinitialized
qlogicfc0 : Link is Up
scsi0 : QLogic ISP2200 SCSI on PCI bus 05 device 48 irq 18 base 0x1000
qlogicfc0 : Fabric found.
qlogicfc0 : Error performing port login 4005
qlogicfc0 : Error performing port login 4005
<repeats the above line>

<no console access (no response) and ssh hangs>
<until i unplug the fibre>

qlogicfc0 : Error performing port login 4005
qlogicfc0 : Link is Down
qlogicfc0 : Error performing port login 4005
qlogicfc0 : Get All Next failed 4005.
qlogicfc0 : Port Database
wwn: 210000e08b012ce3  scsi_id: 0  loop_id: 0
es1371: version v0.32 time 12:55:36 Jan  3 2006
Linux Kernel Card Services 3.1.22
   options:  [pci] [cardbus] [pm]
usb.c: registered new driver hub
host/uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Setting latency timer of device 00:1d.0 to 64

so, what am i missing?  probably something fairly obvious and basic, but
that wouldn't be the first time... :P


so this looks like you are using the qlogicfc module. i dont think the
qla2200* modules are compatible with the qlogicfc module. how did you
get the qla2000 modules?


used aptitude and pointed at the non-free section to grab the qla source,
then recompiled the kernel and built the module.  said the compile
completed successfully.


we are using san disks as boot devices in our environment and what i did
was make modules from the qla2x00-source and then create an initrd image
to load those modules:


thinking i can skip the 'initrd' part since i'm booting of a local drive,
the san connection is just some empty disk.


$ lsmod | grep qla
qla2200               281188   2  (autoclean)
qla2200_conf          300828   0  (autoclean)

$ cat /etc/mkinitrd/modules
scsi_mod
sd_mod
qla2200_conf
qla2200
reiserfs

-matt zagrabelny


if you reference my 2nd post, you'll see additional info.  this part:

and this is what i'm seeing in my /var/log/messages file:

Jan  5 15:14:04 ptah kernel: qla2x00_set_info starts at address = f014f060
Jan  5 15:14:04 ptah kernel: qla2x00: Found  VID=1077 DID=2200 SSVID=1077
SSDID=
2
Jan  5 15:14:04 ptah kernel: PCI: Unable to reserve I/O region #1:100@1000
for d
evice 05:09.0
Jan  5 15:14:04 ptah kernel: PCI: Unable to reserve I/O region #1:100@1000
for d
evice 05:09.0
Jan  5 15:14:04 ptah kernel: scsi(1): Failed to reserve PIO/MMIO regions
(05:09.
0)
Jan  5 15:14:04 ptah kernel: qla2x00: couldn't configure PCI I/O space!

is reproduceable by `modprobe qla2200` (if memory serves).  so its
essentially not loading, but i'm not exactly sure why.  on our solaris
boxes we need a qla2200.conf, unsure if i'll need something similar on
debian, and if so, where to put it.


no, i havent had to do anything with the qla2200.conf.

i would blacklist the qlogicfc driver and add 'qla2200_conf' and
'qla2200' to your /etc/modules. from the sounds of your output it seems
like the problem may be with your san, ive havent had to do any san
configuration / partitioning, so i cant comment on that, i just know
that they can be fickle.

-matt zagrabelny



--------------------------------------------------------------------------
"Ballerinas are always on their toes.  Why don't they just get
 taller women?"
 -- Steven Wright
--------------------------------------------------------------------------
Jim Jarocki
Systems Administrator
jarocki@startribune.com
--------------------------------------------------------------------------
Reply to: