System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Entries added in grub.conf by PSP

SOLVED
Go to solution
atqquebec
Advisor

Entries added in grub.conf by PSP

Hi,

 

I just realized I got new entries in grub.conf that seem to have beeen added by my last PSP install test (this is a test server).  It also changed the default boot to the latest (entry no.4).

 

Can someone tell me

 

  • Why they're there
  • Can I remove them and set the default to the default Red Hat kernel?  (I just tested a kernel upgrade and it set it back to default=0 (default RH kernel)
  • Is it documented somewhere?

Here are the entries:

 

# This entry (no. 2) added by Proliant HBA install script
# in package cpq_cciss-3.6.28-15.rhel5
title HP-2.6.18-274.el5
        root (hd0,0)
        kernel /vmlinuz-2.6.18-274.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
        initrd /HP-initrd-2.6.18-274.el5.img


# This entry (no. 3) added by Proliant HBA install script
# in package hpahcisr-1.2.6-9.rhel5
title HP-2.6.18-274.el5-0
        root (hd0,0)
        kernel /vmlinuz-2.6.18-274.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
        initrd /HP-initrd-2.6.18-274.el5.img-0


# This entry (no. 4) added by Proliant HBA install script
# in package mptlinux-4.00.13.09-6.rhel5
title HP-2.6.18-274.el5-1
        root (hd0,0)
        kernel /vmlinuz-2.6.18-274.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
        initrd /HP-initrd-2.6.18-274.el5.img-1


1 REPLY
Matti_Kurkela
Honored Contributor
Solution

Re: Entries added in grub.conf by PSP

When a storage driver that controls your system disk(s) is updated, the updated driver must be included in the initrd file. Otherwise the old version of the driver will still be used to mount your root filesystem... which will obviously make it (effectively) impossible to unload the old driver without rebooting the system.

 

The HP storage driver update packages don't check if the driver that is being updated is in fact required to mount the root filesystem, since complexities like software RAID or LVM might mislead an automated check. Therefore, HP has chosen that the update packages will always create a new initrd and a new set of boot options, just to be safe.

 

This is not unique to HP updates: any storage driver updates that are not integrated in the RedHat kernel must do the same, if they need to replace the driver that runs the system disk.

 

Too bad you did not identify your hardware models nor your storage configuration... if your system runs fine with the RedHat kernel, you can skip the storage driver packages if the features/optimizations provided by them are not necessary to you. Eventually the equivalent driver versions tend to end up being included in the RedHat standard kernel packages, too...

 

However, there is one big exception to that:

If your hardware includes a Smart Array B110i, you will need the hpahcisr driver package. Without it, the system will treat the B110i controller as a standard non-RAID AHCI SATA controller... since that's exactly what the physical hardware is. The B110i is a software/BIOS-based RAID, which only uses a metadata format that is compatible with its bigger SmartArray E and P series brothers. All modern Linux distributions include a basic AHCI controller driver, and will automatically use it on the B110i unless the hpahcisr package is installed and the proper procedures have been followed.

 

I think RedHat regards the hpahcisr driver as a simple duplication of the Linux software RAID functionality, and probably won't include it in their distribution. I guess RedHat would rather see the Smart Array metadata support included in (an extended version of) the dmraid utility, which reads various software/BIOS RAID metadata formats and implements a compatible RAID setup using tried-and-true Linux software RAID routines. That would make the hpahcisr driver unnecessary.

 

But I guess HP wants to keep their Smart Array metadata format proprietary, so this is unlikely to happen...

MK