It is possible that this happened by the fault of myself. While I first
installed grub2 on this lucid alpha-mashine the upgrade-manager asked me
on what disks and partitions the boot-manager is going to be installed.
So I guess that I selected all ones and by that overrote the MBRs of the
two partitions. I dont have the disks left to boot them in recovery
console and fixmbr, so i cannot check it and eventually get them back.
Do you know any workarounds for that? Drives, partitions and data are
still healthy and accessible.
Why whould grub2 upgrade gives you the possibility to screw your "ms
windows" so easily? I dont see a need in explicitly allow it installing
on ms-partitions. The maximum allowed compliance should be limited to
install it on just the drive.
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => criticalmess (criticalmess)
** Changed in: grub2 (Ubuntu)
Assignee: criticalmess (criticalmess) => (unassigned)
--
Booting WindowsXp/Xp-X64 out of Grub2 just echos "GRUB _" blinking cursor
https://bugs.launchpad.net/bugs/518330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
