topic Cannot see XP1024 LUNS on reboot without performing an hp_rescan in Operating System - Linux

Cannot see XP1024 LUNS on reboot without performing an hp_rescan

jmazzaro — Fri, 03 Aug 2007 12:49:19 GMT

Hi all,

We have a DL585 running Red Hat AS4 UP5 64Bit
Our FC cards are: Qlogic 2340's.

We can't see certain luns attached to our XP1024 after a reboot. They disapear. Yet, when we perform an hp_rescan, they show up. We have 600 Luns assigned to this server, but only 435 show up after a reboot. Any ideas why?

Re: Cannot see XP1024 LUNS on reboot without performing an hp_rescan

Steven E. Protter — Sun, 05 Aug 2007 09:08:48 GMT

Shalom,

Perhaps you have exhausted resources on the system. Check the kernel and whether update 5 of RH 4 is certified with the hardwware.

In my opinion its either kernel or drivers.

SEP

Re: Cannot see XP1024 LUNS on reboot without performing an hp_rescan

Ivan Ferreira — Sun, 05 Aug 2007 09:49:53 GMT

From "Using the QLogic HBA driver for
single-path or multipath failover mode
on Linux systems"

If you have trouble detecting these devices, run the /opt/hp/hp_fibreutils/probe-luns script during system boot.

â ¢ Enter the following commands to install the probe-luns startup code:
# cd /opt/hp/hp_fibreutils/pbl
# ./pbl_inst.sh -i
â ¢ Enter the following commands to remove the probe-luns startup code:
# cd /opt/hp/hp_fibreutils/pbl
# ./pbl_inst.sh -u

Re: Cannot see XP1024 LUNS on reboot without performing an hp_rescan

jmazzaro — Mon, 06 Aug 2007 08:43:04 GMT

I ran this command and rebooted the system but it sill only sees 432 disks.

Re: Cannot see XP1024 LUNS on reboot without performing an hp_rescan

jmazzaro — Mon, 06 Aug 2007 09:15:19 GMT

OK,

I checked the startup script(/etc/rc.d/rc.sysinit)
and noticed that it added a probe-luns -d, which doesn't do the job, even from the command line. I'm going to modify the script to do a probe-luns -a to see if it resolves it.

It works. We now have the proper number of LUNS after a reboot.
We have a call into HP to see if this can be the permanent solution, or if there is a driver or kernel parameter that needs to be changed so this can be native to reboot behavior.