Question about Linux HBA driver verion upgrade

[Gary L]

Hi

Our SAN admin sent a email to me let me upgrade the RHEL Linux SAN connect servers's HBA driver version from current 7.05.00-fo to 7.07.05.02 (HP Recommended)for support their SAN upgrade. I have a question?

Our Linux serers are all blade BL20P g3 box.
OS: RHEL ES3 update 4.
HBA Model: QLA2312 A6826A
HBA Firmware version: 3.03.11
HBA Driver version 7.05.00-fo

How to upgrade the HBA driver version?

I downloaded the "hp_qla2x00-2007-10-05" (include: hp_qla2x00src-7.07.05.08-1.linux.rpm and hp_qla2x00src-8.01.07.25-1.linux.rpm etc.) from hp.com. And I ran the command ./install installed them, reboot server and run the command
rpm -q hp_qla2x00src and
rpm –q fibreutils
according as its installation guide. I could see hp_qla2x00src-7.07.05.08-2 and
fibreutils-2.4-1
But, through check via command # cat /proc/scsi/qla2300/0 /1 the HBA driver version still 7.05.00-fo doen't update.

Through HP SANsurfer the version of HBA driver still old.

How to upgrade Linux HBA driver verison (HP-UX just install a higher version depot)?

Any answers will be very appreciate!

[Gary L]

And

How to upgrade HBA firmware version?

thanks

[skt_skt · Accepted solution]

i guess each rpm will have an associated read me file.. so that is the best one to follow..

unmount all SAN volume..(we do reboot the server after commenting the fstab entries for san file systems... we normally upgrade hba driver along with kernel upgrade if required)

uninstall the current rpm reinstall the new one(or existing one) which ever is applicable . Also check the licenses are still valid for the san management software like power path or which ever is applicable.

[Gary L]

Hi Santhosh

Thanks for your above suggestions.

The "readme" of hp_qla2x00-2007-10-05 just list how to install this rpm package (./install) That's it. I have followed the steps but it didn't work. Still show the old HBA driver version. So I thought probably the software that I downloaded was wrong or not necessary or need more ... So i post my questions wanna got a right way to upgrade the HBA driver version for RHEL.

You mean, the software "hp_qla2x00-2007-10-05" is correct for HBA upgrade? Just need uninstall the old one and install the new one?

[Don Vanco - Linux Ninja]

When you run the install do you see messages about a "new initrd file" being built?

The drivers are shoehorned into an initrd - it may be that for whatever reason a new initrd was not built, or if it was it is not being called at boot.

Look at the date stamps on the .img files in /boot - one should correspond to both your running kernel version AND to near the date/time you did the "upgrade"

Also - were there any changes made to /etc/modprobe.conf?? (should not have been for a simple upgrade, but worth a peek anyway)

I just installed the HBA drivers today (albeit for Blades) and the installer was actually "INSTALL" (in caps) - is that what you used???

HTH
Don

[Gary L]

Thanks Don.

I'm sorry for reply this and assign the points to you late.

Have a great day

-G

[Gary L]

Hi Don and Santhosh

I think I find out the reason why installed the new HBA driver but system still show the old one.

I should do some tasks in /boot/grub/grub.conf. Commented the old kernel boot "default=0" and change to new entry that added by Proliant HBA install script "default=3" initrd /hp-initrd-2.4.21-27.ELsmp.img.

I think, if reset those SAN linux servers the new HBA driver version will list.

Thanks a lot.

[Don Vanco - Linux Ninja]

Gary -
Unfortunately, without seeing your grub.conf file we can't really say what is "right".

By default, the driver installer should:
- look at the kernel you are running RIGHT NOW and build a driver for the /lib/modules/ tree
- (possibly) make edits to /etc/modprobe.conf to include options (or new options) for the driver - like multipath or load balance options if you've more than one FC port connection
- build a required initrd that includes the new drivers
- edit your grub.conf file to call the correct initrd (if it didn't simply copy off the current one and replace it with the new one with the existing name)

I believe by default it just renames the initrd for the current kernel and then replaces it with the new one - meaning all you should have to do is reboot and you're good to go (or manually unload the drivers, but that can be a PITA)

My fear is (without a machine I can check on myself) that you're actually talking about editing in the OLD initrd! Is there any way you can post up your grub.conf file and a long listing if the files in /boot?

I also can't say with certainty when the SANSurfer utility will report the new driver - it should be current over a reboot, but at a minimum you should restart the agents. Sorry I don't know them by name, but you should be able to look over /etc/init.d and see the script for it, and likely run:
"service SANSurfer_Agent_Name restart" (with the correct script)

[Gary L]

Hi Don

I met a problem, when I done the ./INSTALL (install new HBA driver), changed the /boot/grub/grub.conf, reboot server. System reset stop at
...
mounting root filesystem
mount: error 2 mounting ext3
pivotroot: pivot_root )/sysroot, /sysroot/initrd ) failed:2
umount initrd/proc failed:2
Freeing unused kernel memory: 228k freed
Kernel Panic: No init found. Try passing init= option to kernel.

grub.conf
==========
# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/vg00/lv00
# initrd /initrd-version.img
#boot=/dev/cciss/c0d0
#default=1 # commented out by Proliant HBA install script
default=5
fallback=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Enterprise Linux ES (2.4.21-50.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-50.EL ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-50.EL.img
title Red Hat Enterprise Linux ES (2.4.21-50.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-50.ELsmp ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-50.ELsmp.img
title Red Hat Enterprise Linux ES (2.4.21-27.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-27.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.4.21-27.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.EL ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-27.EL.img

# This entry (no. 4) added by Proliant HBA install script
# in package cpq_cciss-2.4.64-6.rhel3
title HP-2.4.21-27.EL
root (hd0,0)
kernel /vmlinuz-2.4.21-27.EL ro root=/dev/vg00/lv00
initrd /HP-initrd-2.4.21-27.EL.img


# This entry (no. 5) added by Proliant HBA install script
# in package cpq_cciss-2.4.64-6.rhel3
title HP-2.4.21-27.ELsmp
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=/dev/vg00/lv00
initrd /HP-initrd-2.4.21-27.ELsmp.img


/boot
=====
config-2.4.21-27.EL
config-2.4.21-27.ELsmp
config-2.4.21-50.EL
config-2.4.21-50.ELsmp
grub
HP-initrd-2.4.21-27.EL.img
HP-initrd-2.4.21-27.ELsmp.img
initrd-2.4.21-27.EL.img
initrd-2.4.21-27.ELsmp.img
initrd-2.4.21-27.ELsmp.img.old
initrd-2.4.21-50.EL.img
initrd-2.4.21-50.ELsmp.img
kernel.h
message
message.ja
System.map-2.4.21-27.EL
System.map-2.4.21-27.ELsmp
System.map-2.4.21-50.EL
System.map-2.4.21-50.ELsmp
vmlinux-2.4.21-27.EL
vmlinux-2.4.21-27.ELsmp
vmlinux-2.4.21-50.EL
vmlinux-2.4.21-50.ELsmp
vmlinuz-2.4.21-27.EL
vmlinuz-2.4.21-27.ELsmp
vmlinuz-2.4.21-50.EL
vmlinuz-2.4.21-50.ELsmp

[Gary L]

Additional input:

/lib/modules]# ll
total 24
drwxr-xr-x 6 root root 4096 Jul 24 2007 .
drwxr-xr-x 11 root root 4096 Feb 17 2005 ..
drwxr-xr-x 4 root root 4096 Feb 1 13:46 2.4.21-27.EL
drwxr-xr-x 4 root root 4096 Feb 1 13:46 2.4.21-27.ELsmp
drwxr-xr-x 3 root root 4096 Jul 24 2007 2.4.21-50.EL
drwxr-xr-x 3 root root 4096 Jul 24 2007 2.4.21-50.ELsmp

no HP-initrd-2.4.21-27.ELsmp.img and HP-initrd-2.4.21-27.EL.img entries there.

The kernel boot throug below entry
title HP-2.4.21-27.ELsmp
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=/dev/vg00/lv00
initrd /HP-initrd-2.4.21-27.ELsmp.img

[Gary L]

Additional input:

/lib/modules]# ll
total 24
drwxr-xr-x 6 root root 4096 Jul 24 2007 .
drwxr-xr-x 11 root root 4096 Feb 17 2005 ..
drwxr-xr-x 4 root root 4096 Feb 1 13:46 2.4.21-27.EL
drwxr-xr-x 4 root root 4096 Feb 1 13:46 2.4.21-27.ELsmp
drwxr-xr-x 3 root root 4096 Jul 24 2007 2.4.21-50.EL
drwxr-xr-x 3 root root 4096 Jul 24 2007 2.4.21-50.ELsmp

no HP-initrd-2.4.21-27.ELsmp.img and HP-initrd-2.4.21-27.EL.img entries there.

The kernel boot throug below entry
title HP-2.4.21-27.ELsmp
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=/dev/vg00/lv00
initrd /HP-initrd-2.4.21-27.ELsmp.img

/boot folder no System.map-HP-initrd-2.4.21-27.ELsmp informations.

[Gary L]

Sorry I forgot paste a important entry in /boot. It's

System.map -> System.map-2.4.21-50.ELsmp

[Don Vanco - Linux Ninja]

The issue is that there is no "Option 5" to boot from! grub counts from ZERO - your last available kernel appears to be 4!!!

When it is booting select one of the other kernels and it should boot OK - and then go in and fix your error.

Again - I am sot sure that the initrd images with the HP in the filename are the correct ones - but at least fixing the "default=5" will get you booting again so you can test some more....

[Gary L]

Hi Don

I think the default = 5 is correct, you could re-count
...
#default=1 # commented out by Proliant HBA install script
default=5
fallback=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
(Entry 0)
title Red Hat Enterprise Linux ES (2.4.21-50.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-50.EL ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-50.EL.img

(Entry 1)
title Red Hat Enterprise Linux ES (2.4.21-50.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-50.ELsmp ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-50.ELsmp.img

(Entry 2)
title Red Hat Enterprise Linux ES (2.4.21-27.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-27.ELsmp.img

(Entry 3)
title Red Hat Enterprise Linux ES-up (2.4.21-27.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.EL ro root=/dev/vg00/lv00
initrd /initrd-2.4.21-27.EL.img

(Entry 4)
# This entry (no. 4) added by Proliant HBA install script
# in package cpq_cciss-2.4.64-6.rhel3
title HP-2.4.21-27.EL
root (hd0,0)
kernel /vmlinuz-2.4.21-27.EL ro root=/dev/vg00/lv00
initrd /HP-initrd-2.4.21-27.EL.img

(Entry 5)
# This entry (no. 5) added by Proliant HBA install script
# in package cpq_cciss-2.4.64-6.rhel3
title HP-2.4.21-27.ELsmp
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=/dev/vg00/lv00
initrd /HP-initrd-2.4.21-27.ELsmp.img

System boot from this entry, past is boot from 1. As you know boot from 1 is ok, boot from 5 stop at above part.

In /boot, System.map -> System.map-2.4.21-50.ELsmp It is old .50 not the new HP-initrd.

[Don Vanco - Linux Ninja]

Sorry - I did mis-count (because the form of this forum doesn't let you see the entire thread when you reply).

An am confused why you're not booting to the "latest" installed kernel, but that is your choice. Have you validated that this kernel is supported by the driver? Sorry I don't have a point of reference and I don't have any 2.4 systems any more...


Anyway -

I would:
re-make the sym link for system.map, and point it to System.map-2.4.21-27.ELsmp

I would edit entry #5 (hit "e" in the boot menu for the kernel, in the menu that follows you can move to the line that calls the initrd image, hit "e" again and edit it (remove the HP-) then hit "b" to boot with that edit. Note that this does not fix it permanently - you'll have to make the same edit once the system is booted.

To overstate the obvious - it sounds like that "HP" initrd image is bogus. The only way to make sure you have a valid one may be to build it manually, forcing in the modules you require....

[Don Vanco - Linux Ninja]

Also note - the /lib/modules tree will not necessarily reflect every "named" initrd with a unique sub-directory - only the actual kernels installed. You can have numerous initrd's for a single kernel, and the whole idea behind the grub menu process is that you can "pair" a kernel with an initrd image as you required....

Likewise with system.map - one per kernel works just fine.

[Gary L]

Hi Don

Our OS of SAN linux servers are all RHEL ES 3 update 4 ( yes, pretty old ) so the kernel is 2.4.21-27.ELsmp.
I'm not quite sure your means "An am confused why you're not booting to the "latest" installed kernel" Your mentioned latest verson is it entry 1: 2.4.21-50? Yes, I boot system for it no problem, but this kernel NO update HBA driver info.

As you know Actually the grub.conf file modified by the HBA driver install script ( you could see the remarks on entry 4 5 and default = 0.
When I ran the ./INSTALL for update the HBA driver version, this script did below items:
1. made two new img files HP-initrd-2.4.21-27.EL.img and HP-initrd-2.4.21-27.ELsmp.img

2. Modified the /boot/grub/grub.conf
a. commented the default=0,
b. add the last two entries 4 and 5 and
c. change the default=5.

Unfortunately, this install script has some bugs, the system cold not startup. probably I need manually do something, like chang he img file's name?

Our server is HP Prolant Blade Bl20p g3. Two FC A6828A Qlogic cards. I download the new HBA driver version 7.07.05.08 for hp.com, ran the command "./install" That'all do i miss some parts? Would you please list your steps when you update your HBA driver couple weeks ago.

Thanks

-G

[Gary L]

Hi Don

All steps that what i am doing on HBA driver upgrade are:

1. # cat /proc/scsi/qla2300/0
QLogic PCI to Fibre Channel Host Adapter for QLA2312 :
Firmware version: 3.03.11, Driver version 7.05.00p8-fo.
SAN admin recommend versoin is 7.07.05.02 or later.

2. Plan to upgrade the HBA driver version, down the hp_qla2x00-2007-10-05 from http://h18006.www1.hp.com/products/sanworks/softwaredrivers/multipathoptions/qlogicv70.html ( our Linux server verison are all RHEL ES 3 udpate 4).
It include:
fibreutils-2.4-1.linux.i386.rpm hp_qla2x00-7.07.05.08-1.src.rpm hp_qla2x00src-8.01.07.25-1.linux.rpm set_parm2.24
fibreutils-2.4-1.linux.ia64.rpm hp_qla2x00-8.01.07.25-1.src.rpm install set_parm2.26
fibreutils-2.4-1.linux.x86_64.rpm hp_qla2x00src-7.07.05.08-1.linux.rpm revision_notes

3. uploaded them onto SAN server

4. # ./install

5. reboot server

6. stop at
...
mounting root filesystem
mount: error 2 mounting ext3
pivotroot: pivot_root )/sysroot, /sysroot/initrd ) failed:2
umount initrd/proc failed:2
Freeing unused kernel memory: 228k freed
Kernel Panic: No init found. Try passing init= option to kernel.

7. through check found: install script changed grub.conf let system boot from
title HP-2.4.21-27.ELsmp
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=/dev/vg00/lv00
initrd /HP-initrd-2.4.21-27.ELsmp.img

and added two new img files in /boot, HP-initrd-2.4.21-27.EL.img and HP-initrd-2.4.21-27.ELsmp.img.

Do i loss some steps?

-G

[Don Vanco - Linux Ninja]

According to the release notes, the minimum required release is RHEL 3 Update 8. Does this kernel that you're trying to make work correlate to RHEL 3 U8 or U9??

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=315739&swItem=co-54962-1&prodNameId=315741&swEnvOID=1080&swLang=8&taskId=135&mode=4&idx=0

According to the RHEL 3 Update 8 release notes it included kernel-2.4.21-43.EL

I would encourage you to:
1) reboot to the -50 kernel
2) attempt to install the driver against that kernel

IMO - you are installing on an unsupported kernel. From what I can see the only changes with the U8 kernel (wrt FC support) was the addition of "disk_dump" function - but there are other notes about FC HBAs as well....
http://mirror.centos.org/centos/3/docs/release-notes/as-x86/RELEASE-NOTES-U8-x86-en.html

Don

[Gary L]

Hi Don

I think I lost a important part. This version of HBA driver only support RHEL 3 update 8 and later. Our current OS version are all update 4, lower then its min requirement. I think, that's the reason why my upgrade failure.
So, either upgrade all of them to update 8 or forget it. UPgrade HBA driver just a recommend.

Anyway, Thanks a lot.

Have a great day.

-Gary

[Don Vanco - Linux Ninja]

Gary -
Even though you originally installed with RHEL 3U4 you have at least one kernel present that meets the requirement of the HBA driver. You probably got this through a series of updates.

You have:
2.4.21-50

Which is NEWER than the required minimum of 2.4.21-43.

This is why I suggested that you boot to this kernel, and then attempt the adapter installation with this as the running kernel.


I'm curious - what to you get when you run:
cat /etc/redhat-release
?

Don

[Gary L]

# cat /etc/redhat-release
Red Hat Enterprise Linux ES release 3 (Taroon Update 4)

RHEL 3 update 4. As you know the kernel should be 2.4.21-27. But I have no idea when why there is a SAN linux server was installed the 2.4.21-50 kernel, and boot from it.
It is uncorrect, right?

I have a new question probably need restart a thread, but anyway I wanna ask you first:

Just now, I did the HBA driver version upgrade through HP PSP (SmartStart CD). I just wanna try this way. It doen't work. BUT, after PSP install, this server was automatic rebooted over five times. When the server startup, within 2 min, it was rebooted atuomaticlly. It boot from 2.4.21-27.ELsmp. I changed boot kernel to 2.4.21-27.EL, system didn't auto reboot but loss all SAN disk. lssd show nothing.

Do you know what's happying.

BTW,
I did the PSP installation on two two server, PSP version is 7.70. One is good, another have auto reboot problem.

Sigh!

-G

[Don Vanco - Linux Ninja]

Gary - I would take the rebooting server into single user mode and read the logs.

The reason the non-SMP kernel boots OK but has no SAN disks is likely because it did NOT get modules compiled for it by the driver install, or at least there was no initrd image created for it that has the required drivers.

The 7.70 PSP is quite old. There are likely several "stand alone" releases of the driver that are newer than this PSP that will still work with the kernel you boot with.

As far as why you have a server that has the -50 kernel on it.... only you can answer that one! ;) However - if you can boot to that kernel and it's stable, you may be able to install the current driver and SANSurfer and get on with your life.

[Gary L]

Hi Don

You means, forget kernel 2.4.21-27.ELsmp because of its crash , instead of it, Boot from 2.4.21-27.EL. And I need install the latest version of SANSurfer and HBA driver versoin on this kernel, right?

The reason why I'm using PSP 7.70 is from hp.com it is the latest version of PSP for RHEL 3."psp-7.70.rhel3.linux.en". I download the psp-7.91.rhel4.linux.en v7.91 for RHEL4 in the same time. Do you know where could find the higher version of PSP for RHEL3.

Thanks a lot.

-Gary

[Don Vanco - Linux Ninja]

I would not risk installing the drivers against the 2.4.21-27.EL kernel - but you CAN boot to it and try to see if you can see why this server is reboot.

What I am telling you to consider is booting the the 2.4.21-50 (smp) kernel that you have installed and attempt to load the LATEST drivers that you have against it. It meets the minimum kernel level requirement of the driver and you just might get the driver to install without issue.

I am concerned because you keep jumping back and forth between driver releases - and you may end up with a very messed up server (if you haven't already).

I would NOT look to install older releases of the PSP - there is no point attempting to use that tool simply to get a the Fibre Channel driver. Concentrate on getting the system stable again, the move on toward the next step.