I did a clean FC4 install to the second disk (hdb) of my x86 machine. hda is Windows. During install, I requested grub be written to hda, and upon reboot, grub runs.
But grub can't find its config file, so it dumps me at a command prompt.
I can proceed normally by typing 'configfile /grub/grub.conf'. The menu pops up and I can boot both windows or linux just fine.
What can I do to make grub automatically find its config file in this most obvious of locations? :) Could there be a bug that I'm tickling, since the config file is on hdb instead of hda?
-Ed
Edwin Olson wrote:
I did a clean FC4 install to the second disk (hdb) of my x86 machine. hda is Windows. During install, I requested grub be written to hda, and upon reboot, grub runs.
But grub can't find its config file, so it dumps me at a command prompt.
I can proceed normally by typing 'configfile /grub/grub.conf'. The menu pops up and I can boot both windows or linux just fine.
What can I do to make grub automatically find its config file in this most obvious of locations? :) Could there be a bug that I'm tickling, since the config file is on hdb instead of hda?
-Ed
try /boot/grub/grub.conf. This is where the file resides, not where some strange ( non standard? ) link is. There's a standard symlink from /etc/grub.conf, but that's all I know about.
Steve
On Friday 17 June 2005 15:21, Steve Holdoway wrote:
Edwin Olson wrote:
I did a clean FC4 install to the second disk (hdb) of my x86 machine. hda is Windows. During install, I requested grub be written to hda, and upon reboot, grub runs.
But grub can't find its config file, so it dumps me at a command prompt.
I can proceed normally by typing 'configfile /grub/grub.conf'. The menu pops up and I can boot both windows or linux just fine.
What can I do to make grub automatically find its config file in this most obvious of locations? :) Could there be a bug that I'm tickling, since the config file is on hdb instead of hda?
-Ed
try /boot/grub/grub.conf. This is where the file resides, not where some strange ( non standard? ) link is. There's a standard symlink from /etc/grub.conf, but that's all I know about.
Steve
Hi Edwin: Did you set the location of boot as /dev/hdb? See below. If not, it's trying to find /boot on /dev/hda.
Tom
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda6 # initrd /initrd-version.img #boot=/dev/hda <<<<<<<<<<<<<<<<<<<<<<< change default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.11-1.1369_FC4smp) root (hd0,0) kernel /vmlinuz-2.6.11-1.1369_FC4smp ro root=LABEL=/ rhgb quiet
Thomas Taylor wrote:
On Friday 17 June 2005 15:21, Steve Holdoway wrote:
Edwin Olson wrote:
I did a clean FC4 install to the second disk (hdb) of my x86 machine. hda is Windows. During install, I requested grub be written to hda, and upon reboot, grub runs.
But grub can't find its config file, so it dumps me at a command prompt.
I can proceed normally by typing 'configfile /grub/grub.conf'. The menu pops up and I can boot both windows or linux just fine.
What can I do to make grub automatically find its config file in this most obvious of locations? :) Could there be a bug that I'm tickling, since the config file is on hdb instead of hda?
-Ed
try /boot/grub/grub.conf. This is where the file resides, not where some strange ( non standard? ) link is. There's a standard symlink from /etc/grub.conf, but that's all I know about.
Steve
Hi Edwin: Did you set the location of boot as /dev/hdb? See below. If not, it's trying to find /boot on /dev/hda.
Tom
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda6 # initrd /initrd-version.img #boot=/dev/hda <<<<<<<<<<<<<<<<<<<<<<< change default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.11-1.1369_FC4smp) root (hd0,0) kernel /vmlinuz-2.6.11-1.1369_FC4smp ro root=LABEL=/ rhgb quiet
Updating a commented out line is unlikely to make much of a difference (: I suggest pointing to root being on /dev/hdb as follows instead...
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
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
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
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
It looks like there is some confusion here. I believe the location of the grub.conf is coded into the boot sector. Perhaps there is something wrong with the script that installs grub?
In any event, it shouldn't hurt anything to re-install Grub running grub-install /dev/hda in a terminal (as root of course), you might even want to do a linux rescue from an old boot CD, just to eliminate the install grub script duplicating the problem.
Scott
On Fri, 2005-06-17 at 19:19 -0700, Scott Talbot wrote:
Edwin Olson wrote:
These are the contents of my grub.conf, as written during install... they already point to (hd1,0). Any other ideas? :)
...
It looks like there is some confusion here. I believe the locationof the grub.conf is coded into the boot sector. Perhaps there is something wrong with the script that installs grub?
In any event, it shouldn't hurt anything to re-install Grub runninggrub-install /dev/hda in a terminal (as root of course), you might even want to do a linux rescue from an old boot CD, just to eliminate the install grub script duplicating the problem.
Another way to avoid potential grub-install problems is to do it manually in grub at the prompt.
grub> root (hd1,0) grub> setup (hd0)
Check the output for any error messages.
Phil
P.S. This should be on "fedora-list" for FC4 release problems. Not a test problem.
grub> root (hd1,0) grub> setup (hd0)
After doing this as root, grub now finds its configuration file correctly (automatically), yay!
I'd guess that anaconda isn't doing quite the right thing when setting up grub. In fact, it appears to be this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159089
I've updated the bug report with the results of this thread. Thanks for the help!
-Ed
On Fri, 2005-06-17 at 17:26 -0700, Thomas Taylor wrote:
Hi Edwin: Did you set the location of boot as /dev/hdb? See below. If not, it's trying to find /boot on /dev/hda.
Tom
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda6 # initrd /initrd-version.img #boot=/dev/hda <<<<<<<<<<<<<<<<<<<<<<< change
This line will affect what gets passed to grub-install when you do a kernel upgrade; it won't affect what grub does while you're booting.
-
Edwin Olson -
Oldman -
Peter Jones -
Phil Schaffner -
Steve Holdoway -
Thomas Taylor