I've been looking into this last night and this morning; fix for
partman-auto is now in the queue for review by archive admins.
Looks like this was because efi recipes used "free" rather than
explicitly setting the partition filesystem type to "fat32" or some
value of FAT as per the UEFI spec; so for some reason this showed up as
ext3 until the partition was properly formatted, which would have
happened *after* the extra uefi warning, if it wasn't breaking things in
other ways.
I'm splitting this into a separate bug for the Force UEFI warning which
appears to be handled incorrectly and is worded in a confusing manner.
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Invalid
** Changed in: ubiquity (Ubuntu)
Milestone: ubuntu-15.04 => None
** Also affects: partman-auto (Ubuntu)
Importance: Undecided
Status: New
** Changed in: partman-auto (Ubuntu)
Status: New => In Progress
** Changed in: partman-auto (Ubuntu)
Importance: Undecided => Critical
** Changed in: partman-auto (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: partman-auto (Ubuntu)
Milestone: None => ubuntu-15.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418706
Title:
Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1418706/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
