multiple luns assigning on FastT600
 

Hi,
I'm having problems picking up additional storage that is
assign from the Fastt600 to any blades in my blade center. I'm
booting off the SAN but thats the only partiton I can see. During
installation disk druid see's only a LUN ( the bootup LUN ) after
installation it does not see other LUN assigned. I'm using
RedHat Linux Advance Server 3.0 update 2. The HBA on the
Blade is a qlogic card ..QLA2300..I've tried running kudzu to pick
the addition partitions. I've assign the LUN in this order bootup
lun -0 addition partition lun-1..the bootup partiton
is /dev/sda ..so i tried a long shot to fdisk /dev/sdb through
till /dev/sdz..all to no avail ... when dmesg is run .. i can see the
boot up Lun ... any help or advice ..would be highly appreciated

joshua

This might do it:

http://www.clockwatching.net/~fin/ra...an-scsi-bus.sh

But I doubt it...

Really, it sounds like you need the kernel option:

CONFIG_SCSI_MULTI_LUN:

That will probe all LUNs on each scsi device, its probably not on a default RH install kernel knowing their typical timidity.

Aside from that, what does "dmesg" say with regard to the qlogic load?

Cheers,

Finegan

Finegan ...
thanks for the script but it did not find new luns. Dmesg finds the qlogic card ..finds lun 0 ( the boot lun ) ..Loads lun 0 but does not find other lun/scsi partitions. I don't know where i'm going wrong ... i 've loaded the system with Windows and windows picks up all the partitions.
I've been to the qlogic and ibm site regarding how to install on linux .. still can't find something i'm doing wrong ...thanks again for the help

Its an install kernel vs stock kernel issue. The problem is that the install kernel is slimmed down so that the option to probe all LUNs on boot isn't compiled in. I'm 90% certain the kernel you install will see everything properly, but this is a hangup for installation. Its not something I think you can work around unless you want to make a special boot kernel (which I recommend entirely, but don't know the parameters of how your work would look upon that), or you can tell RHEL support they're daft monkeys and that they need to shoot you a new boot kernel.

Cheers,

Finegan

I had to setup a linux server using a san this week and ran into the same problem you had. The script worked for me. I did have to modify it. LUN 9 was assigned to the linux server. The script will only scan the first 7. I made a change in the script to scan 0 thru 9 and it worked. It created the dev as sdc. I fdisked and made the file system and its working great. You do have to run the script every time you boot the system. I just kicked off the script and mount the file system from rc.local. You do need to run the script like this rescan-scsi-bus.sh -l -w --color --nooptscan. I hope this helps....