Edwin Olson wrote:
These are the contents of my grub.conf, as written during install...
they already point to (hd1,0). Any other ideas? :)
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img #boot=/dev/hda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro
root=/dev/VolGroup00/LogVol00 video=vesa vga=793
initrd /initrd-2.6.11-1.1369_FC4.img
title Windows rootnoverify (hd0,0)
chainloader +1
Steve Holdoway wrote:
Steve Holdoway wrote:
[snip]
title Fedora Core (2.6.11-1.1369_FC4smp)
root (hd0,1) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
kernel /vmlinuz-2.6.11-1.1369_FC4smp ro root=LABEL=/ rhgb quiet
Steve
Oops, make that root (hd1,0) will you (:
Cheers,
Steve
1. Do you have the option to boot either to windows or linux - ie is
this file being used?
2. Does the stock initrd image contain all the modules necessary to boot
lvm?
If 1 is yes, then the problem is with the kernel/initrd resources
available at boot.
Steve