[Bug 1418706] Re: Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode install

Jason Gerard DeRose jason at system76.com
Mon Apr 20 16:37:22 UTC 2015


Just tested the "truly blank drive" scenario on the 20150417.1 daily:

http://cdimage.ubuntu.com/ubuntu/daily-live/20150417.1/

(sha1sum 0f1bdbc623df6816f1d058277811d8191408aeb9)

And it worked okay (although from others it sounds like things
definitely aren't fixed for all scenarios).

BTW, the reason I'm booting the ISO with init=/sbin/upstart is to work
around this bug:

https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1445587

-- 
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:
  Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
  install

Status in partman-auto package in Ubuntu:
  In Progress
Status in partman-efi package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress

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