I'd love to look for lupin-support, but yesterday, during another package
update, a new kernel got installed that somehow failed to update grub at
least that is my guess). This left me with the grub command line when
booting. That was the point where I gave up for now.
Anyway this might help.
In my case 2 partitions are involved. Windows is installed on a small
partition (i.e. "C:") and I installed Ubuntu on the large data partition
(i.e. "D:"). No RAID configuration since this is a simple laptop. Not sure
whether it matters, but there's also a recovery partition located in front
of the "C:" partition.
- Recovery (7.81 GB)
- OS_Install (43.95 GB)
- Data (414 GB)
Regards,
Alex
On Sun, Aug 15, 2010 at 5:51 AM, Jordan <email address hidden> wrote:
> Could you please check if the package "lupin-support" is installed?
> Running "apt-cache policy lupin-support" in a terminal will tell you.
>
> --
> Fresh wubi 10.04 install + package update can brick the system
> https://bugs.launchpad.net/bugs/609815
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Wubi, Windows Ubuntu Installer: Confirmed
> Status in Ubuntu: Invalid
>
> Bug description:
> Steps to reproduce:
> Install 10.04 (32-bit desktop edition) within Windows using Wubi.
> Boot Ubuntu and start a package update. This updates 'grub'.
> During the package install phase, 'grub' pops up a window that asks you
> whether or not to perform the update.
> If you do NOT choose to abort, but choose to let 'grub' update the system,
> it overwrites the windows master boot record.
>
> Result:
> This bricks the system since neither Windows or Linux boot (since both
> depend on the Windows bootloader).
> The solution is to use a recovery disk/stick to replace the MBR by a
> windows version again. This is not for everyone.
>
> So there are 2 problems here:
> - A newbie user can brick his system. Great way to popularize Linux.
> - 'grub' manages to ask difficult questions (to inexperienced users) during
> a routine package update.
>
> P.S. Sorry for the ad-hoc bug report. This needs analysis by someone who
> knows what he/she is talking about. Is this a grub, wubi or generic Ubuntu
> issue? The problem is real though.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/wubi/+bug/609815/+subscribe
>
Hi Jordan,
I'd love to look for lupin-support, but yesterday, during another package
update, a new kernel got installed that somehow failed to update grub at
least that is my guess). This left me with the grub command line when
booting. That was the point where I gave up for now.
Anyway this might help.
In my case 2 partitions are involved. Windows is installed on a small
partition (i.e. "C:") and I installed Ubuntu on the large data partition
(i.e. "D:"). No RAID configuration since this is a simple laptop. Not sure
whether it matters, but there's also a recovery partition located in front
of the "C:" partition.
- Recovery (7.81 GB)
- OS_Install (43.95 GB)
- Data (414 GB)
Regards,
Alex
On Sun, Aug 15, 2010 at 5:51 AM, Jordan <email address hidden> wrote:
> Could you please check if the package "lupin-support" is installed? /bugs.launchpad .net/bugs/ 609815 /bugs.launchpad .net/wubi/ +bug/609815/ +subscribe
> Running "apt-cache policy lupin-support" in a terminal will tell you.
>
> --
> Fresh wubi 10.04 install + package update can brick the system
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Wubi, Windows Ubuntu Installer: Confirmed
> Status in Ubuntu: Invalid
>
> Bug description:
> Steps to reproduce:
> Install 10.04 (32-bit desktop edition) within Windows using Wubi.
> Boot Ubuntu and start a package update. This updates 'grub'.
> During the package install phase, 'grub' pops up a window that asks you
> whether or not to perform the update.
> If you do NOT choose to abort, but choose to let 'grub' update the system,
> it overwrites the windows master boot record.
>
> Result:
> This bricks the system since neither Windows or Linux boot (since both
> depend on the Windows bootloader).
> The solution is to use a recovery disk/stick to replace the MBR by a
> windows version again. This is not for everyone.
>
> So there are 2 problems here:
> - A newbie user can brick his system. Great way to popularize Linux.
> - 'grub' manages to ask difficult questions (to inexperienced users) during
> a routine package update.
>
> P.S. Sorry for the ad-hoc bug report. This needs analysis by someone who
> knows what he/she is talking about. Is this a grub, wubi or generic Ubuntu
> issue? The problem is real though.
>
> To unsubscribe from this bug, go to:
> https:/
>