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

[Jason Gerard DeRose]

@Paulo: no, I didn't think that ISO was the RC, I was just checking in
on the latest daily.

In case booting with Upstart was the variable, I just tested with
systemd (with the same daily ISO), and this EFI partitioning bug (in
terms of my original scenario) seems to be fixed. Although in the
systemd case, I can't really confirm this nicely as I can't reboot the
VM after the install finishes (my tooling uses the plain-jane KVM Gtk
window, doesn't provide UI to force a reset). All I know for sure is
that I'm at least not getting the original error message dialog when
booting with systemd, which I was still getting with the ISO from the
day before.

Grub may or not be getting installed correctly when booting with
systemd. For what it's worth, when I tried to boot from this virtual
disk after killing my kvm process, it didn't work, but there are many
reason why this could happen as pulling the (virtual) plug in this way
could easily leave the vm disk file in an inconsistent state. Or I could
have just made a goof.

But when I tested earlier booting the ISO with Upstart, things
definitely worked correctly. Grub was installed correctly and I could
reboot into Ubuntu after the installation completed.

If this isn't the case for everyone in their specific scenario, keep in
mind that I'm testing with:

1) A truly "blank" target drive (a freshly created qcow2 disk image
containing the byte 0x00 repeated)

2) An OEM-mode install these last to times around (although previously
I've tested normal installs, just in case this bug was specific to OEM-
mode, and found no difference)

Plus, to get things fully working without a hard-reset, I booted the ISO
with init=/sbin/upstart :D

Thanks!

-- 
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