startup order for emulex driver

[Diane M. Morin]

Hi,

I'm running RHAS 3 on a bl20p G4. This system has an emulex card in it that starts the driver after the mount script is run when booting. Is there away to have the emulex start up before the mount script so my san disk can be mounted via /etc/fstab?

Thanks
diane

[Ian Vaughan]

Howdy,
I know it's cheating but can you not just put a "mount -a " in rc.local after the script that has done the scan for LUN's?

HTH
Ian

[Diane M. Morin]

Hi,

How would I get around the intial mount? When the system boots it tries to mount all the disks in fstab. When it gets to the san device it's unable to mount it because the emulex driver hasn't been started. So then the systems gives you an option to go into maintenance mode or reboot.

diane

[Matti_Kurkela]

/etc/rc.modules is a script that gets executed very early in the boot sequence, if it exists. You could use it to load the Emulex driver.
I have this in one of our RHES3 servers with Emulex FC cards:

---- begin /etc/rc.modules -------------
#!/bin/sh
# Load SAN modules and do necessary init
# -- mkurkela 4.8.2004

. /etc/init.d/functions

action "Load Linux multipath support" modprobe multipath
action "Load Emulex FibreChannel storage driver" modprobe lpfc
action "Identify SAN volumes" devlabel reload
------ end /etc/rc.modules -------------

If you cannot arrange the driver to load before the mount phase, add the option "noauto" to the FC disk lines in /etc/fstab.

The mount script (and the mount -a command) will skip all disks marked with "noauto" option. You must then have explicit "mount " or "mount " commands in some later boot phase.

[Diane M. Morin]

Thanks,

I'll give the /etc/rc.modules a try.

diane