Hi Brent,
Do these machines have XFS as their root filesystem?
That would explain what is happening.
When you install a kernel, it rebuilds the mkinitrd, while when you
install a kernel module, it only does a depmod.
To look at the scripts do a
rpm -q --scripts <package>
like
rpm -q --scripts kernel
or
rpm -q --scripts kernel-module-xfs-2.6.18-128.1.10.el5
Troy
Brent L. Bates wrote:
Still no joy.
I uninstalled:
kernel-2.6.18-128.1.10.el5.x86_64
kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64
rebooted into old kernel. Did following command:
# yum install kernel-2.6.18-128.1.10.el5.x86_64
kernel-devel-2.6.18-128.1.10.el5.x86_64
kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64
After the above finished, I double checked the size of
/boot/initrd-2.6.18-128.1.10.el5.img and knew it was too small for things to
have worked, but I rebooted anyways. It failed to fully boot as it couldn't
mount the XFS file systems.
Here is a list of all `yum' RPM's installed:
yum-3.2.19-22.sl.noarch
yum-aliases-1.1.16-14.el5.noarch
yum-autoupdate-1-1.SL.noarch
yum-changelog-1.1.16-14.el5.noarch
yum-conf-53-1.SL.noarch
yum-cron-0.6-3.el5.noarch
yum-downloadonly-1.1.16-14.el5.noarch
yumex-2.0.3-1.0.el5.noarch
yum-filter-data-1.1.16-14.el5.noarch
yum-keys-1.1.16-14.el5.noarch
yum-kmod-1.1.16-14.el5.noarch
yum-list-data-1.1.16-14.el5.noarch
yum-merge-conf-1.1.16-14.el5.noarch
yum-metadata-parser-1.1.2-2.el5.x86_64
yum-priorities-1.1.16-14.el5.noarch
yum-protectbase-1.1.16-14.el5.noarch
yum-protect-packages-1.1.16-14.el5.noarch
yum-refresh-updatesd-1.1.16-14.el5.noarch
yum-security-1.1.16-14.el5.noarch
yum-tsflags-1.1.16-14.el5.noarch
yum-updatesd-0.9-2.sl.noarch
yum-upgrade-helper-1.1.16-14.el5.noarch
yum-utils-1.1.16-14.el5.noarch
yum-verify-1.1.16-14.el5.noarch
If you have any suggestions or need more information, please let me know.
