I have had this issue for quite some time now.  Every time I update the
kernel my menu.lst root partitions are set incorrectly.  I have been
fixing them by hand every time and this morning I decided to figure out
what in the world is going on here.  After reading this post I think I
can see what my problem is.

This machine has been through numerous upgrades.  I think I started out
as Ubuntu Breezy Badger 5.10 and now I am Kubuntu 7.10.  If I remember
right this all started during the transition to UUIDs.

I think the problem might have something to do with an invalid groot
setting in my menu.lst file.

[EMAIL PROTECTED]:~# df /boot
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda4              6919068   4475280   2092368  69% /

but my groot is set as such;

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,1)

Now, when I tried to reboot after a kernel upgrade this is what I got;

title           Ubuntu 7.10, kernel 2.6.22-14-generic
root            (hd0,1)
kernel          /boot/vmlinuz-2.6.22-14-generic 
root=UUID=246246ac-7013-4b6a-be9a-8bb2bde3125b ro quiet splash
initrd          /boot/initrd.img-2.6.22-14-generic
savedefault

Which doesn't work at all.  What does work is this;

title           Ubuntu 7.10, kernel 2.6.22-14-generic
root            (hd0,3)
kernel          /boot/vmlinuz-2.6.22-14-generic 
root=UUID=246246ac-7013-4b6a-be9a-8bb2bde3125b ro quiet splash
initrd          /boot/initrd.img-2.6.22-14-generic
savedefault

So, my guess is that somewhere along the way I changed groot for some
reason and this has been biting me on every kernel upgrade since!

Anyway, thanks for the posts.  I will change my groot and see if that
doesn't work on the next kernel upgrade.  :)

After running an update-grub my menu.lst looks correct now that I have
the proper groot setting.  It even fixed the other entries I forgot to
change by hand.  :^O

Hopefully, this will help others out with the same issue.

-- 
Wrong boot hdx,x in menu.lst
https://bugs.launchpad.net/bugs/74486
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to