** Changed in: partman-auto (Ubuntu)
Milestone: ubuntu-15.04 => None
** Changed in: ubiquity (Ubuntu)
Status: In Progress => Confirmed
** Tags added: xenial
** Summary changed:
- Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode install
+ UEFI: blank drive
** Changed in: partman-auto (Ubuntu)
Status: Triaged => 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:
Vivid: UEFI: blank drive incorrectly detected as existing
I removed a Windows partition and some other partitions during the
install and when I clicked continue the Force UEFI Installation? box
came up and I was unable to move forward or backward with either
Continue or Go Back buttons.
Also, sorry, I think I accidentally changed the status of the
** Changed in: ubiquity (Ubuntu)
Status: Triaged => In Progress
--
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
Seeing thiis today in a MATE install (ISO date 20 April). UEFI install
with correct partitioning. Both third-party and updates optons were
*not* selected. "Debian in UEFI mode" displayed after partitioning and
on top "Where Are You?" panel. Does not respond to clicks.
--
You received this bug
So my earlier analysis on this bug was correct, as evidenced by the new
bug #1547286. The real underlying problem is still that the init.d
scripts are executing *after* the commit.d scripts have written the
partitions to the disk, and they are not intended to. Matthie's attempt
at fixing this
The bug happens if at the beginning of the installation you choose to
download updates while installing Ubuntu or if you select download third
party software for graphics and Wi-Fi hardware, Flash, Mp3 and other
media. Deselecting this dialog box allows the partition to occur without
problems.
--
I can reproduce this bug on Xenial Final Beta when installing to a 500Gb empty
intel ssd.
I get stuck in the dialogue which should not appear at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reproduce able on an Intel NUC trying to install to SSD via the M.2 slot.
Install from Ubuntu 15.10 Live CD installed to the SSD.
CRAZY this haven't been fixed yet. I'm not able to install at all. No matter
what I do to the UEFI / BIOS settings.
--
You received this bug notification because
If you're seeing this in Xenial I'd say it's a regression, so I'd file a
new bug report and mention there that it seems to be a regression to
this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this bug "open" or not? Not familiar with this bug tracker, but it
looks like it was declared fixed, but it either wasn't or there's a
regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unable to re-produce.
Laptop had latest install of Win 10 Pro '1511', and I was installing
'beta' Xerus.
Erased ALL drive partitions, and re-installed. Did NOT recur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue is present for current daily ISO for 16.04 LTS (Xenial
Xerus).
Will test further ..
--
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
After I got past that point, I also got an "Unable to install GRUB in
/dev/sda: Executing 'grub-install /dev/sda' failed. This is a fatal
error." Related? Not sure. Documentation on Ubuntu wiki on how to create
and install to a btrfs hasn't been updated since 12.04
--
You received this bug
Can also confirm this bug, or something similar is present in the latest
15.10 ISO downloaded from http://www.ubuntu.com/download/alternative-
downloads (torrent) as of 3/10/2016. I'm installing within a Gen 2
Hyper-V machine to a completely blank vhdx. Tried to create 3 partitions
for EFI boot,
Hi, I just hit that bug on the last ubuntu 15.10
I'll reboot and try your solution.
--
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
This occurred again today.
Aborted from 14.10 (fully updated) after 'prompt to upgrade to vivid',
which looked like it would take forever.
Restarted Notebook, to install 15.04 using USB of 'Ubuntu 15.04 Desktop
(64-bit)' (release).
When prompted with 'non-UEFI' mode warning, I choose 'back' and
Hi Colin, I thought the visual.d scripts present, *and manipulate* an in
memory view of partitions, which are later checked by check.d, and then
written to disk by commit.d. If it isn't visual.d, then what
manipulates the partitions? The problem seems to be that ubiquity is
running init.d -
To add to what Mathieu said, Phillip, please do NOT open a separate bug
about the allegation repeated several times earlier in this bug log that
visual.d scripts are creating partitions. They do not do this, as you
can see simply by inspecting those scripts for a few moments (they're
all very
Attempting to install Vivid (15.04) Daily Build, on HP Stream 11 (as
above). Device had earlier (failed) attempt to install 15.04 64-bit
present (standard auto-install: system, swap; but missing EFI), and
Secure-Boot mode is enabled.
http://cdimage.ubuntu.com/ubuntu/daily-live/pending/
Either option does nothing, and dialog is ignored by 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:
Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
Repeat of above, but with device has blank 32GB eMMC storage.
Chose to 'Erase disk and install Ubuntu', to create ESP, ext4, and swap
..
Appears to be installing ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
^
vivid-desktop-amd64.iso 21-Apr-2015 08:34
Ooops. Didn't noticed.
--
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
@david
You're using the latest April 21 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:
Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
install
To manage
Summary:
Install appears to complete, and prompts for reboot; (identical
behaviour as 14.10 install)
- reboot pauses, device still power-on but screen blank (no backlight); (often
occurs with 14.10 install, on HP Stream 11)
- then prompts to remove any install media, and press Enter ..
-
On next reboot, requires pressing Enter Enter to get through to
normal login.
--
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
I think we've established the most common cases for this are fixed; so
I'll close this as Fix Released -- ubiquity will properly handle blank
drives.
Fixes landed in:
- partman-auto: https://launchpad.net/ubuntu/+source/partman-auto/125ubuntu2
- ubiquity:
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
I tested my theory on today's daily image and it is true: creating a
single root partition with no esp still triggers broken dialog, so the
change to partman-auto is not a correct fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, and to absolutely avoid confusion:
$ sha1sum vivid-desktop-amd64.iso
e54c7cb9cc54613f44af84c7dce796a729b74c94 vivid-desktop-amd64.iso
:D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418706
Oh, and to potentially avoid confusion, when I said I tested the
16-Apr-2015 daily ISO, I'm going by the dates that Apache is showing
here:
http://cdimage.ubuntu.com/daily-live/current/
(Which for me at the moment is still 16-Apr-2015.)
--
You received this bug notification because you are a
@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
Mathieu, I think one thing you might check for that changing partman
doesn't fix is this: choose manual partitioning, create an ext4
filesystem for root, and nothing else. I believe you will then get this
pop up as it will see the one ext4 partition, and no ESP.
--
You received this bug
Attempting to install Vivid (15.04) Daily Build, on HP Stream 11 (Bay
Trail notebook, with 32GB eMMC storage). Device already has 14.10 64-bit
present (standard auto-install: EFI, system, swap), and Secure-Boot mode
is enabled.
http://cdimage.ubuntu.com/ubuntu/daily-live/pending/
@Paulo
No, have not seen that message during install.
Had it before though, when I tested iso files of before 17 April 2015.
Don't remember exactly of which dates those dailys were, however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Thomas
Do you still get the Force UEFI installation message?
https://launchpadlibrarian.net/196734906/Screenshot%20from%202015-02-05%2012%3A13%3A29.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Thomas
Thanks for confirming.
--
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
@Paulo
This may relate to @Thomas stating Installed in UEFI Mode, Secure boot
off.
I've seen a number of sites trying to install on various ultra-books and
tablets all say must disable secure boot. As this is a component of
proper use of UEFI (which should work), I have left it enabled.
--
You
My System: Dell XPS 13 (2015) (9343)
I had the same problem until now.
Today I tried to install again with desktop-amd64.iso of April 17, 2015.
This time it installed correctly and I could boot without any problems.
Installed in UEFI Mode, Secure boot off.
After one successful boot I enabled
I just did a UEFI-mode install in a kvm VM using the latest Vivid
desktop ISO (16-Apr-2015), and it worked!
I booted the ISO with init=/sbin/upstart to work around the installer
not being able to reboot after the install has finished, but otherwise
things worked perfectly!
--
You received this
I hope not, because it isn't fixed yet ..
The freeze was around 6 hours ago, and that build is nearly a day old.
( Here is Australia it is already mid-afternoon of Apr-17. )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Jason
Do you think the (16-Apr-2015) is already the RC?
Thanks
--
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
Or using the EFI partition (on USB flash), in place of creating EFI
partition on target ..
--
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
There is also an issue with installer creating the EFI partition on USB
flash device, instead of target platform.
This is NOT obvious when default settings are used.
Will need to do further tests, to see if this can still occur ..
--
You received this bug notification because you are a member
I don't think you quite understand the problem Mathieu. Yes, partman-
efi's init.d script sees the partition as ext3 instead of fat32 because
it has not yet been formatted as fat. The problem is that the init.d
scripts are supposed to have been run long before partman-auto creates
the new
In other words, the init.d scripts are supposed to be the first ones
run, so they can look at the state of the drive as it is when you first
boot the installer. Instead, ubiquity is running the visual.d scripts
first, so they decide to add an efi system partition, and then ubiquity
runs the
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
Partman-auto fix has been approved, but it will still need ubiquity to
include the changes.
partman-auto (125ubuntu2) vivid; urgency=medium
* Use fat32 rather than free as a filesystem type for the efi partitions
for amd64, arm64, i386; otherwise it's seen as an ext2 partition by
FYI, If you install with d-i instead of ubiquity, it does not run into
this problem since it runs the scripts in the correct order, so I don't
think it is appropriate to change partman-auto since that would change
the way d-i works, and it isn't broken.
--
You received this bug notification
Yup, I can confirm the above when it comes to the daily Vivid server
ISOs... I regularly test them for UEFI installs, and at no time since I
filed this bug have I encountered any problems when doing good ol' text-
based d-i server installs.
--
You received this bug notification because you are a
If you install in d-i mode, things still did work because it would be
running one instance of parted_server, as far as I could tell, to
complete all of its job. In ubiquity, parted is run multiple times,
which explains why scripts appear to be running out of order.
--
You received this bug
I'm not sure why you think they only appear to be running out of
order. If the partman log shows the visual.d script being run before
the init.d script, then it is. Stopping and restarting parted_server
wouldn't cause log entries from a script run later to be inserted
earlier in the log file.
@polochamps2004
I've tried that 'fix', but I get error message for 'grub-install'
command.
I need to manually create EFI partition as well ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418706
@david6
It may boot if you will follow the instructions here -
http://ubuntuforums.org/showthread.php?t=2268815
--
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
Which is copied from:
http://ubuntuforums.org/showthread.php?t=2223856p=13025073#post13025073
I will try it out ..
--
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
@david6
Yeah but without the last 2 commands if you would notice.
@Fred Palmer
If you're referring to my post
http://ubuntuforums.org/showthread.php?t=2268815 then the reason I
brought the ESP term is that I thought that it may help describe or it
is related with the bug.
Thanks for the info
It is my understanding that ESP is the correct full Initials (name) for
what we often just call the efi partition.
EFI System Partition (ESP)
Ubuntu installers have referred to the ESP by the name EFI boot partition,
But use of boot partition has confused new users thinking that is
Ubuntu's
Attempting to install Vivid (15.04) Daily Build, on HP Stream 11 (Bay
Trail notebook, with eMMC storage):
- Installed using USB drive, with UEFI-only image; (.ISO file 'restored' to USB
drive, no SysLinux or MBR)
- Installer incorrectly concludes that the drive contains an existing
BIOS-mode
For latest Vivid (daily build), it also suggests I have 'Secure Boot'
disabled, and it needs to force 'UEFI mode'.
This is part of the same issue, and also results in NO Grub being
installed (so wont boot). Live works fine.
--
You received this bug notification because you are a member of
If you choose not to download updates from the internet, it works
anyway.
--
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
Again I can confirm the bug still exist on the 02-Apr-2015 build.
Updates checked or not still displays the Force UEFI message.
ESP is still the term used on the boot partition instead of the usual
EFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@g-philip - in my testing, i've never chosen the download updates while
installing option, yet uefi mode installs haven't worked for me since i
originally filed this bug.
can you provide more details?
fyi, my testing has been done using a qemu/kvm virtual machine, but
others have confirmed this
Jep still present in Beta2. Installing to brand new SSD 850 EVO as in
Bug #1437255
--
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
I tried working around this bug by using GParted to manually create the
partitions needed, and ubi-partman dies in the Something else section
of the installer (exit code 141). Apparently ubi-partman hates the world
right now... :)
--
You received this bug notification because you are a member of
Still present on Beta 2.
--
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
** Changed in: ubiquity (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
I can confirm this bug.
http://ubuntuforums.org/showthread.php?t=2268815
--
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
I hadn't checked in on this for a bit... but for what it's worth, this
bug is still present in the latest daily ISO (02-Mar-2015).
--
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:
** Changed in: partman-efi
Status: Incomplete = 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:
Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
This bug is still present in the 18-Feb-2015 Vivid desktop amd64 daily
ISO, but I imagine the fix just hasn't made it into the daily yet.
--
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:
gotcha, thanks! i misunderstood the status change :)
--
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
It hasn't been fixed yet. The debian bug was closed as invalid since
Debian isn't affected. The bug watch updater is just broken and can't
tell the difference between fixed and invalid.
** No longer affects: partman-efi
** Changed in: partman-efi (Ubuntu)
Status: Triaged = Invalid
**
FYI, the problem seems to be that ubiquity is running things in parallel
and/or in the wrong order. Specifically, it is running the partman
visual.d scripts first, which add the new partitions, and then the
init.d scripts after, which detect the newly added partitions and thinks
they are existing
** Changed in: partman-efi
Status: New = Incomplete
--
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
So from what I can see, the underlying error message from partman-efi
happens any time there is NOT an existing EFI system partition on the
disk you are installing to, and ubiquity is broken because it displays
the error message and waits a few seconds, then proceeds to the next
screen, and if you
** Bug watch added: Debian Bug tracker #777647
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777647
** Also affects: partman-efi via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777647
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Same problem with the latest daily ISO (Tue Feb 10).
--
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
** Changed in: partman-efi
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:
Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode
install
I'm launching qemu with -cdrom vivid-desktop-amd64.iso. I just double-
checked from the try without installing live session, and the CDROM is
already showing up as /dev/sr0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Strange... the message itself comes from the underlying d-i component
partman-efi. The logic it uses to present the message is are there no
EFI system partitions, but there are any other existing partitions. I
wonder... there was some other flawed partition logic like this that was
triggering on
ah, gotcha, that makes sense. i did cross my mind that perhaps it was
looking at the wrong block device when deciding that an existing BIOS-
mode install was present.
for what it's worth, this is a very recent regression. I did a
successful UEFI-mode install using the Vivid daily ISO from about a
okay, latest daily is in a bit better shape: I still get this erroneous
warning dialog, but now clicking Continue on the dialog works, and the
install completes successfully (grub is installed correctly, system
boots fine).
--
You received this bug notification because you are a member of Ubuntu
er, scratch that... system isn't bootable. i ended up back in the live
ISO without noticing it :P
--
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
Well at least the ubiquity side is working then ;)
When you set up your virtual machine, are you configuring the iso as a
hd or cdrom? If it shows up as /dev/sr0 instead of /dev/sd[abc] then
I'll bet the warning goes away.
--
You received this bug notification because you are a member of
Okay, just double checked with `parted -l`... the target drive is
totally uninitialized:
Error: /dev/vda: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk: /dev/vda 17.2GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
--
You received this bug
Totally blank... I'm using qemu-img to create a new, empty virtual disk
before doing the install. So every sector should be 0x00 repeated.
I'm having trouble getting a terminal open to run parted. When I try
ubuntu without installed, i get some nautilus error and unity isn't
starting correctly.
When you say blank, do you mean has no partition table, or has a
partition table but no partitions? Can you show the output of parted
-l?
--
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:
I just tested the latest vivid *server* daily ISO in UEFI mode, and it
installs fine. So seems the problem is likely in Ubiquity, not in the
underlying debian installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
88 matches
Mail list logo
