This is irritating: I've got a server I just upgraded to 5.4, then
rebooted, only to discover that it just *sits* there at the grub boot
menu. I looked at grub.conf, and uncommented hiddenmenu (which should have
been done long ago).
It *still* sits there when I reboot. Any clues, folks?
mark
grub.conf:
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-164.2.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-164.2.1.el5 ro root=LABEL=/ rhgb
initrd /initrd-2.6.18-164.2.1.el5.img
title CentOS (2.6.18-164.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-164.el5 ro root=LABEL=/ rhgb
initrd /initrd-2.6.18-164.el5.img
<snip>
On Wed, 28 Oct 2009, m.roth at 5-cent.us wrote:> This is irritating: I've got a server I just upgraded to 5.4, then > rebooted, only to discover that it just *sits* there at the grub boot > menu. I looked at grub.conf, and uncommented hiddenmenu (which should have > been done long ago). > > It *still* sits there when I reboot. Any clues, folks? > > mark > > grub.conf: > #boot=/dev/sda > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (2.6.18-164.2.1.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-164.2.1.el5 ro root=LABEL=/ rhgb > initrd /initrd-2.6.18-164.2.1.el5.img > title CentOS (2.6.18-164.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-164.el5 ro root=LABEL=/ rhgb > initrd /initrd-2.6.18-164.el5.img > <snip>Try labelling root as the actual drive, not using the LABEL as above. In other words, something like this: root=/dev/VolGroup00/LogVol00 rhgb quiet Otherwise, your grub.conf is exactly like mine, and it works without issue here. ******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
m.roth at 5-cent.us wrote:> This is irritating: I've got a server I just upgraded to 5.4, then > rebooted, only to discover that it just *sits* there at the grub boot > menu. I looked at grub.conf, and uncommented hiddenmenu (which should have > been done long ago). > > It *still* sits there when I reboot. Any clues, folks?Anyone sitting at the keyboard holding a key down? I ran into a really annoying bug in the latest Dell DRAC cards for example which caused the management card to spew crap onto the console causing the grub boot loader to hang at the menu screen(as if someone hit a key to cancel the timeout). Lots of other side effects to that bug as well(on a couple of occasions would have almost everything get zombied out until I rebooted the management card which cleared it up). nate
On Wednesday 28 October 2009 15:47, m.roth at 5-cent.us wrote:> This is irritating: I've got a server I just upgraded to 5.4, then > rebooted, only to discover that it just *sits* there at the grub boot > menu. I looked at grub.conf, and uncommented hiddenmenu (which should have > been done long ago). > > It *still* sits there when I reboot. Any clues, folks? > > mark > > grub.conf: > #boot=/dev/sda > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (2.6.18-164.2.1.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-164.2.1.el5 ro root=LABEL=/ rhgb > initrd /initrd-2.6.18-164.2.1.el5.img > title CentOS (2.6.18-164.el5) > root (hd0,0) > kernel /vmlinuz-2.6.18-164.el5 ro root=LABEL=/ rhgb > initrd /initrd-2.6.18-164.el5.img > <snip> > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centosLooks OK. Can you boot this system at all? Have you tried to boot yhe old kernel, maybe there is an issue with the new one? If you cannot boot ayt all try a live CD and check the log files for a clue. -- Regards Robert Linux User #296285 http://counter.li.org
m.roth at 5-cent.us <m.roth at 5-cent.us> wrote:> This is irritating: I've got a server I just upgraded to 5.4, then > rebooted, only to discover that it just *sits* there at the grub boot > menu. I looked at grub.conf, and uncommented hiddenmenu (which should have > been done long ago).I just saw something similar happen on a server when I was upgrading it to kernel 2.6.18-164.2.1.el5xen. In this case, however, it didn't get to the grub prompt but rather only got as far as printing "GRUB" and nothing else. This was on a machine that was originally CentOS 5.3 and was previously upgraded to 5.4. In this case, I had mirrored OS disks so I was able get into the BIOS, and boot from the second disk (which had been previously been set up with a redundant boot block). I then reinitialized the boot block on the first disk (and is the default boot device). If I didn't have mirrored disks, I would have booted the DVD in rescue mode. Both the initial grub setup and the reinit were done according to the info available at <http://grub.enbug.org/MirroringRAID>. Hopefully that helps. Devin -- UNIX is very simple, but it takes a genius to understand the simplicity. - Dennis Ritchie