installer failed to set boot flag on UEFI

[Lorens]

Hi,

I installed Ubuntu 14.10 but it wouldn't boot, it took several hours to get a working system. I've managed, but I'd just like to document this because I couldn't find any relevant writeups online and the problem seems so simple that I'm surprised it just didn't work out of the box.

I received a new Acer Aspire E1-572G, I took out the pre-installed Windows disk (after just checking that it booted OK) and replaced it with a blank SSD. I dd'd the 64-bit 14.10 to a USB key. I got the ISO last week from www.ubuntu.com, and most of the files on it are dated Oct 22.

After booting (with some difficulties detailed at http://ubuntuforums.org/showthread.php?t=2263270) I installed Ubuntu, entire disk encrypted LVM (it's a laptop after all), rebooted... and nothing: "No bootable device -- insert boot disk and press any key". I tried with UEFI instead of Legacy, and I get a different error message (text graphics reminiscent of linux kernel make menuconfig) but same meaning, nothing bootable found.

I booted the live USB to check that the disk looked OK (a half gig "Microsoft basic" partition, then a small 244MB linux partition, then the rest as a Linux partition. I followed the boot-repair doc on <https://help.ubuntu.com/community/Boot-Repair>, and I used default repair, no good. <http://paste.ubuntu.com/9959580>

The installer needed to put the bootable flag on the "Microsoft Basic" partition, and maybe change the type to EFI also. Now that I've done that, my laptop boots OK with Legacy or UEFI without secure boot (and with secure boot it finds the bootable partition and says that the security policy blocks it, which is better than totally ignoring it like it did before). I don't understand why the installer didn't do that, maybe a problem with choosing encrypted LVM?

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1416634

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Lawrence (2-bbuntu-j)]

ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lorens 2570 F.... pulseaudio
 /dev/snd/controlC0: lorens 2570 F.... pulseaudio
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=0d6cd42d-084c-47d7-8325-6de63566c9f2
InstallationDate: Installed on 2015-01-29 (1 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Acer Aspire E1-572G
Package: linux (not installed)
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-29-generic N/A
 linux-backports-modules-3.16.0-29-generic N/A
 linux-firmware 1.138.1
Tags: utopic
Uname: Linux 3.16.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/15/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HW
dmi.board.vendor: Acer
dmi.board.version: V2.14
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd01/15/2014:svnAcer:pnAspireE1-572G:pvrV2.14:rvnAcer:rnEA50_HW:rvrV2.14:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E1-572G
dmi.product.version: V2.14
dmi.sys.vendor: Acer

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lawrence (2-bbuntu-j)]

apport information

[Lorens (lorens-kockum)]

"Confirmed" seems to mean "confirmed by someone else than the bug reporter", which conflicts with the request in comment #1. Marking as Confirmed according to comment #1.

[Lorens (lorens-kockum)]

If this isn't really simple to find and correct, it may be important that I remember having restarted the install. Maybe the install doesn't set the flags immediately, and won't set them if it finds a previous partitioning?

[Phillip Susi (psusi)]

We will need the log files from a failed installation to proceed. Can you reproduce the problem and attach files in /var/log ( on the live cd, or they are copied to /var/log/installer on the hard disk )?

[Lawrence (2-bbuntu-j)]

here are the resulting installer logs

[Phillip Susi (psusi)]

According to your logs it was properly set up as an EFI system partition. Can you perhaps repeat the process and show the output of parted -l when it isn't correct?

[gordon (6a0ac33c)]

Not 100% certain that this is my exact bug. Tried both secure and normal ubuntu 14.10 installs on a new hd that has just had win8.1 installed. Normal install has some problems and then misses unbuntu and goes straight to windows. Secure install crashes before installation is complete. Cannot grab any files as only accessible file is this bug report screen - terminal not available. Ubuntu runs on other installed disks on system just not with this latest attempt.

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]