grub update

Jonathan Berry berryja at gmail.com
Wed Apr 13 23:22:12 UTC 2005


On 4/13/05, jack wallen <jlwallen at monkeypantz.net> wrote:
> okay so i made the mistake earlier when i sent out the email saying it
> was all about /etc/grub instead of /boot/grub. okay well here's the real
> deal.
> 
> i have three kernels installed on FC3 (from up2date). there is a symlink
> in /etc/ to /boot/grub/grub.conf but there is no grub directory
> in /boot. the machine still boots but it's booting the older kernel
> (kernel-2.6.9-1.667). the other kernels on the machine are:
> 
> kernel-2.6.10-1.770_FC3
> kernel-2.6.11-1.14_FC3
> 
> the contents of /boot are:
> 
> config-2.6.10-1.770_FC3      System.map-2.6.10-1.770_FC3
> config-2.6.11-1.14_FC3       System.map-2.6.11-1.14_FC3
> initrd-2.6.10-1.770_FC3.img  vmlinuz-2.6.10-1.770_FC3
> initrd-2.6.11-1.14_FC3.img   vmlinuz-2.6.11-1.14_FC3
> 
> so how do i get grub back up and running so i can actually configure the
> machine to boot the new kernel instead of the old one?
> 
> thanks everyone
> 

I think your problem is that you have a boot partition, but that
partition is not getting mounted.  Notice that you are booting a
kernel that is not there!  So GRUB can find it, as well as itself, but
since it is not properly mounted (the /boot directory, that is) you
cannot see either.  Also, you cannot boot your new kernels because RPM
could not find the grub.conf when you updated your kernel.  I suggest
removing the newer kernels, mounting your /boot partition, and then
reinstalling the newer kernels.
What partitions do you have?  (run "fdisk -l" as root)  What is in
your /etc/fstab file?  I have seen someone else with this problem, I
wonder what causes a system to not mount the /boot partition after
install.  Perhaps fstab wasn't created properly?  Jack, how did you
initially partition your disk? (With Disk Druid, or fdisk?)

Jonathan




More information about the users mailing list