[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Caitlyn Martin
caitlynmmartin at gmail.com
Tue Nov 15 03:16:27 UTC 2016
OK, I've worked around the problem. First, I can confirm what vygotski
reported: it only happens if you are installing to a blank SSD. I
created my ESP (FAT32) partition first and made it larger (300 MB) and
the rest of my custom install worked after that. Not a huge problem but
it would be nice if it was at least documented somewhere.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-auto in Ubuntu.
https://bugs.launchpad.net/bugs/1418706
Title:
UEFI: blank drive incorrectly detected as existing BIOS-mode install
Status in partman-auto package in Ubuntu:
Triaged
Status in partman-efi package in Ubuntu:
Triaged
Status in ubiquity package in Ubuntu:
Triaged
Status in partman-auto package in Debian:
New
Bug description:
When doing a UEFI-mode install using the latest daily Vivid ISO (Thu
Feb 5), Ubiquity incorrectly concludes that a blank drive contains an
existing BIOS-mode install (see error in attached screenshot).
The resulting error dialog is also broken: none of the buttons do any
thing when clicked: X (close button), "Go Back", "Continue".
You can seemingly move the install forward by clicking "Continue" in
the main installer window, but things are still broken somewhere as
grub isn't getting correctly installed (system is unbootable after the
install completes).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1418706/+subscriptions
More information about the foundations-bugs
mailing list