Screwed Up My grub.conf Somehow <Solved>

[forbin]

When I boot my machine, it stops at a grub> prompt.

If I enter...

grub> find /v (and press TAB to autocomplete it)

Then it displays...

grub> find /var/

So evidently it thinks /dev/sda1 -- also called hd(0,0) -- is the place to boot from, since that is where the / filesystem is mounted.

The /boot filesystem is actually mounted on /dev/sda3, so I can get the system to boot by entering...

grub> root (hd0,2)
grub> kernel /xen.gz-2.6.18-8.el5
grub> module /vmlinuz-2.6.18-9.el5xen ro root=LABEL=/ rhbg quiet
grub> module /initrd-2.6.18-8.el5xen.img
grub> boot

After which the system comes up fine. But if I reboot, it stops at the grub> prompt again.

Any ideas?

My complete grub.conf looks like this:

default=0
timeout=1
splashimage=(hd0,2)/grub/splash.xpm.gz
title RedHat (2.6.18-8.el5xen)

root (hd0,2)
kernel /xen.gz-2.6.18-8.el5
module /vmlinuz-2.6.18-9.el5xen ro root=LABEL=/ rhbg quiet
module /initrd-2.6.18-8.el5xen.img

Here's fdisk...

[root@hurley ~]# fdisk -l

Disk /dev/sda: 1497.1 GB, 1497198755840 bytes
255 heads, 63 sectors/track, 182024 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 19122 153597433+ 83 Linux
/dev/sda2 19123 21162 16386300 82 Linux swap / Solaris
/dev/sda3 * 21163 21191 232942+ 83 Linux

And here's parted...

[root@hurley ~]# parted
GNU Parted 1.8.1
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all

Model: DELL PERC 5/i (scsi)
Disk /dev/sda: 1497GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 32.3kB 157GB 157GB primary ext3
2 157GB 174GB 16.8GB primary linux-swap
3 174GB 174GB 239MB primary ext3 boot


Error: Unable to open /dev/md0 - unrecognised disk label.

[forbin]

Well, crap. Never mind. Right after I posted this question, I found the solution in another thread. I ran...

# /sbin/grub-install /dev/sda --recheck

..and even though it said there were no errors detected, it fixed the problem. Go figure.

[pwalden]

I have had a successful F9 instance for several months, then suddenly this "stops at GRUB" problem occurs. I cannot remember if it was immediately after a yum update or not, as I routinely do yum updates, almost every day.

I tried the above grub-install process. But the script wanted a /sbin/grub. I created a soft link from /usr/sbin/grub to /sbin/grub. However, I now get a a the following

# grub-install --recheck /dev/sda
Probing devices to guess BIOS drives. This may take a long time.
Could not find a device for
#

What can I do now?