[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
I think you misunderstand the point of this bug Niko. You did not need to create a partition on the drive to get the prompt; a completely blank drive would cause it, and it was not supposed to. This prompt has been completely removed in 18.04 however, so I guess that closes this issue. ** Changed in: partman-auto (Ubuntu) Status: Triaged => Fix Released ** Changed in: partman-efi (Ubuntu) Status: Triaged => Fix Released ** Changed in: ubiquity (Ubuntu) Status: Triaged => Fix Released -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Had the same problem on a brand new empty SSd. The above suggested solution worked for me: > Formatting the ssd in gpt and creating one ext4 partition [with gparted] made the installer ask if I wanted to force UEFI ahead of the partitioning process. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
This is still present on 18.04 daily builds. I downloaded it just today and I can't get past the 'Force UEFI installation?' dialog. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Just ran into this bug on 17.10. Can confirm if you let the installer partition for you then re-install afterwards with manual partitions it works. Partitioning manually before installation does NOT work and still stuck on force UEFI message. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Still affects 17.10; confirmed in a VM and on bare metal -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Can confirm. Same UEFI error with hanged install due to unresponsive dialogue window. - Ubuntu Gnome 17.04 - Brand new blank SSD I was able to complete the install with the workaround described in: > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1418706/comments/90 > I chose the first (default) installation option and let it create the > partions. I aborted and rebooted when I had to select the timezone. Then I > chose the manual partion mode and deleted all but the efi partion and created > my partions For the second (real) install I used: - encrypt - use lvm - something else In my case this is the efi partition I got from the first (fake) install: - efi ~536 MB I created two ext4 partitions for / and /home respectively; then selected "encrypt home folder". Mentioning it for thoroughness. At all times, during the default (fake) install and the manual (real) install I had: - Ethernet connected - check for upgrades - install 3rd party --- To be able to boot I had to go once more into the BIOS and enable the new UEFI SSD entry in the boot order list. That isn't related to the bug. It is more specific to my motherboard and chosen security settings. Still worth to mention. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
This problem still occurs in Ubuntu 17.04 installer.
If internet is connected before installation and using a blank disk, the "Force
UEFI installation" box will pop up after a manual partition. The buttons ("Go
Back" and "Continue") on the box do not work, and installation gets stuck here.
Reproducible on multiple machines. Have to disconnect Internet before running
the installer.
--
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:
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
This problem is still around in 17.04! Really? -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
I've experienced this problem as well on Ubuntu MATE 16.04.2 LTS, but managed to resolve it. This issue seems to be related somehow to the existing partition table of the drive: even after manually creating a new GPT table in gparted (or KDE partition manager) I got stuck at this message, but if I created a new partition table for the blank drive inside "something else" the message did not show up (dispite the fact that it also creates a GPT table if I'm correct). I assume that's why the default install method worked for everybody here - this step must be included in that one as well. Reproduced this three times (error and resolution as well). Hope this helps somehow to the devs. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
I encountered the same problem (first using Ubuntu 16.04.1, and then 16.04.2), but only on one of the three pc's I just built. The only differences between the one which showed the bug and the others, was that I used another motherboard in the one with the problematic install, and another brand of DDR4 Ram (same amoount of memory). All other components (120 GiB SSD, Intel I3 processor, socket 1151) were exactly the same and brand new. I used these two motherboards and memory: ASUS H170-PRO (problematic install), and ASUS H170M-PLUS (no problems). Given that these two motherboards are likely almost the same, this given might help in solving the problem... I worked around the problem by choosing the first installation option instead of 'something else'. Hope this gives someone an idea about the source of the problem... Differences between the motherboards according to Asus and setup utility: H170M-Plus: microATX, Gigabit ethernet: Intel I219-V, No ordinary PCI slots, BIOS: 2002 x64; Build date: 09/20/2016; (ME FW version: 11.0.10.1002). H170 PRO: ATX, Gigabit ethernet: Realtek 811H, 2 ordinary PCI slots, BIOS: 2003 x64; Build date: 09/19/2016; (ME FW version: 11.0.10.1002). -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Yeah, it happens when you have a brand new SSD and try to create the partions manually - it won't work. My workaround: I chose the first (default) installation option and let it create the partions. I aborted and rebooted when I had to select the timezone. Then I chose the manual partion mode and deleted all but the efi partion and created my partions - no strange pop-up :-) -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418706 Title: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
The problem still exists in Yakkety. I am doing an install on an HP x2 Detachable 10-p010nr (the latest version). I attempted to basically wipe the SSD and do a custom install so that I could have multiple partitions. I got stuck at Force UEFI installation? and couldn't go back or continue. Please note that I am using the Ubuntu GNOME iso with the patched kernel for Intel Cherry Trail SOCs at: https://linuxiumcomau.blogspot.com/2016/10/running-ubuntu-on-intel-bay- trail-and.html I realize this is not an officially supported OS image. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
For me, the error only occurred when I was installing from an empty ssd. Formatting the ssd in gpt and creating one ext4 partition made the installer ask if I wanted to force UEFI ahead of the partitioning process. After that the installation works as usual. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
** Changed in: partman-auto (Debian) Status: Unknown => New -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
** Also affects: partman-auto (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834373 Importance: Unknown Status: Unknown ** Changed in: partman-auto (Ubuntu) Status: Confirmed => Triaged ** Changed in: partman-efi (Ubuntu) Status: Confirmed => Triaged ** Changed in: partman-efi (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Triaged -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
** Changed in: partman-efi (Ubuntu) Status: Invalid => Confirmed -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Hi Alberto, I have filed a report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834373 ** Bug watch added: Debian Bug tracker #834373 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834373 ** Changed in: partman-auto (Ubuntu) Status: Incomplete => Confirmed ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Confirmed -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Please: 1. Report to (http://bugs.debian.org/). 2. Paste the new report link here. 3. Set this bug status back to "confirmed". Thank you. ** Changed in: partman-auto (Ubuntu) Status: Confirmed => Incomplete ** Changed in: ubiquity (Ubuntu) Status: Triaged => Incomplete ** Changed in: partman-efi (Ubuntu) Importance: High => Critical -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
** Changed in: ubiquity (Ubuntu) Status: Confirmed => Triaged -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Still present in public release of Ubuntu MATE 16.04, and presumably other Ubuntu versions as well. What do we need to do to help this get fixed? This is, as Martin says, infuriating. It completely blocks you from installing Ubuntu in Hyper-V to a blank VHDX using EFI boot. I tried the steps Martin posted, and I was able to get past that screen. Indeed, if you just select "EFI System Partition", it formats it as ext4, with no option available. Yet if you consult here the EFI spec v2.5, section 12.3, it states that "The file system supported by the Extensible Firmware Interface is based on the FAT file system," so ext4 would be inappropriate. Source: http://www.uefi.org/sites/default/files/resources/UEFI%202_5.pdf#page=536 Unfortunately, I later ran into problems installing GRUB2 and the process failed, so there is still something else to debug. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Sorry, I forgot to mention above that I selected both "download updates while installing Ubuntu" and "download third party software for graphics and Wi-Fi hardware, Flash, Mp3 and other media." -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
This is an infuriating bug, but I've found a workaround, more or less described in a comment in a duplicate bug here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1547286/comments/11 I'm installing Xubuntu 16.04 amd64 on a completely blank SSD on a brand new UEFI-enabled HP system. If I immediately create an EFI partition (say 200 MB) before the main partition, that doesn't fix the bug. I still get the broken "Force UEFI installation" dialog in the next step. This is because, for some strange reason, the installer decides to set the EFI partition to ext4 instead of FAT32. You can see this in the space allocation graphic at the top of the manual partitioning dialog. So, instead of directly creating an EFI partition (during which you can't specify the file system type), I created a 200 MB FAT32 partition, then changed it to EFI with the "change..." button, and voila, I now have a FAT32 EFI partition. After allocating my root partition and hitting next, I no longer get the broken "Force UEFI installation" dialog, and installation proceeds smoothly. -- 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: 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
