Following install GRUB menu does not appear on startup

[Tony Pursell]

Ubuntu was installed on a new Lenovo E50-00 desktop PC using a USB stick alongside Windows 8.1. The installer was used to create a data partition for Ubuntu. First install failed with the install hanging while 'completely removing xfsprogs'. The install was rerun using the data partition created on the first run and completed successfully.

What I expected to happen: The GRUB menu appears on start up.

What does happen: The GRUB menu does not immediately appear on start up. It is necessary to use F12 on start up to call up the machine's boot menu and select 'ubuntu' (see attached screenshot). The GRUB menu then appears from which Ubuntu can be booted.

The USB stick for the install was booted in EFI mode. The installation is EFI and the version of GRUB in use is grub-efi.

There is a partition (sda3) named LRS_ESP which contains folders 'EFI' and 'onekey'. The folder 'EFI' contains only a folder 'Microsoft'.

There is a folder /boot/efi/EFI that contains folders 'Boot', 'Microsoft' and 'ubuntu'.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jun 26 17:17:45 2015
InstallationDate: Installed on 2015-06-21 (5 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Tony Pursell (ajpursell)]

/var/log/installer/syslog

[Tony Pursell (ajpursell)]

/var/log/installer/partman

[Tony Pursell (ajpursell)]

F12 boot menu

[Tony Pursell (ajpursell)]

GRUB menu

[Phillip Susi (psusi)]

Please provide the output of efibootmgr -v and findmnt.

[Tony Pursell (ajpursell)]

efibootmgr -v

BootCurrent: 0004
Timeout: 6 seconds
BootOrder: 0000,0004,0008,0003,0002,0001
Boot0000* Windows Boot Manager HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0002* UEFI: IPV6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO
Boot0003* UEFI: IPV4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)..BO
Boot0004* ubuntu HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\ubuntu\shimx64.efi)
Boot0008* ubuntu HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\Ubuntu\grubx64.efi)

findmnt

TARGET SOURCE FSTYPE OPTIONS
/ /dev/disk/by-uuid/2e321d15-1961-4c45-b1ce-7662ab1eee40 ext4 rw,relatime,errors=remount-ro,data=ordered
├─/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup tmpfs tmpfs rw,mode=755
│ │ ├─/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
│ │ ├─/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio
│ │ ├─/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct
│ │ ├─/sys/fs/cgroup/memory cgroup cgroup rw,nosuid,nodev,noexec,relatime,memory
│ │ ├─/sys/fs/cgroup/hugetlb cgroup cgroup rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb
│ │ ├─/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event
│ │ ├─/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio
│ │ ├─/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer
│ │ ├─/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatim...

[Phillip Susi (psusi)]

Looks like someone just set windows back to the default choice. You can switch it back with sudo efibootmgr -o 4,8,0.

[Tony Pursell (ajpursell)]

Hi Phillip

Thanks for all your help. Unfortunately, what you suggested did not change anything. It is still booting straight into Windows unless I go via the F12 boot menu. So I have done some tests.

Here is the output of efibootmgr -v after running sudo efibootmgr -o 4,8,0

BootCurrent: 0004
Timeout: 6 seconds
BootOrder: 0000,0004,0008,0003,0002,000A,0009,0001
Boot0000* Windows Boot Manager HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0002* UEFI: IPV6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO
Boot0003* UEFI: IPV4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)..BO
Boot0004* ubuntu HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\ubuntu\shimx64.efi)
Boot0008* ubuntu HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\Ubuntu\grubx64.efi)
Boot0009* UEFI: IPV6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO
Boot000A* UEFI: IPV4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)..BO

So I ran sudo efibootmgr -o again. Here is the output:

tony@Lloyd:~$ sudo efibootmgr -o 4,8,0,3,2
[sudo] password for tony:
BootCurrent: 0004
Timeout: 6 seconds
BootOrder: 0004,0008,0000,0003,0002
Boot0000* Windows Boot Manager
Boot0001* Windows Boot Manager
Boot0002* UEFI: IPV6 Realtek PCIe GBE Family Controller
Boot0003* UEFI: IPV4 Realtek PCIe GBE Family Controller
Boot0004* ubuntu
Boot0008* ubuntu
Boot0009* UEFI: IPV6 Realtek PCIe GBE Family Controller
Boot000A* UEFI: IPV4 Realtek PCIe GBE Family Controller

Then I ran efibootmgr -v again, and got what we would expect

BootCurrent: 0004
Timeout: 6 seconds
BootOrder: 0004,0008,0000,0003,0002
Boot0000* Windows Boot Manager HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0002* UEFI: IPV6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO
Boot0003* UEFI: IPV4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(b8aeed23982c,0)..BO
Boot0004* ubuntu HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\ubuntu\shimx64.efi)
Boot0008* ubuntu HD(2,1f4800,82000,c380ecc2-e19f-41f3-94ff-c1bb937d71dc)File(\EFI\Ubuntu\grubx64.efi)
Boot0009* UEFI: IPV6 Realtek PCIe...

[Tony Pursell (ajpursell)]

Photo of F12 boot menu (taken on Ubuntu phone!)

[Phillip Susi (psusi)]

Can you post the output of sudo parted -l, and also run dmesg after the efibootmgr -o and see if there are any EFI related error messages.

[Tony Pursell (ajpursell)]

Here is the output of sudo parted -l

Model: ATA WDC WD5000AAKX-0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
 1 1049kB 1050MB 1049MB ntfs hidden, diag
 2 1050MB 1322MB 273MB fat32 EFI system partition boot, esp
 3 1322MB 1847MB 524MB fat32 hidden
 4 1847MB 1981MB 134MB Microsoft reserved partition msftres
 5 1981MB 152GB 150GB ntfs Basic data partition msftdata
 7 152GB 470GB 318GB ext4
 8 470GB 474GB 4183MB linux-swap(v1)
 6 474GB 500GB 26.2GB ntfs hidden, diag

For the record, sda2 is named SYSTEM_DRV and sda3 is named LRS_ESP. When I Iog in, sda3 and sda5 (Windows8_OS) are mounted.

I cannot see any EFI related errors in dmesg after running sudo efibootmgr -o 4,8,0,3,2, but I have attached the output anyway.

[Phillip Susi (psusi)]

Which one is mounted in /boot/efi? sda3 or sda2? It looks like you have some sort of non compliant UEFI firmware that I would classify as malware and it is refusing to let you boot anything but windows.

[Tony Pursell (ajpursell)]

sda2 is mounted on /boot/efi. sda3 is mounted on /media/tony.

It's not quite true that it is refusing to let me boot anything but windows. It's just making it a little bit more difficult by making me boot Ubuntu from the F12 boot menu. I just have to remember to hold down F12 when I start up.

When I look at /boot/efi it has two folders in it - BOOT and EFI. In the EFI folder are Boot, Microsoft and ubuntu. I assume that the ubuntu folder was placed there by ubiquity. Personally, I don't know much about EFI (this is the first PC I have owned that has it). What is it that ubiquity does that should make it display the GRUB menu?

I have attached a full ls -R of /boot/efi.

[Phillip Susi (psusi)]

Setting the Ubuntu entry to the first one in the BootOrder with efibootmgr is what is supposed to make the firmware load grub first, but your firmware seems to rewrite the entry to put windows first every time you boot.

[Tony Pursell (ajpursell)]

Thank you for the help, Phillip. I suspect this has something to do with this

http://support.lenovo.com/sg/en/product_security/modify_uefi_variable

and a heavy handed 'fix' for it. It seems I shall just have to get used to pressing F12 on boot.

[Launchpad Janitor (janitor)]

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