- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- ProLiant Support Pack after Kernel Update
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2011 12:20 AM
тАО04-13-2011 12:20 AM
Is there a "correct" way to treat the PSP after kernel update, i.e. to build from-source modules against the new kernel?
I installed RHEL5u5 64 bit and applied PSP 8.43. After a yum update to a more current release, I now cannot mkinitrd (to update qla2xxx settings in initrd for multipath) because I get the following error: -
No module hpahcisr found for kernel 2.6.18-238.1.1.el5, aborting.
Modules that are built are as follows: -
./2.6.18-194.el5/extra/hp-be2iscsi
./2.6.18-194.el5/extra/hp-netxtreme2
./2.6.18-194.el5/extra/hp-e1000
./2.6.18-194.el5/extra/hp-nx_nic
./2.6.18-194.el5/extra/hp-mlnx-en
./2.6.18-194.el5/extra/hp-qla4xxx
./2.6.18-194.el5/extra/hp-tg3
./2.6.18-194.el5/extra/hp-igb
./2.6.18-194.el5/extra/hp-e1000e
./2.6.18-194.el5/kernel/drivers/usb/serial/hp4x.ko
./2.6.18-194.el5/kernel/drivers/misc/hpilo.ko
./2.6.18-194.el5/kernel/drivers/pci/hotplug/pciehp.ko
./2.6.18-194.el5/kernel/drivers/pci/hotplug/acpiphp.ko
./2.6.18-194.el5/kernel/drivers/pci/hotplug/acpiphp_ibm.ko
./2.6.18-194.el5/kernel/drivers/pci/hotplug/shpchp.ko
./2.6.18-194.el5/kernel/drivers/pci/hotplug/fakephp.ko
./2.6.18-194.el5/kernel/drivers/scsi/hpahcisr
./2.6.18-194.el5/kernel/drivers/scsi/hpahcisr/hpahcisr.ko
./2.6.18-194.el5/kernel/drivers/scsi/hptiop.ko
./2.6.18-194.el5/kernel/drivers/md/dm-hp-sw.ko
./2.6.18-238.1.1.el5/weak-updates/hp-be2iscsi
./2.6.18-238.1.1.el5/weak-updates/hp-netxtreme2
./2.6.18-238.1.1.el5/weak-updates/hp-e1000
./2.6.18-238.1.1.el5/weak-updates/hp-nx_nic
./2.6.18-238.1.1.el5/weak-updates/hp-mlnx-en
./2.6.18-238.1.1.el5/weak-updates/hp-qla4xxx
./2.6.18-238.1.1.el5/weak-updates/hp-tg3
./2.6.18-238.1.1.el5/weak-updates/hp-igb
./2.6.18-238.1.1.el5/weak-updates/hp-e1000e
./2.6.18-238.1.1.el5/kernel/drivers/usb/serial/hp4x.ko
./2.6.18-238.1.1.el5/kernel/drivers/misc/hpilo.ko
./2.6.18-238.1.1.el5/kernel/drivers/pci/hotplug/pciehp.ko
./2.6.18-238.1.1.el5/kernel/drivers/pci/hotplug/acpiphp.ko
./2.6.18-238.1.1.el5/kernel/drivers/pci/hotplug/acpiphp_ibm.ko
./2.6.18-238.1.1.el5/kernel/drivers/pci/hotplug/shpchp.ko
./2.6.18-238.1.1.el5/kernel/drivers/pci/hotplug/fakephp.ko
./2.6.18-238.1.1.el5/kernel/drivers/scsi/hptiop.ko
./2.6.18-238.1.1.el5/kernel/drivers/md/dm-hp-sw.ko
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2011 01:36 AM
тАО04-13-2011 01:36 AM
SolutionThe B110i is a software-based RAID controller that is upwardly compatible with "real" hardware-based SmartArray raid controllers. If your system contains a B110i controller, you should never update a kernel before checking that the kernel version is listed as supported in the Release Notes of the B110i driver. If it's not supported and there is no updated version of the B110i driver available yet, you must not install the kernel update.
You should now download the specific kernel version 2.6.18-238 from https://rhn.redhat.com (your RedHat Network password is required) and live with it until an updated version of the hpahcisr driver package becomes available.
HP provides the Proliant Support Pack and the hpahcisr driver in a yum-accessible repository format too. You can even mirror the repository to your organization's internal servers, if you wish:
http://downloads.linux.hp.com/SDR/
See the "Getting Started" link at the left column for instructions.
----begin opinion piece----
I'm rather displeased that HP chose to use the SmartArray name with a software-based controller like B110i. I don't think it does anything good to the SmartArray brand name.
It would be better if HP provided hpahcisr driver updates for all (or most) errata kernels in a timely manner, but so far I'm afraid I can only describe HP's response to errata kernel releases as "slow and spotty".
At the moment, I would not recommend the B110i controller for new Linux implementations unless you know for sure the system is not going to require any updates.
----end opinion piece----
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2011 04:39 AM
тАО04-13-2011 04:39 AM
Re: ProLiant Support Pack after Kernel Update
So to address my immediate concern, it appears I can use the --allow-missing switch to mkinitrd to update my initrd.
Curious why that modules been installed (not sure if it's been loaded, got to do some more testing) by PSP though, since it wouldn't have detected any matching hardware. I guess hpsum /s isn't quite as intelligent as it should be.
So the remaining query is whether or not there is anything to do generally for PSP post kernel update. I know for example that the hp-ilo module gets recompiled by /etc/init.d/hp-ilo if a module doesn't exist for the currently booting kernel, but I don't know what the rest do - looks like they just get moved to "weak-updates"?
I'm going to have a play building a box and applying PSP before and after patching and see what differences there appear to be, but any further insight into best practice approach would be appreciated (apart from don't install newer kernels than the PSP release notes say :D)
Thanks, Simon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2012 10:10 AM
тАО10-15-2012 10:10 AM
Re: ProLiant Support Pack after Kernel Update
[root@xyz]# rpm -qp --scripts kmod-hpahcisr-1.2.6-13.rhel5u8.x86_64.rpm
postinstall scriptlet (using /bin/sh):
if [ -e "/boot/System.map-2.6.18-308.el5" ]; then
/sbin/depmod -aeF "/boot/System.map-2.6.18-308.el5" "2.6.18-308.el5" > /dev/null || :
fi
## GMM - Added hpahcisr to PREMODS variable in
## /etc/sysconfig/mkinitrd/hpahcisr used by mkinitrd.
## Puts hpahcisr at the top of the driver load order in initrd.
echo "PREMODS='hpahcisr '" > /etc/sysconfig/mkinitrd/hpahcisr
chmod 755 /etc/sysconfig/mkinitrd/hpahcisr
Comment this line you will not see the error . Apparently removing the rpm does not remove this file.
[root@raptor-bk ~]# cat /etc/sysconfig/mkinitrd/hpahcisr
# PREMODS='hpahcisr '
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-07-2013 07:38 AM
тАО12-07-2013 07:38 AM
Re: ProLiant Support Pack after Kernel Update
Thanks!!! adding --allow-missing to the mkinitrd worked for me.......saturday morning patching. Last thing I need is something that is going to slow me down like a kernel panic