Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
• application/x mplayer2 plugin
• RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
• Command stream end of file while reading
• X Windows problem (xauth)
• Upgrading openoffice 1 1 rpm
• FTP: connection refused
• FTP: connection refused
• mount: /dev/cdrom: is not a valid block device
• Dell Precision 650, RedHat 9, no sound
• how to trace the cause resulting in the crash of bind server
• Virus on the list
• UNINSTALL RPM MYSQL
• usb pen drives: mounting as a user
• broadcom network interface
• make mrproper
• sendmail configuration on redhat
• Couldn 't open PID file /var/run/named/named pid Permission denied
• Promise 378 controller
• kernel 2 6 and /dev/sound/mixer not found
• Problem using up2date
• mrtg step by step howto/configuration for a newbie?
• Compiling and Installing Kernel 2 6
• Can 't locate module ppp0, can 't locate module ppp compress 21
• HOW I CAN MAKE BOOTABLE FLOPPY DISKET
• Lotus Notes under Wine
• /etc/security/limits conf question
• Intel E/1000 driver
• Command stream end of file while reading
• rpm database corrupt
• qla2300 modules
 
System Refuses to auto-boot from grub-specified default

System Refuses to auto-boot from grub-specified default

2006-02-03       - By Tim Evans

 Back
Reply:     1     2     3     4  

System is Red Hat Enterprise Linux WS release 3 (Taroon Update 6)

On installation of kernel updates, the system always refuses to boot from the
new, default kernel specified in /boot/grub/grub.conf.  It always boots from
the
last prior kernel.

More details:

In addition, up2date, on installing the last kernel release, showed the
following error message (referencing lilo, even though lilo is not the active
boot manager):

Modifying bootloader config to include the new kernel info
Adding 2.4.21-37.0.1.EL to bootloader config
Adding 2.4.21-37.0.1.EL to bootloader config
Adding 2.4.21-37.0.1.ELsmp to bootloader config
Running lilo with the new configuration
Running "/sbin/mkinitrd --ifneeded /boot/initrd-2 (See http://trd-2.ora-code.com).4.21-37.0.1.EL.img
2.4.21-37.0.1.EL"
/boot/initrd-2 (See http://trd-2.ora-code.com).4.21-37.0.1.EL.img was created
Running "/sbin/mkinitrd --ifneeded /boot/initrd-2 (See http://trd-2.ora-code.com).4.21-37.0.1.EL.img
2.4.21-37.0.1.EL"
/boot/initrd-2 (See http://trd-2.ora-code.com).4.21-37.0.1.EL.img was created
Running "/sbin/mkinitrd --ifneeded /boot/initrd-2 (See http://trd-2.ora-code.com).4.21-37.0.1.ELsmp.img
2.4.21-37.0.1.ELsmp"
/boot/initrd-2 (See http://trd-2.ora-code.com).4.21-37.0.1.ELsmp.img was created
making a backup copy of /etc/lilo.conf as
/etc/lilo.conf.up2date-1138553642 (See http://ate-1138553642.ora-code.com).379946
writing out the new /etc/lilo.conf
Running " /sbin/lilo -t -r /"  (lilo test mode)
restoring the backup file /etc/lilo.conf.up2date-1138553642 (See http://ate-1138553642.ora-code.com).379946 to
/etc/lilo.conf
Error installing lilo.conf  The message was: test install of lilo failed

The only way to get it to boot the current kernel, which again is specified as
the default in grub.conf, is to manually select it at boot time from the menu.  
As I manage the system remotely, this creates a problem, and I have to find
someone on site to ensure the correct kernel boots.

--
Tim Evans, TKEvans.com, Inc.   |    5 Chestnut Court
tkevans@(protected)     |    Owings Mills, MD 21117
http://www.tkevans.com/     |    443-394-3864
http://www.come-here.com/News/   |    

--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list