Wrong changes in grub menu.lst after system update (dual boot configuration)

[Erik Rosenlund]

I am using Ubuntu 7.10 with a dual boot setup which is corrupted after some system updates, latest on February 18, where I introduced the last 8 to 10 updates.

Presently I am using a “levorno T60” but I have used the same configuration on other computers with the same problem. As external boot and manual correction of menu.lst is needed after such update, the configuration is only useful for more advanced users.

The configuration use two separate HD
1. Original HD with Windows complete unchanged by the Ubuntu installation. Boot on this disk starts Windows normally.
2. Extra HD in device bay with Ubuntu. Boot on this disk starts grub for dual boot, Windows or Linux may be started.

The main benefit of the configuration is dual boot with a complete unchanged Windows disk.

The correct working menu.lst contain:

title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=93d08c48-a882-4619-b61c-1348a1e1e4cd ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet

title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=93d08c48-a882-4619-b61c-1348a1e1e4cd ro single
initrd /boot/initrd.img-2.6.22-14-generic

title Ubuntu 7.10, memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
root (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
savedefault
chainloader +1

Is after the update changed to:

title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd1,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=93d08c48-a882-4619-b61c-1348a1e1e4cd ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet

title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd1,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=93d08c48-a882-4619-b61c-1348a1e1e4cd ro single
initrd /boot/initrd.img-2.6.22-14-generic

title Ubuntu 7.10, memtest86+
root (hd1,2)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
root (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
savedefault
chainloader +1

The changed HD1 must manual be changed back to HD0 before boot of linux on the HD again is possible.

I hope this input may inspire some change to further improvement of the Ubuntu system. Anyhow thank you for a good and stable system.

Kind regards

Erik Rosenlund

[Michael Doube (michael-doube)]

Hi Erik

I have a similar problem with a triple-boot scenario. I'll mark it as a duplicate and hopefully we'll get better support for dual (and more) boot installation scenarios.

Mike

[Erik Rosenlund (er-lug)]

Hi Mike

Are you sure the duplicate note is correct?

In https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/10824 windows is not detected correct, during installation.
I experienced something similar after installation and I edited meu.lst to get the dual boot working for windows.

Hovever the problem I reported in https://bugs.launchpad.net/ubuntu/+bug/197687, occur after some system updates where the existing (and working) menu.lst has been modified so grub no longer can boot linux, however windows can is still be booted from grub.

The update procedure has changed the linux disk from hd0 to hd1 in menu.lst. (the only change I have recognised!).

The PC must then be booted from a CD and
The changed HD1 must manual be changed back to HD0 before boot of linux on the HD again is possible.

Erik

[Michael Doube (michael-doube)]

Hi Erik

I duped it because the first error you note (having to manually hack
menu.lst after a fresh install) is the main part of the problem and I
think there's a broader problem with grub configuration consistency.
I can see that the second problem is different to the first one (that
grub hasn't carried over your modded configuration) but perhaps we
should go back to the fact that you had to modify the config in the
first place? Feel free to un-duplicate, just trying to pull together
all the grub installation config bugs I can cos it's really annoying
that I have to rewrite menu.lst everytime I test the Hardy
installer...

Cheers

Mike

On 02/03/2008, Erik Rosenlund <email address hidden> wrote:
> *** This bug is a duplicate of bug 10824 ***
> https://bugs.launchpad.net/bugs/10824
>
> Hi Mike
>
> Are you sure the duplicate note is correct?
>
> In https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/10824 windows is not detected correct, during installation.
> I experienced something similar after installation and I edited meu.lst to get the dual boot working for windows.
>
> Hovever the problem I reported in
> https://bugs.launchpad.net/ubuntu/+bug/197687, occur after some system
> updates where the existing (and working) menu.lst has been modified so
> grub no longer can boot linux, however windows can is still be booted
> from grub.
>
> The update procedure has changed the linux disk from hd0 to hd1 in
> menu.lst. (the only change I have recognised!).
>
> The PC must then be booted from a CD and
> The changed HD1 must manual be changed back to HD0 before boot of linux on the HD again is possible.
>
> Erik
>
>
> --
> Wrong changes in grub menu.lst after system update (dual boot configuration)
> https://bugs.launchpad.net/bugs/197687
> You received this bug notification because you are a direct subscriber
> of the bug.
>