Bug #1753518 “package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 f...” : Bugs : grub2-signed package : Ubuntu

Revision history for this message

Thierry Mallard (thierrymallard) wrote on 2018-03-05:

#1

AptOrdering.txt Edit (360 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Df.txt Edit (847 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (75.2 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (21.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (5.3 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Thierry Mallard (thierrymallard) wrote on 2018-03-06:

#2

Strace log extract for the dpkg --configure strace -qf -o /tmp/grub_installation.log dpkg --configure grub-efi-amd64-signed Edit (3.2 KiB, text/plain)

I made a strace for the installation process and find the following error in a subprocess, which seems to be the cause.

strace -qf -o /tmp/grub_installation.log dpkg --configure grub-efi-amd64-signed

Revision history for this message

Thierry Mallard (thierrymallard) wrote on 2018-03-06:

#3

grub-install -v Edit (696.3 KiB, text/plain)

Furthermore, I looked for the postinst script and found out that it's just the « grub-install » command which fails.

root@ingatech-XPS-13-9343:~# LC_ALL=C grub-install
Installing for x86_64-efi platform.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required.

The attached file is a dump of a grub-install -v

Hope this helps...

Revision history for this message

Thierry Mallard (thierrymallard) wrote on 2018-03-06:

#4

grub-install.txt Edit (600.1 KiB, text/plain)

... and LC_ALL=C version of the grub-install -v command

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-03-25:

#5

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

Changed in grub2-signed (Ubuntu):
status:	New → Confirmed

Revision history for this message

Daniel Garcia Sardina (silverfish27) wrote on 2018-07-09:

#6

Any workaround available for this bug?

Revision history for this message

Morten (apsidjoaieroie-deactivatedaccount) wrote on 2018-07-10:

#7

Experiencing this on 18.04 as well.

Revision history for this message

Michael (mes2k) wrote on 2018-07-16:

#8

My hardware: Dell XPS 13 (9343)

I am able to reproduce the error using
$ sudo dpkg-reconfigure grub-efi-amd64-signed

Then I thought what might be different on my system, because this kind of error should normally affect more people. I remembered a BIOS update some weeks ago. Before attempting to downgrade I had a lucky guess and deleted the BIOS update file (9343_A17.exe) from /boot/efi - et voila: the problem seems to be gone.

Can other affected people please try to check their /boot/efi partition for unneeded files?

I updated my BIOS using this method (putting the exe file from the Dell support page to /boot/efi and then choosing BIOS update in the F12 boot menu) since months or even years. So this issue definitelly is a regression within Ubuntu.

BR, Michael

Revision history for this message

Henrique Ferrolho (henriqueferrolho) wrote on 2018-07-27:

#9

Dell XPS 13 9343 here too, running Ubuntu 18.04.1 with 4.15.0-23-generic.
However, I do not use the same method as @mes2k for BIOS updates. I just boot into Windows to install the .exe... Therefore I have nothing under /boot/efi that could be causing it...

➜ ~ sudo dpkg-reconfigure grub-efi-amd64-signed
/usr/sbin/dpkg-reconfigure: grub-efi-amd64-signed is broken or not fully installed.

➜ ~ sudo apt install grub-efi-amd64-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
grub-efi-amd64-signed is already the newest version (1.93.3+2.02-2ubuntu8.2).
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up grub-efi-amd64-signed (1.93.3+2.02-2ubuntu8.2) ...
Installing for x86_64-efi platform.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

➜ efi ls -l
total 5284
drwxr-xr-x 5 root root 4096 Apr 4 2015 Boot
-rwxr-xr-x 1 root root 1615712 Apr 4 2015 bootmgfw.efi
-rwxr-xr-x 1 root root 427680 Apr 4 2015 bootmgr
-rwxr-xr-x 1 root root 1612128 Apr 4 2015 bootmgr.efi
drwxr-xr-x 3 root root 4096 Jul 16 10:52 boot-repair
-r-xr-xr-x 1 root root 512 Jul 29 2015 BOOTSECT.BAK
drwxr-xr-x 3 root root 4096 Apr 4 2015 DELL
drwxr-xr-x 7 root root 4096 May 30 2015 EFI
drwxr-xr-x 2 root root 4096 Apr 4 2015 en-us
-rwxr-xr-x 1 root root 1183744 Jan 1 1980 FSCK0000.REC
-rwxr-xr-x 1 root root 106496 Jan 1 1980 FSCK0001.REC
-rwxr-xr-x 1 root root 427680 Apr 4 2015 NTLDR
drwxr-xr-x 2 root root 4096 Apr 4 2015 sources

Dell XPS 13 9343 here too, running Ubuntu 18.04.1 with 4.15.0-23-generic.
However, I do not use the same method as @mes2k for BIOS updates. I just boot into Windows to install the .exe... Therefore I have nothing under /boot/efi that could be causing it...

➜  ~ sudo dpkg-reconfigure grub-efi-amd64-signed
/usr/sbin/dpkg-reconfigure: grub-efi-amd64-signed is broken or not fully installed.

➜  ~ sudo apt install grub-efi-amd64-signed
Reading package lists... Done
Building dependency tree       
Reading state information... Done
grub-efi-amd64-signed is already the newest version (1.93.3+2.02-2ubuntu8.2).
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up grub-efi-amd64-signed (1.93.3+2.02-2ubuntu8.2) ...
Installing for x86_64-efi platform.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

➜  efi ls -l
total 5284
drwxr-xr-x 5 root root    4096 Apr  4  2015 Boot
-rwxr-xr-x 1 root root 1615712 Apr  4  2015 bootmgfw.efi
-rwxr-xr-x 1 root root  427680 Apr  4  2015 bootmgr
-rwxr-xr-x 1 root root 1612128 Apr  4  2015 bootmgr.efi
drwxr-xr-x 3 root root    4096 Jul 16 10:52 boot-repair
-r-xr-xr-x 1 root root     512 Jul 29  2015 BOOTSECT.BAK
drwxr-xr-x 3 root root    4096 Apr  4  2015 DELL
drwxr-xr-x 7 root root    4096 May 30  2015 EFI
drwxr-xr-x 2 root root    4096 Apr  4  2015 en-us
-rwxr-xr-x 1 root root 1183744 Jan  1  1980 FSCK0000.REC
-rwxr-xr-x 1 root root  106496 Jan  1  1980 FSCK0001.REC
-rwxr-xr-x 1 root root  427680 Apr  4  2015 NTLDR
drwxr-xr-x 2 root root    4096 Apr  4  2015 sources

Revision history for this message

Ronan Mooney (roomey) wrote on 2018-08-08:

#10

I hit this issue during an update last night. I am now worried about rebooting my laptop. Is any other info required to investigate this?

I think #8 is unrelated, and actually due to lack of space on the EFI partition. There is plenty of room in my system, and removing the exe does not help

# df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 1.7M 1.6G 1% /run
/dev/mapper/xubuntu--vg-root 219G 195G 13G 94% /
tmpfs 7.8G 104M 7.7G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/loop0 87M 87M 0 100% /snap/core/4917
/dev/loop2 87M 87M 0 100% /snap/core/4830
/dev/sda2 442M 227M 193M 55% /boot
/dev/sda1 300M 8.1M 292M 3% /boot/efi
tmpfs 1.6G 32K 1.6G 1% /run/user/1000
/dev/loop3 87M 87M 0 100% /snap/core/5145

Revision history for this message

Ronan Mooney (roomey) wrote on 2018-08-08:

#11

WORKAROUND:
From:

https://askubuntu.com/questions/1031066/errors-during-upgrade-from-17-10-to-18-04-shim-signed-and-grub-efi-amd64-signed

    sudo su -
    cd /boot/efi/EFI
    mv ubuntu ubuntu-old
    apt install -f
    mv ubuntu-old ubuntu
    update-grub2
    exit

"It seems that the newer grub couldn't access the /boot/efi/EFI/ubuntu directory, for some reason. So since my system was booting normally, I want just to get rid off that error everytime I was using the apt. So I thought that workaround just to check it the installation would finish and it seems that worked. Lastly, I restored the ubuntu directory name just not mess around with my system's ability to boot. It seems, I forgot to mention to issue an update-grub2 afterwards. – George Tavantzopoulos"

Revision history for this message

oldfred (oldfred) wrote on 2018-08-23:

#12

May be related to this bug.
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1787692

Revision history for this message

Andrei Borzenkov (arvidjaar-s) wrote on 2018-08-24:

#13

It is possible that there are different problems but in my case the problem is that efibootmgr cannot delete EFI variable:

root@bor-Latitude-E5450:~# LC_ALL=C grub-install
Installing for x86_64-efi platform.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required.

or more verbosely

grub-install: info: Registering with EFI: distributor = `ubuntu', path = `\EFI\ubuntu\shimx64.efi', ESP at hostdisk//dev/sda,gpt1.
grub-install: info: executing efibootmgr --version </dev/null >/dev/null.
grub-install: info: executing modprobe -q efivars.
grub-install: info: executing efibootmgr -b 0000 -B.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required.

It is neither grub nor efibootmgr issue, I cannot remove variable even manually:

root@bor-Latitude-E5450:/sys/firmware/efi/efivars# LC_ALL=C rm Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c
rm: cannot remove 'Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c': Invalid argument

and stracing it

unlinkat(AT_FDCWD, "Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c", 0) = -1 EINVAL (Invalid argument)

As I do not believe all systems got firmware problem at once, it is more likely kernel issue. There is nothing in dmesg.

I do not see how it can be fixed by removing anything in ESP.

Revision history for this message

Andrei Borzenkov (arvidjaar-s) wrote on 2018-08-24:

#14

After rebooting everything worked again

bor@bor-Latitude-E5450:~$ sudo dpkg --configure -a
Настраивается пакет grub-efi-amd64-signed (1.93.4+2.02-2ubuntu8.3) …
Выполняется установка для платформы x86_64-efi.
Установка завершена. Ошибок нет.
Обрабатываются триггеры для shim-signed (1.34.9.2+13-0ubuntu2) …
No DKMS modules installed.
bor@bor-Latitude-E5450:~$

Revision history for this message

kylea (kylea) wrote on 2018-08-29:

#15

This the message I get after running:

sudo dpkg --configure -a

Cannot upgrade Secure Boot enforcement policy due to unsigned kernels
│ │
│ Your system has UEFI Secure Boot enabled in firmware, and the following │
│ kernels present on your system are unsigned: │
│ │
│ 4.18.0-041800-generic │
│ │
│ │
│ These kernels cannot be verified under Secure Boot. To ensure your │
│ system remains bootable, GRUB will not be upgraded on your disk until │
│ these kernels are removed or replaced with signed kernels.

Revision history for this message

shivang patel (patelshivang82) wrote on 2018-09-05:

#16

Ya. I am facing same issue. Anyone know how to resolve it ?

Revision history for this message

Andrei Borzenkov (arvidjaar-s) wrote on 2018-09-07:

#17

I got the same error ("efibootmgr failed") again after today's update and again running "dpkg --configure -a" immediately after reboot completed without errors. It really sounds like kernel issue - something goes wrong over time.

Revision history for this message

Antony Jones (wrh) wrote on 2018-09-10:

#18

Ronan Mooney's workaround worked for me.

Also Dell XPS 13. Sounds like this is a machine specific issue.

Revision history for this message

Jeroen Claeys (jeroenclaeys) wrote on 2018-09-14:

#19

Latitude E7450. Same issue.

Revision history for this message

oldfred (oldfred) wrote on 2018-09-16:

#20

I updated UEFI from Asus, but same version I was using since April.

Still only can boot with rEFInd from sdc or flash drive with full install of Ubuntu.

UEFI does not want to see ESP on sda which is mounted by fstab. It changes entries to like drive disconnected.
And on reboot all new entries only from ESP on sdc are created.

But ran dosfsk on ESP at sda1, and it showed error with dirty bit set, as soon as I rebooted so shutdown was not correct.

Also tried manually unmounting my ESP at sda1 and immediately shutting down, but same issue. UEFI would not see ESP on sda1 and dirty bit set again. And all new entries in UEFI from sdc's ESP files.

Revision history for this message

Rémi Douvenot (remizzz) wrote on 2018-10-05:

#21

I have installed the IEEE version of the GRUB. Package: grub-ieee1275. It seems to work perfectly.

However, I am not expert in computer science, therefore I have no idea of the possible consequences of this change.

Revision history for this message

Andrea Fernandes da Fonseca (andreafdaf) wrote on 2018-10-13:

#22

Dell XPS 13 here too, Ronan Mooney's workaround does the trick and everything was fine.

Updating to 1.93.7 brought up this same error once again :/

Revision history for this message

Owen (owen-ozone) wrote on 2018-10-15:

#23

This also just happened to me for the second time updating to 1.93.7

Workaround fixed it again.

Revision history for this message

Daniel Holmes (danielgholmes) wrote on 2018-10-17:

#24

Had the same issue on a Dell Latitude E5550. Reboot also fixed it for me.

Revision history for this message

Ronan Mooney (roomey) wrote on 2018-11-02:

#25

Just hit me again updating to
grub-efi (2.02-2ubuntu8.7)

workaround from #11 worked again

Dell Latitude E5450

Revision history for this message

Andrei Borzenkov (arvidjaar-s) wrote on 2018-11-06:

#26

And I just had exactly the same problem (failure to modify EFI variable) during update of secureboot-db and again running postinstall script immediately after reboot worked OK.

Silence is becoming ridiculous. What we need is kernel with verbose debug output about handling EFI variables. Right now it is not even clear whether failure is returned by kernel or firmware.

Revision history for this message

patrick (patj-8) wrote on 2018-11-13:

#27

Hi, I had the same bug since summer 2018. But for me, the following fixed the problem:
The bug was caused by a "no space left on device error" on the "efi firmware". There was a hint in the apt log.
So a colleague of mine (https://launchpad.net/~aburch) gave me the tip to delete dump files in

/sys/firmware/efi/efivars

There where hundred of files starting with "dump" and I removed only these!
This fixed it immediately.

Can someone confirm that deleting these files is save? Is that the trigger of the general bug?

Revision history for this message

Bert Vermeulen (biot) wrote on 2018-11-13:

#28

That appears to be unrelated to this bug, plenty of space left here for me with no dump files.

I'm seeing the same error everyone else is seeing: efibootmgr unable to delete a file in EFI via sysfs, as Thierry Mallard's strace already showed:

unlink("/sys/firmware/efi/efivars/Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c") = -1 EINVAL (Invalid argument)
write(2, "Could not delete variable", 25Could not delete variable) = 25
write(2, ": Invalid argument\n", 19: Invalid argument
) = 19

Revision history for this message

cement_head (andorjkiss) wrote on 2019-02-08:

#29

This is the error I just got, and the warning when I used workaround #11

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up grub-efi-amd64-signed (1.93.12+2.02-2ubuntu8.11) ...
/var/lib/dpkg/info/grub-efi-amd64-signed.postinst: 22: /var/lib/dpkg/info/grub-efi-amd64-signed.postinst: /usr/share/grub/grub-check-signatures: Permission denied
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 126
Errors were encountered while processing:
grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
andor@andor-galagopro:~$ sudo su -
[sudo] password for andor:
root@###############:~# cd /boot/efi/EFI
root@###############:/boot/efi/EFI# mv ubuntu ubuntu-old
root@###############:/boot/efi/EFI# apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up grub-efi-amd64-signed (1.93.12+2.02-2ubuntu8.11) ...
W: APT had planned for dpkg to do more than it reported back (0 vs 4).
Affected packages: grub-efi-amd64-signed:amd64

Revision history for this message

Noel Miller (noeldamonmiller) wrote on 2019-02-08:

#30

workaround #11 just worked for me. Dell XPS-13 (9343) circa 2016-02

Revision history for this message

Rolf Kutz (vzsze) wrote on 2019-02-09:

#31

I'm seeing the same error.

$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up grub-efi-amd64-signed (1.93.13+2.02-2ubuntu8.12) ...
Installing for x86_64-efi platform.
File descriptor 4 (/dev/sdb1) leaked on vgs invocation. Parent PID 16086: grub-install
File descriptor 4 (/dev/sdb1) leaked on vgs invocation. Parent PID 16086: grub-install
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed; however:
Package grub-efi-amd64-signed is not configured yet.

dpkg: error processing package shim-signed (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message

Bruno16 (bruno17) wrote on 2019-02-10:

#32

I have a DELL 9343 XPS running 'Ubuntu 18.04.1'. The first recent indication that I had a problem with the Software Updater was with an update I installed on 31-JAN-2019 when Software Updater returned the message 'package operation failed'.

Looking back at the logs, I found in /var/log/dpkg.log the last three lines indicated that my grub-efi was shown as 'half-configured' but not 'installed'.

2019-02-01 07:03:44 startup packages configure
2019-02-01 07:03:44 configure grub-efi-amd64-signed:amd64 1.93.11+2.02-2ubuntu8.10 <none>
2019-02-01 07:03:44 status half-configured grub-efi-amd64-signed:amd64 1.93.11+2.02-2ubuntu8.10

Since I don't like error messages, I began searching for an explanation and for a solution before attempting to remedy the problem. I found that others felt there may be a problem with BIOS file(s) in a permission protected folder /boot/efi.

I found the latest BIOS update '9343_A18.exe' on the DELL support page and downloaded the file. In order to copy the BIOS update binary into the efi partition (/boot/efi) I had to use sudo in the Terminal to copy the 9343_A18.exe file to /boot/efi.

I then followed the instructions to update the BIOS which is to restart / reboot, pressing F12 key in order to enter in the Boot Menu and then choose BIOS Update selecting 9343_A18.exe and choosing to update the BIOS.

After updating the BIOS, Ubuntu Software Updater works fine again without returning any error messages. The last line in the most recent version of /var/log/dpkg.log shows the following documentation that my grub-efi is now shown as 'half-configured' and finally 'installed'.

2019-02-10 05:04:47 configure grub-efi-amd64-signed:amd64 1.93.11+2.02-2ubuntu8.10 <none>
2019-02-10 05:04:47 status half-configured grub-efi-amd64-signed:amd64 1.93.11+2.02-2ubuntu8.10
2019-02-10 05:04:49 status installed grub-efi-amd64-signed:amd64 1.93.11+2.02-2ubuntu8.10

After spending considerable time looking into my problem, I concluded that updating the BIOS to the latest version from DELL was the best answer and solved my problem.

Hope this helps anyone looking for a similar answer. Installed systems are of course different. If your problem is different, looking in /var/log/dpkg.log for 'status half-configured' without seeing 'status installed' files may give you a lead on where to look for your own solution.