Re: Need to install on LUN past 8

[Rick Stevens <rstevens vitalstream com>]

On Tue, 2007-03-13 at 12:56 -0600, isplist logicore net wrote:
> I've tried everything I can find and think of or that has been suggested.
> 
> I have a Xyratex/MTI type chassis split into 32 volumes. I need to install 32
> blades onto each volume so that I can remove the drives on each blade.
> 
> When I start a Linux install on a blade, it never sees all of the volumes, 
> only LUNS 0/1. I need to see all 32 LUNS so that I can install all of my 
> servers.
> 
> I've tried all of the following;
> 
> RHEL4, CentOS4.4, others. I don't really care what the distro is, so long as 
> it runs basic services such as web/php, qmail, etc. What I do need however is
> that they be GFS/Cluster machines.
> 
> I've tried passing the information at the installers command line;
> 
> scsi_mod.max_luns=256
> scsi_mod.scsi_dev_flags=INLINE:TF200:0x242
> 
> I've tried many variations of these types of commands with no result.
> 
> I've then set up a PXE boot server thinking that I might be able to pass the 
> options using pxelinux.cfg. Still no luck, it only sees two LUNS.
> 
> I've tried installing from network with a recompilled initrd.img from a 
> machine which was already installed and modprobe.conf modified to see the 
> LUNS. The donor server can see all of the volumes, the installing version dies 
> with a kernel problem since it cannot see the same already installed volume.
> 
> What in the world can I do? Is there a guru here who can tell me how I can do
> this?
> 
> Thank you VERY much for reading this :).

Don't specify the module on the command line.  Just use

	max_luns=256

You shouldn't need the "scsi_dev_flags" unless the device is broken in
some way.  Your flags say:

	0x200: there are LUNs numbered > 7
	0x040: the LUNs may not be consecutively numbered
	0x002: force a LUN scan

The "max_luns=256" will force a LUN scan, so the "0x002" bit is, uhm,
useless.  The other flags aren't needed unless the LUN scan causes the
device to lock up--which isn't very common with modern equipment.

If you're not booting off a SCSI disk, you can test it fairly easily.
Just do this:

	modprobe -r scsi_mod
	modprobe scsi_mod max_luns=256
	modprobe name-of-your-SCSI-driver

Then "cat /proc/scsi/scsi" to verify that the LUNs are seen.

----------------------------------------------------------------------
- Rick Stevens, Principal Engineer          rstevens vitalstream com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-     Never put off 'til tommorrow what you can forget altogether!   -
----------------------------------------------------------------------