Grub 2 in Jaunty/Karmic can break double boot configuration

[Lucio M Nicolosi]

On Fri, Oct 2, 2009 at 10:30 PM, Lucio M Nicolosi <lmnicolosi at gmail.com> wrote:
>
> Later I decided to try grub2 in Jaunty. Although grub2 install found
> my kernels at (hd0,8) it defaulted them all to (hd0,0) (failed Karmic)
> and even the new (chainloaded) menu.lst defaulted to (hd0,0), UUID and
> all, and I found this last part weird. No working chainload means no
> easy recovery besides LiveCD, root edit menu.lst etc., not exactly a
> newbie dream.
>
> Lucio
>

Update:

Chainloaded of course refers to Grub2, once my parameter got messed I
missed up things, sorry.

To make it clear, Grub2 install on my Jaunty defaulted everything to
to hd0,0 and corresponding UUID and since Jaunty root, in my case,
resides on (hd0,8) it made the system unbootable.

Once the transitional menu.lst was corrected I was able to chainload
to grub2 and use it.

Once at grub2 boot screen I found out that my Karmic install was not
flawed at all and I could boot it.

This suggests it was the grub2 phase of Karmic install that went
wrong, probably twice.

The occurrence might be resumed as:

"Fresh Karmic Beta install may fail (grub2 phase) if there's a
previous grub version installed on another partition. - Observed on
Jaunty (hd0,8) - secondary == Karmic (hd0,0) - primary."

However, if Karl and others managed to install Karmic among an array
of older releases, this doesn't make sense, unless the choice of the
default partition was crucial (hd0,0).

Regards,

Lucio