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

2018-06-14 Thread Phillip Susi
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. **

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

2018-05-28 Thread Niko Krause
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

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

2018-03-13 Thread David Klasinc
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:

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

2018-01-23 Thread Kenrin Xamithan
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

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

2017-11-18 Thread TJ
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

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

2017-08-19 Thread Gastón
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

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

2017-06-28 Thread Huan Zhang
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.

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

2017-05-18 Thread Mayou36
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

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

2017-04-11 Thread Ákos Laczkó
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

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

2017-03-14 Thread Richard at webbureau
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

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

2017-02-05 Thread Nicolas Peifer
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

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

2016-11-14 Thread Caitlyn Martin
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

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

2016-11-14 Thread Caitlyn Martin
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.

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

2016-08-26 Thread vygotski
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

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

2016-08-19 Thread Bug Watch Updater
** 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

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

2016-08-19 Thread Alberto Salvia Novella
** 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 **

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

2016-08-14 Thread Evan
** 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

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

2016-08-14 Thread Evan
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:

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

2016-07-29 Thread Alberto Salvia Novella
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 **

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

2016-07-29 Thread Alberto Salvia Novella
** 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

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

2016-07-21 Thread Evan
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

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

2016-07-12 Thread Martin Spacek
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

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

2016-07-12 Thread Martin Spacek
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