[Bug 1786992] Re: Existing bios mode Windows install left unbootable after installing in EFI mode
Jean-Baptiste Lallement
jean-baptiste.lallement at ubuntu.com
Wed Apr 22 04:44:33 UTC 2020
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to os-prober in Ubuntu.
https://bugs.launchpad.net/bugs/1786992
Title:
Existing bios mode Windows install left unbootable after installing in
EFI mode
Status in os-prober package in Ubuntu:
Triaged
Status in partman-auto package in Ubuntu:
Triaged
Status in partman-efi package in Ubuntu:
Triaged
Status in ubiquity package in Ubuntu:
Triaged
Bug description:
Bugs #1668148 and #1766945 changed the installation process to install
grub-efi instead of grub-pc when the installer is booted in EFI mode
but the existing OS on the disk is in bios mode. Currently, this
renders the existing Windows or FreeDOS install unbootable. Windows
installs at least may be able to be salvaged by patching os-prober to
generate a grub.cfg that still has the windows bios mode chainloader
command when interpreted by grub-pc ( if the user tells their firmware
to boot in legacy mode ), or to chainload the windows EFI boot loader
when booting grub-efi. Normally os-prober looks for the windows
bootmgr in the ESP, but in the case of a bios mode install, a copy can
also be found in the windows\boot directory and at least in theory
should be loadable to boot Windows even though it was originally
installed in bios mode.
As things currently stand, this will be a major breakage for users in
18.10 and 18.04.1, so unless the changes to os-prober can be made in
time, the other two changes should be reverted and simply stick with
grub-pc in the case where the existing OS is in bios mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1786992/+subscriptions
More information about the foundations-bugs
mailing list