Thanks,

 I fixed it again.

 One month ago I did lock the grub in the System; I do not know what kind of
update I installed, so it rendered my Ubuntu unbootable ??

  Cheers,

  Alex




On Sat, Feb 5, 2011 at 8:50 PM, Erick Brunzell <email address hidden> wrote:

> @ Alex,
>
> Check out the Wubi megathread that bcbc linked to in post #38. There is
> a more "permanent" work-around there.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/610898
>
> Title:
>  grub-pc upgrade renders computer unbootable when Wubi is installed to
>  partition other than Windows
>
> Status in Release Notes for Ubuntu:
>  Invalid
> Status in Wubi, Windows Ubuntu Installer:
>  Triaged
> Status in “lupin” package in Ubuntu:
>  Triaged
> Status in “lupin” source package in Natty:
>   Triaged
>
> Bug description:
>  Users with wubi 10.04 are running the latest grub-pc updates, and it's
>  installing the grub2 bootloader to their drive MBR, rendering their
>  computers unbootable.
>
>  Users are reporting that the computer boots straight to a grub rescue
>  prompt, with the error 'no such device xxxxxxx'. They cannot boot
>  windows or access their system restore utilities. Grub2 is in the MBR
>  pointing to partition #256.
>
>  I first reported this on the #grub IRC channel, in the following bug
>  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/576724, and now
>  here as it's probably correct to create a new bug (an there's been no
>  response yet).
>
>  Here are the links to the ubuntuforums.org threads...
>  http://ubuntuforums.org/showthread.php?t=1538228
>  http://ubuntuforums.org/showthread.php?t=1537956
>  http://ubuntuforums.org/showthread.php?t=1538170
>  http://ubuntuforums.org/showthread.php?t=1482621 (this is an older
> thread, but a new user (softis) added to it and has the same issue).
>  http://ubuntuforums.org/showthread.php?t=1540744
>  http://ubuntuforums.org/showthread.php?t=1540772
>  http://ubuntuforums.org/showthread.php?t=1539672
>
>  I suspect, but cannot be certain, that it may be related to another
>  bug in the lupin-support overrides of grub, that fails to identify a
>  wubi installed ubuntu, when it has been installed to a partition other
>  than the main windows partition.
>  https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/604417
>
>  Although not conclusive, it seems that the most affected users
>  reported installing wubi to a partition other than windows.
>
>
>  =====================
>  FOLLOW UP: Aug 13 2010
>  =====================
>  I ran a new 10.04 wubi install on two computers. On the first wubi was
> installed on the same partition as windows. On the second it was installed
> on an external drive.
>
>  After installing, I booted wubi on both, connected to the internet and
> immediately downloaded all updates. When the grub-pc screen was presented, I
> clicked Forward (without checking the box) and then proceeded to select ALL
> devices presented to install grub.
>  On the WUBI on the same partition as Windows, this had no effect (verified
> with Bootinfoscript)
>  On the WUBI on a different partition than Windows, this installed grub to
> the MBR of both drives, with grub looking in partition #256.
>
>  ===========
>  CONFIRMED:
>  ===========
>  This only affects WUBI installs on a partition other than windows,
> therefore, is probably a duplicate of bug 604417.
>
>
>  Side note:
>  On both computers, Wubi would not start upon reboot after completion of
> updates. When I clicked on Ubuntu under the Windows Boot Manager, both
> computers rebooted. (This is totally unrelated to the MBR issue). To fix I
> had to boot each wubi install from a grub command line (from a direct ubuntu
> install),  and then run "sudo update-grub", after which I was able to boot
> normally into the wubi install using the Windows Boot Manager.  I'm not sure
> how a user with just wubi would do this!? Chroot from a live CD!?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/610898/+subscribe
>