Hi Folks.

I had a situation a few days ago after running up2date on a RedHat ES 4 box where my machine wouldn't boot.

I got that fixed (sort of) but now I boot directly into a GRUB prompt rather than booting up "like normal."

I can boot once I'm to the GRUB prompt by doing:

root (hd0,0)
kernel /vmlinuz-2.6.9-78.0.13.EL ro root=/dev/md2 rhgb quiet
initrd /initrd-2.6.9-78.0.13.EL.img
boot

And then it does the normal "okay, booting the kernel" thing.

My /etc/grub/conf looks okay (just like what I manually enter into GRUB), as does the copy at /boot/grub/grub.conf and /boot/grub/menu.lst.

I am using software RAID 1 with two identical drives, if that matters.

Once the machine is "up" it behaves normally.

Surely there's some little setting somewhere that I can change from a "0" to a "1" so it doesn't make me interactively enter the kernel information every time I boot the machine.

If anyone has any ideas, I'd be happily open to them.

Thanks in advance!

G.--

It sounds like grub isn't finding your configuration files. I would try reinstalling grub.

Thanks! I was hesitant do reinstall grub because of the RAID 1 situation, but finally got up the nerve and now everything is back to normal.

Thanks again.

G.--

Thanks! I was hesitant do reinstall grub because of the RAID 1 situation, but finally got up the nerve and now everything is back to normal.

Thanks again.

G.--