Selecting grub entries (efi) at boot time leads to "error: symbol 'grub_efi_find_last_device_path' not found"

Status changed to 'Confirmed' because the bug affects multiple users.

Would like to confirm this bug, I recently experienced the exact same error when trying to boot a Windows8.1 install from grub menu. My Linux Mint 17 continued to boot normally.

I attempted to remove/reinstall grub with all defaults etc.. no change.

I found in my update history updates of 6 x grub packages firstly from 1.3 to 1.6 and then from 1.6 to 1.7 on January 6th.

grub2-common
grub-common
grub-efi
grub-efi-amd64
grub-efi-amd64-bin
grub-pc-bin

I rolled back to 1.3 using files in /var/apt/cache/archives and presto, Windows boots just fine again. Updated to 1.6 and Windows still boots. Updated to 1.7 and it breaks again with exact same error as reported in this bug.

Another confirmation, and have been waiting for a fix for some time now. Winding back is not a fix. Please assign someone to this.

It might appear that MS are not the only ones to arrogantly ignore the possibility of coexisting OSs.

@carolin-wildt, I'm experiencing the same issue, If you need any help, or testers, or whatever, don't hesitate to ask

@Luis Siera Garcia, yes I have the same problem with windows 7and no solution until now...

Please post the output of the following commands:

sudo efibootmgr -v
md5sum /boot/efi/EFI/ubuntu/grubx64.efi
md5sum /boot/efi/EFI/Boot/bootx64.efi

@psusi
sudo efibootmgr -v
[sudo] password for caro:
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 3001,3002,2001,2002
Boot0000* Notebook Hard Drive BIOS(2,500,e9)................-.O.......O.A.O........................................
Boot0001* Windows Boot Manager HD(2,c8800,82000,1fa8ef6f-1021-4aa4-8555-31954e1c2e2f)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.}...f................
Boot0002* Ubuntu HD(2,c8800,82000,1fa8ef6f-1021-4aa4-8555-31954e1c2e2f)File(\EFI\ubuntu\grubx64.efi)RC
Boot0003* Internal CD/DVD ROM Drive BIOS(3,500,e9)................-.V.......V.A.V........................................
Boot2001* USB Drive (UEFI) RC
Boot2002* Internal CD/DVD ROM Drive (UEFI) RC
Boot3001* EFI Internal Hard Disk or Solid State Disk RC
Boot3002* EFI Internal Hard Disk or Solid State Disk RC
caro@caro-HP-655-Notebook-PC:~$ md5sum /boot/efi/EFI/ubuntu/grubx64.efi
e42bb94d8a5d4ccd68e687822dbc41ce /boot/efi/EFI/ubuntu/grubx64.efi
caro@caro-HP-655-Notebook-PC:~$ md5sum /boot/efi/EFI/Boot/bootx64.efi
517654478fd4760415e2e8046c2d1146 /boot/efi/EFI/Boot/bootx64.efi
caro@caro-HP-655-Notebook-PC:~$
caro@caro-HP-655-Notebook-PC:~$

sudo efibootmgr -v

BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002,0003
Boot0001* UEFI: Corsair Force 3 SSD HD(2,GPT,4702e26a-3252-46f6-b496-3e658a30d05d,0x4a83800,0x32117)/File(\EFI\BOOT\BOOTX64.EFI)AMBO
Boot0002* Hard Drive BBS(HD,,0x0)AMGOAMNO........o.C.o.r.s.a.i.r. .F.o.r.c.e. .3. .S.S.D....................A...........................>..Gd-.;.A..MQ..L.3.1.5.1.3.0.5.1.0.0.F.F.5.1.7.7.0.0.5.1......AMBOAMNO........o.S.T.3.0.0.0.D.M.0.0.1.-.1.C.H.1.6.6....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .1.Z.2.F.W.J.E.J......AMBOAMNO........o.W.D.C. .W.D.3.2.0.0.B.E.V.T.-.2.2.Z.C.T.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.X.W.7.E.8.0.J.S.1.8.2.3......AMBO
Boot0003* CD/DVD Drive BBS(CDROM,,0x0)AMGOAMNO........o.A.S.U.S. . . . .D.R.W.-.2.4.B.5.S.T....................A...........................>..Gd-.;.A..MQ..L.1.D.0.D.L.C.5.0.9.2.1.7. . . . . . . . ......AMBO

md5sum /boot/efi/EFI/ubuntu/grubx64.efi

d187797c3b4c32db64b8b31e7534b148 /boot/efi/EFI/ubuntu/grubx64.efi

md5sum /boot/efi/EFI/Boot/bootx64.efi

7ecbd413a06452d7e5964cc839861692 /boot/efi/EFI/Boot/bootx64.efi

Carolin, please try running sudo efibootmgr -o 0002,0001, reboot, and see if that fixes it. Also run sudo efibootmgr -v after the reboot again.

Could both of you also run md5sum on /boot/efi/EFI/Microsoft/Boot/bootx64.efi? And have you both used boot repair in the past to get the system booting?

it didnt help.
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 3001,3002,2001,2002
Boot0000* Notebook Hard Drive BIOS(2,500,00)................-.O.......O.A.O........................................
Boot0001* Windows Boot Manager HD(2,c8800,82000,1fa8ef6f-1021-4aa4-8555-31954e1c2e2f)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.}...f................
Boot0002* Ubuntu HD(2,c8800,82000,1fa8ef6f-1021-4aa4-8555-31954e1c2e2f)File(\EFI\ubuntu\grubx64.efi)RC
Boot0003* Internal CD/DVD ROM Drive BIOS(3,500,00)................-.V.......V.A.V........................................
Boot2001* USB Drive (UEFI) RC
Boot2002* Internal CD/DVD ROM Drive (UEFI) RC
Boot3001* EFI Internal Hard Disk or Solid State Disk RC
Boot3002* EFI Internal Hard Disk or Solid State Disk RC
caro@caro-HP-655-Notebook-PC:~$

boot repair i already tried

how can I test if md5sum on /boot/efi/EFI/Microsoft/Boot/bootx64.efi runs?

What? That didn't make sense. Can you go into your bios and try to change the boot order there? It looks like it is buggy and refuses to accept the boot configuration and will only boot the hard drive like it is a removable media. You might try deleting the Boot directory on your EFI system partition and see if that helps ( but keep a copy of it somewhere else so you can put it back if the system becomes unbootable ). Otherwise, the only thing for it is to copy ubuntu/grubx64.efi to Boot/bootx64.efi and complain to the manufacturer about their broken firmware ( or better yet, return it for a refund and buy from someone who doesn't use broken firmware ). This is what boot-repair did when you used it before, and after updating grub, the copy is now out of date, hence the error.

Sorry, I don't know very good how to make all this stuff- I don't understand half of it. If there are some simple things like copy and paste something to terminal- I'll make it ;)
Is there any possibility to return to old grub version....?

@carolin wildt

see in the report above at section 2.4 to revert back:

2.4 Reverting to grub 2.02-beta2-9ubuntu1.6_amd64

Steps:

1. Download the following files in a separate (newly created) folder

grub2-common_2.02-beta2-9ubuntu1.6_amd64.deb
grub-common_2.02-beta2-9ubuntu1.6_amd64.deb
grub-efi-amd64_2.02-beta2-9ubuntu1.6_amd64.deb
grub-efi-amd64-bin_2.02-beta2-9ubuntu1.6_amd64.deb
grub-efi_2.02-beta2-9ubuntu1.6_amd64.deb

@Michael Frericks: Is there any link, where to download? Can't find all of them...

@Carolin Wildt

The packages are still in the repositories, you can downgrade via apt-get

sudo apt-get install grub2-common=2.02~beta2-29ubuntu0.2 \
  grub-common=2.02~beta2-29ubuntu0.2 grub-efi-amd64=2.02~beta2-29ubuntu0.2 \
  grub-efi-amd64-bin=2.02~beta2-29ubuntu0.2

sudo apt-mark hold grub-common grub-efi-amd64-bin grub2-common grub-efi-amd64

The hold line will avoid future updates, so you will have to "unhold" the packages as soon as the bus is closed

@Luis Sieira: Thanks. But it's still not working. I don't know why...

You don't need to downgrade, you just need to copy ubuntu/grubx64.efi to Boot/bootx64.efi, which is what boot-repair did before. You can either run it again or manually copy the file.

How can this be a duplicate of the 2 years old bug #1366546?

This one here occured recently (~ January 2016)

The preveios version of grub2-common_2.02 - i my case grub2-common_2.02-beta2-9ubuntu1.6_amd64.deb - works fine.

The questions is: What has changed from

     grub2-common_2.02-beta2-9ubuntu1.6_amd64.deb

to

    grub2-common_2.02-beta2-9ubuntu1.7_amd64.de

Because it occurs every time grub is updated when you have a broken system that only works because boot-repair made a copy of the main grub image. When grub is then updated, your system is still trying to use the old main image, but with the new modules.

@Luis: You wrote me this: The packages are still in the repositories, you can downgrade via apt-
get

sudo apt-get install grub2-common=2.02~beta2-29ubuntu0.2 \
  grub-common=2.02~beta2-29ubuntu0.2 grub-efi-amd64=2.02~beta2-29ubuntu0.2 \
  grub-efi-amd64-bin=2.02~beta2-29ubuntu0.2

sudo apt-mark hold grub-common grub-efi-amd64-bin grub2-common grub-efi-amd64

When I do this I get this out:Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
W: Duplicate sources.list entry http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages)
W: Duplicate sources.list entry http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_main_binary-i386_Packages)
W: Probieren Sie »apt-get update«, um diese Probleme zu korrigieren.
E: Version »2.02~beta2-29ubuntu0.2« für »grub2-common« konnte nicht gefunden werden.
E: Version »2.02~beta2-29ubuntu0.2« für »grub-common« konnte nicht gefunden werden.
E: Version »2.02~beta2-29ubuntu0.2« für »grub-efi-amd64« konnte nicht gefunden werden.
E: Version »2.02~beta2-29ubuntu0.2« für »grub-efi-amd64-bin« konnte nicht gefunden werden.
caro@caro-HP-655-Notebook-PC:~$ apt-get update
E: Sperrdatei /var/lib/apt/lists/lock konnte nicht geöffnet werden. - open (13: Keine Berechtigung)
E: Das Verzeichnis /var/lib/apt/lists/ kann nicht gesperrt werden.
E: Sperrdatei /var/lib/dpkg/lock konnte nicht geöffnet werden. - open (13: Keine Berechtigung)
E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, sind Sie root?
caro@caro-HP-655-Notebook-PC:~$ apt-get updateinstall grub2-common=2.02~beta2-29ubuntu0.2 \
> grub-common=2.02~beta2-29ubuntu0.2 grub-efi-amd64=2.02~beta2-29ubuntu0.2 \
> grub-efi-amd64-bin=2.02~beta2-29ubuntu0.2
E: Ungültige Operation updateinstall
caro@caro-HP-655-Notebook-PC:~$

I have a similar problem, but am having trouble deciphering what is the "safe" resolution here. Can someone help diagnose my issue?

sudo efibootmgr -v
BootCurrent: 0005
Timeout: 2 seconds
BootOrder: 0005,0002,0000
Boot0000 ubuntu VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0002 Windows Boot Manager VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)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.}...2................
Boot0005* UEFI: ST1000DM003-1CH162 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,65535,0)/HD(3,GPT,ba842f15-01fe-4f37-8bb6-bf83225d2adf,0xc8800,0x96000)AMBO

f25a2b1d6702324caa2c55e4790d684f /boot/efi/EFI/ubuntu/grubx64.efi

4db5a7a214176316347cefbbcb40b29f /boot/efi/EFI/Boot/bootx64.efi

cd /boot/efi/EFI/Microsoft/Boot
sudo md5sum *.efi
9cdfbae08da935c0b9c77f01bb2807c6 bootmgfw.efi
c79876d32448cd0ec360d7660ea310d9 bootmgr.efi
7f64065fea99fee26019d4c8bc896c53 memtest.efi

@psusi: one more sample

jani@meriharakka:~$ sudo efibootmgr -v
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0008,0009,0006,0001,000A,000B
Boot0000* ubuntu HD(2,1f4800,82000,307ed590-b2fd-439e-85ff-180e8039f7a7)File(\EFI\ubuntu\grubx64.efi)
Boot0001* Windows Boot Manager HD(2,1f4800,82000,307ed590-b2fd-439e-85ff-180e8039f7a7)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.}....................
Boot0006* Windows Boot Manager HD(3,276800,fa000,aea66ec5-6429-411a-b905-efb033f3bf6b)File(\EFI\Microsoft\Boot\bootmgfw.efi)
Boot0008* Optiarc DVD RW AD-7290H BIOS(3,0,00)AMBO
Boot0009* ST2000DM001-9YN164 BIOS(2,0,00)AMBO
Boot000A* ubuntu HD(2,1f4800,82000,307ed590-b2fd-439e-85ff-180e8039f7a7)File(EFI\Ubuntu\grubx64.efi)
Boot000B* ubuntu HD(3,276800,fa000,aea66ec5-6429-411a-b905-efb033f3bf6b)File(EFI\Ubuntu\grubx64.efi)
jani@meriharakka:~$ md5sum /boot/efi/EFI/ubuntu/grubx64.efi
277187cd570744b1e3719249ad806692 /boot/efi/EFI/ubuntu/grubx64.efi
jani@meriharakka:~$ md5sum /boot/efi/EFI/Microsoft/Boot/bootx64.efi
d17543ded699c2790a5f95ab706f17eb /boot/efi/EFI/Microsoft/Boot/bootx64.efi
jani@meriharakka:~$ md5sum /boot/efi/EFI/Boot/bootx64.efi
d17543ded699c2790a5f95ab706f17eb /boot/efi/EFI/Boot/bootx64.efi

has anyone resolved this? bug #1366546 does not seem to be moving

this was proposed by psusi:
cd /boot/efi/EFI
sudo cp ubuntu/grubx64.efi Boot/bootx64.efi
is this safe?

another option was to downgrade to grub 2.02-beta2-9ubuntu1.6_amd64

for me, copying ubuntu/grubx64.efi did not solve the issue, instead downgrade to 2.02-beta2-9ubuntu1.6 solved it.

This bug has nothing to do with bug 1366546, so I've deduplicated it. This is a bug in boot-repair or whatever has created the boot images being used, as Phillip pointed out.

It's not an issue in grub -- grub simply installs the bootloader in EFI/ubuntu, not in EFI/boot. I don't know what happened to get the system in this state; but to fix this we'll first need to know the current state of boot variables -- could you please paste in the output of the following command:

efibootmgr -v

>sudo efibootmgr -v

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0002,0001,2001,2002,2003
Boot0000* Windows Boot Manager HD(2,12c800,96000,8c965bfd-9dc7-445e-b481-cec70920cd03)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* Unknown Device: HD(2,12c800,96000,8c965bfd-9dc7-445e-b481-cec70920cd03)File(\EFI\ubuntu\shimx64.efi)RC
Boot0002* ubuntu HD(2,12c800,96000,8c965bfd-9dc7-445e-b481-cec70920cd03)File(\EFI\ubuntu\grubx64.efi)
Boot0004* WDC WD10JPVX-22JC3T0 BIOS(4,500,00)................-...........A......R..............................)-........A.........................
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
michael@gonster:~$

Am having the same issue (dual boot, win10 and linux mint based on ubuntu 14.04).
Linux boots, but not win10.

Looks like bug was introduced with 2.02~beta2-9ubuntu1.7.diff.gz

Check here for the commit details:
http://launchpadlibrarian.net/230268356/grub2_2.02~beta2-9ubuntu1.6_2.02~beta2-9ubuntu1.7.diff.gz

Maybe the author of the affected 1.7 version (dann frazier) can help us - I added his e-mail to the subscriber list of this bug.

My details:

# find /boot/efi -ls | grep x64.efi

  14 117 -rwxr-xr-x 1 root root 119808 Jun 26 2015 /boot/efi/EFI/linuxmint/grubx64.efi
    20 1260 -rwxr-xr-x 1 root root 1289424 Apr 13 21:37 /boot/efi/EFI/ubuntu/shimx64.efi
    21 936 -rwxr-xr-x 1 root root 958328 Apr 13 21:37 /boot/efi/EFI/ubuntu/grubx64.efi
   404 1129 -rwxr-xr-x 1 root root 1155424 Jul 10 2015 /boot/efi/EFI/Boot/bkpbootx64.efi
   405 1324 -rwxr-xr-x 1 root root 1355736 Jul 31 2015 /boot/efi/EFI/Boot/bootx64.efi
   772 1129 -rwxr-xr-x 1 root root 1155424 Jul 31 2015 /boot/efi/boot-sav/log/2015-07-31__16h20boot-repair52/sdb2/bootx64.efi

# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2002,0000,0001,2001,2003
Boot0000* Windows Boot Manager HD(2,12c800,32000,c93e4576-8212-41d7-bf8b-539d15048fd9)File(\EFI\linuxmint\grubx64.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 HD(2,12c800,32000,c93e4576-8212-41d7-bf8b-539d15048fd9)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0002* ATAPI CDROM: MATSHITA DVD-RAM UJ8HC ACPI(a0341d0,0)PCI(1f,2)03120a00010000000000CD-ROM(1,52b,15a515)RC
Boot0003* Unknown Device: HD(2,12c800,32000,c93e4576-8212-41d7-bf8b-539d15048fd9)File(\EFI\ubuntu\shimx64.efi)RC
Boot0004* ubuntu HD(2,12c800,32000,c93e4576-8212-41d7-bf8b-539d15048fd9)File(\EFI\ubuntu\shimx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC

By the way, old version of grub (1.6 version) can be also downloaded here:
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/8443424