Kernel did not update after up2date

[vladgur]

I searched these forums and found a way to update kernel using up2date:
up2date -noX -f kernel
My old kernel was 2.4.18-27.7 and the new one I tried to update with was 2.4.20-13.7.
So I went ahead and issued the above up2date command. It did download the kernel rpm but didnt seem to install it. So I went to /var/spool/up2date and issued
rpm -ivh kernel-2.4.20-13.7.i686.rpm
After that was complete I checked /etc/grub.conf and surely there it was:

default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-13.7)
root (hd0,0)
kernel /vmlinuz-2.4.20-13.7 ro root=/dev/hda2
initrd /initrd-2.4.20-13.7.img
title Red Hat Linux (2.4.18-27.7.x)
root (hd0,0)
kernel /vmlinuz-2.4.18-27.7.x ro root=/dev/hda2
initrd /initrd-2.4.18-27.7.x.img

Just to make sure, I edited my lilo.conf and made this the default label:

image=/boot/vmlinuz-2.4.20-13.7
label=linux
root=/dev/hda2
read-only
initrd=/boot/initrd-2.4.20-13.7.img

So basically, this guaranteed that I will boot into 2.4.20...reboot...30 seconds....

[email protected] [/var/spool/up2date]# uname -a
Linux hostname.mydomain.com 2.4.18-27.7.x #1 Fri Mar 14 06:44:53 EST 2003 i686 unknown

I checked dmesg:

[email protected][/var/spool/up2date]# dmesg
Linux version 2.4.18-27.7.x ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-112)) #1 Fri Mar 14 06:44:53 EST 2003
.
.
.
Kernel command line: auto BOOT_IMAGE=linux ro root=302 BOOT_FILE=/boot/vmlinuz-2.4.18-27.7.x

It seems that the new kernel just refuses to boot. ANy advice would be appreciated....

cPanel.net Support Ticket Number:

cPanel.net Support Ticket Number:

 

[vladgur]

thanks, that was the missing piece

cPanel.net Support Ticket Number:

 

[Adz]

I had the same problems as above, made the same steps to correct but on running lilo I get


[email protected] [~]# lilo
Added linux.too
Fatal: Kernel doesn't support initial RAM disks

Any ideas?

cPanel.net Support Ticket Number:

 

[sexy_guy]

Originally posted by Adz
I had the same problems as above, made the same steps to correct but on running lilo I get


[email protected] [~]# lilo
Added linux.too
Fatal: Kernel doesn't support initial RAM disks

Any ideas?

cPanel.net Support Ticket Number:

To apply the new kernel, after you have made the necesarry modifications etc you should have typed;

lilo -v -v

not

lilo, which does nothing.

cPanel.net Support Ticket Number:

 

[nitromax]

New Kernel Won't Boot...

I have successfully updated the kernel with up2date on one of our RH 7.3 servers that uses lilo as the boot loader, no problems.

But on another one of our RH 7.2 machines I go thru the up2date process and I just can't get the new kernel to boot. I think it's using grub, but I'm honestly not sure. I have no anaconda-ks.cfg file like our other newer servers do. I have updated the lilo.conf file and the grub.conf file just to make sure, but still nothing...

After much research I have found that my /proc/cmdline file looks like this:

initrd=initrd.img root=/dev/sda1 BOOT_IMAGE=vmlinuz auto


I think that is the problem, as our 7.3 machine which I upgraded with no problems looks like this:

auto BOOT_IMAGE=linuxnew ro root=307 BOOT_FILE=/boot/vmlinuz-2.4.20-19.7

But again, the 7.3 machine uses lilo for sure! So I'm not sure exactly if that cmdline file is the problem, and if it is I'm not sure exactly what to change in to make it work.

Can anyone point me in the right direction as to know for sure what boot loader is being used on this 7.2 machine? Remember, I don't have an anaconda-ks.cfg file to check as I have read in every other post. And can anyone tell me for sure what I would change the cmdline file to if that is indeed the problem?

Any help would be appreciated!

cPanel.net Support Ticket Number:

 

[Higgins]

Originally posted by Adz
I had the same problems as above, made the same steps to correct but on running lilo I get


[email protected] [~]# lilo
Added linux.too
Fatal: Kernel doesn't support initial RAM disks

Any ideas?

cPanel.net Support Ticket Number:

Im getting the same Error. An other Machine with the same old Kernel has been updated without any Problem. Only on these MAchine i have that Problem

cPanel.net Support Ticket Number:

 

[nitromax]

Hello,

Check the last post in this thread:

http://forums.cpanel.net/showthread.php?s=&threadid=13604


I started that thread, but then had to change NOC's and servers, so I never tried his suggestion. But that might have been it...

cPanel.net Support Ticket Number: