Comment 90 for bug 576724

Revision history for this message
Erick Brunzell (lbsolost) wrote :

@ bcbc,

Regarding this:

"It also affects non-wubi installs, by replacing the grub bootloader with what it figures is the correct target, but it sometimes gets it wrong. In one case, the uuid was invalid. In another, it seemed to be pointing at the right partition (but bootinfoscript is not clear on this - it says 'partition #2 on the same drive' even when it's actually on a separate drive) so I suspect it was pointing at the wrong drive. In any case, reinstalling grub fixed the problem."

It might benefit you to read the interaction between me (kansasnoob) and 'seeker5528' here:

http://ubuntuforums.org/showthread.php?t=1516153

To wrap that in a nut shell I multi-boot a lot and I noticed that 'grub-pc' and/or 'grub-common' updates would now install "grub" wherever it was installed initially. So if I had my Maverick's bootloader in charge of boot but later installed something like Lubuntu 10.04, and handed boot off to it, while updating 'grub-pc' or 'grub-common' in Maverick it will install/reinstall grub wherever "dpkg" was originally told to install grub.

Did I say that in a way that makes sense? I hope so.

Regarding the Wubi thing I'm stuck here:

http://ubuntuforums.org/showthread.php?t=1539619

In other words I can't get past GO :^)