Could not prepare Boot variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to install/upgrade: Unterprozess installed shim-signed package post-installation script gab den Fehler-Ausgangsstatus 1 zurück)

[Reinhard Gimbel]

Bug report popped up during kernel upgrade

ProblemType: Package
DistroRelease: Ubuntu Kylin 18.04
Package: shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Jun 11 20:05:16 2018
EFITables:
 Jun 11 21:21:17 kolibri-lnx kernel: efi: EFI v2.00 by Phoenix Technologies Ltd.
 Jun 11 21:21:17 kolibri-lnx kernel: efi: ACPI=0xc71d9000 ACPI 2.0=0xc71d9014 SMBIOS=0xc70ec000
 Jun 11 21:21:17 kolibri-lnx kernel: secureboot: Secure boot could not be determined (mode 0)
 Jun 11 19:59:04 kolibri-lnx fwupd[2803]: disabling plugin because: failed to startup uefi: UEFI firmware updating not supported
ErrorMessage: Unterprozess installed shim-signed package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
InstallationDate: Installed on 2017-10-28 (226 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.1
SourcePackage: shim-signed
Title: package shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to install/upgrade: Unterprozess installed shim-signed package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: Upgraded to bionic on 2018-05-07 (35 days ago)

[Steve Langasek (vorlon)]

The error in your log is:

shim-signed (1.34.9+13-0ubuntu2) wird eingerichtet ...
x86_64-efi wird für Ihre Plattform installiert.
Could not prepare Boot variable: No space left on device
grub-install: Fehler: efibootmgr failed to register the boot entry: Eingabe-/Ausgabefehler.
dpkg: Fehler beim Bearbeiten des Paketes shim-signed (--configure):
This indicates that there is a problem writing the bootloader information to your firmware's nvram. It is a requirement that UEFI systems allow writing to these variables from the OS in order to update the boot options.

According to your bug report, you initially installed Ubuntu 17.10. Is it possible your firmware's nvram is locked because you are affected by bug #1734147?

Is it possible that you have somehow toggled a "lock" on the firmware variables, preventing them from being updated? I understand that some Lenovo firmware has such an option, did you knowingly turn it on?

Your existing firmware boot config shows no entry for ubuntu, and no BootOrder variable. How do you boot Ubuntu on this system, since it's not a boot option in your firmware config?

[Mathieu Trudel-Lapierre (cyphermox)]

Hi,

Could you please run the following commands and report their full output?

sudo efibootmgr -v
sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi

(the backslashes there matter, we are building a path in EFI mode)

Thanks!

[Reinhard Gimbel (linux-dragonfly7)]

As requested:

0 reinhard@kolibri-lnx $ sudo efibootmgr -v
[sudo] Passwort für reinhard:
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 000A,0000,0001,0002,0005,0006,0007,0008,0009
Boot0000 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0002 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0003 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0004 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0005* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0006* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0007* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0008* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0009* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000A* ubuntu HD(2,GPT,f1fb36c9-50b6-474f-98f9-e595c7007d01,0xe1800,0x32000)/File(\EFI\ubuntu\shimx64.efi)

~
0 reinhard@kolibri-lnx $ sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
efibootmgr: ** Warning ** : Boot000A has same label ubuntu
Could not prepare Boot variable: No space left on device

~
0 reinhard@kolibri-lnx $

The notebook/netbook is a rather old Lenovo ThinkPad X121e with the (Lenovo-typical ?) EFI implementation flaws. I'm not sure if this fact is contributing in a bad way as well.

BR,
Reinhard.

[Launchpad Janitor (janitor)]

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

[oldfred (oldfred)]

May be similar to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271

[CarbonPepper (carbonpepper)]

I had the same today, dist-upgrade to linux-headers-4.15.0-34 resulted in the same error as above.

sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up shim-signed (1.37~18.04.1+15+1533136590.3beb971-0ubuntu1) ...
Installing for x86_64-efi platform.
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 shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Never had this before and no firmware / BIOS changes. It's a dual-boot system with Win10.

------------------
sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up shim-signed (1.37~18.04.1+15+1533136590.3beb971-0ubuntu1) ...
Installing for x86_64-efi platform.
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 shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

---------------------
sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
Could not prepare Boot variable: No space left on device

[CarbonPepper (carbonpepper)]

Sorry for double-paste. Meant to copy this.

sudo efibootmgr -v
BootCurrent: 0003
Timeout: 2 seconds
No BootOrder is set; firmware will attempt recovery
Boot0000* Windows Boot Manager HD(3,GPT,acf9cc9b-1f26-4689-b170-6c645c62eb27,0x101800,0x32000)/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* USB Floppy/CD VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)..BO
Boot0002* USB Hard Drive VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)..BO
Boot000C* UEFI: IPv4 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(3ca82ab30e22,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot000D* UEFI: IPv6 Realtek PCIe GBE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(3ca82ab30e22,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot000E Fake Legacy Option VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0600000000)..BO

[CarbonPepper (carbonpepper)]

Update - a BIOS upgrade fixed this for me. HP Pavilion All-in-One - 23-q199na.
Perhaps this cleared the NVRAM.

sudo apt -f install resulted in:

W: APT had planned for dpkg to do more than it reported back (0 vs 4).
   Affected packages: shim-signed:amd64

and was fixed with a reinstall
sudo apt install --reinstall shim-signed

[Jim Oltman (jim-oltman)]

I'm also running into this issue on 18.04 (fresh install about 3 months ago)

Motherboard: Asus Sabertooth Z97 Mark S
CPU: Intel I7-4790K
RAM: 32GB
Primary Boot Drive: Crucial M550 256GB SSD
Secondary Drives (ZFS mirror, non-boot): Crucial M550 256GB SSD and Samsung 830 SSD.

sudo apt -f install
...
2 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.5+2.02-2ubuntu8.4) ...
Installing for x86_64-efi platform.
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 configuration of 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 unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Errors were encountered while processing:
 grub-efi-amd64-signed
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Below is the output requested from cyphermox:

sudo efibootmgr -v

BootCurrent: 0000
Timeout: 1 seconds
No BootOrder is set; firmware will attempt recovery
Boot0003* Hard Drive BBS(HD,,0x0)..GO..NO........O.C.r.u.c.i.a.l._.C.T.2.5.6.M.5.5.0.S.S.D.1.................>..Gd-.;.A..MQ..L. . . . . . . . .4.1.4.2.C.0.0.5.7.B.4.D........BO..NO........O.C.r.u.c.i.a.l._.C.T.2.5.6.M.5.5.0.S.S.D.1.................>..Gd-.;.A..MQ..L. . . . . . . . .4.1.0.2.C.0.1.2.7.B.6.2........BO..NO........O.S.A.M.S.U.N.G. .S.S.D. .8.3.0. .S.e.r.i.e.s.................>..Gd-.;.A..MQ..L.1.S.H.0.E.N.C.A.0.9.3.1.5.6. . . . . . ........BO..NO........O.S.T.2.0.0.0.D.L.0.0.3.-.9.V.T.1.6.6.................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Y.5.5.D.T.Q.3.X........BO
Boot0084* UEFI OS HD(1,GPT,67596964-080e-41ce-8b5c-42ce19e22bb6,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0085* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO........O.T.S.S.T.c.o.r.p. .D.V.D.-.R.W. .S.H.-.2.1.6.D.B.................>..Gd-.;.A..MQ..L.9.R.J.6.8.6.D.D.0.8.8.1.L.5. . . . . . ........BO..NO........M.H.L.-.D.T.-.S.T.B.D.-.R.E. .B.E.1.4.N.U.4.0.................<..Gd-.;.A..MQ..L.P.R.O.L.I.F.I.C.M.P.0.0.0.0.0.0.1.6.B........BO

sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
Could not prepare Boot variable: No such file or directory

Unfortunately, I don't have a BIOS update handy as I'm already on the latest BIOS. I'd really like to reboot my system without down time.

[Luis Rodriguez (laragones)]

Same error after upgrade

root@node13:/boot/efi/EFI/ubuntu# efibootmgr -v
BootCurrent: 000D
Timeout: 10 seconds
No BootOrder is set; firmware will attempt recovery
Boot0000* CD/DVD Rom VenMedia(0c588db8-6af4-11dd-a992-00197d890238,0c)
Boot0001* Floppy Disk VenMedia(0c588db8-6af4-11dd-a992-00197d890238,00)
Boot0002* Hard Disk 0 VenMedia(0c588db8-6af4-11dd-a992-00197d890238,08)
Boot0003* PXE Network PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(5cf3fc55f190,0)
Boot0004* Hard Disk 1 VenMedia(0c588db8-6af4-11dd-a992-00197d890238,09)
Boot0005* Hard Disk 2 VenMedia(0c588db8-6af4-11dd-a992-00197d890238,0a)
Boot0006* Hard Disk 3 VenMedia(0c588db8-6af4-11dd-a992-00197d890238,0b)
Boot0007* USB Storage VenMedia(0c588db8-6af4-11dd-a992-00197d890238,03)
Boot0008* Diagnostics VenMedia(0c588db8-6af4-11dd-a992-00197d890238,da)
Boot0009* iSCSI VenMedia(0c588db8-6af4-11dd-a992-00197d890238,04)
Boot000A* iSCSI Critical VenMedia(0c588db8-6af4-11dd-a992-00197d890238,05)
Boot000B* Legacy Only VenMedia(0c588db8-6af4-11dd-a992-00197d890238,ee)
Boot000C* Embedded Hypervisor VenMedia(0c588db8-6af4-11dd-a992-00197d890238,01)
root@node13:/boot/efi/EFI/ubuntu# efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
Could not prepare Boot variable: No space left on device
root@node13:/boot/efi/EFI/ubuntu#

[Steve Langasek (vorlon)]

On Wed, Oct 03, 2018 at 12:02:02PM -0000, Luis Rodriguez wrote:
> root@node13:/boot/efi/EFI/ubuntu# efibootmgr -v
> BootCurrent: 000D
> Timeout: 10 seconds
> No BootOrder is set; firmware will attempt recovery
> Boot0000* CD/DVD Rom VenMedia(0c588db8-6af4-11dd-a992-00197d890238,0c)

Can you provide additional information about what model of hardware this is
and what firmware version you're running?

[Reinhard Gimbel (linux-dragonfly7)]

Hi !

The device is a Lenovo Thinkpad X121 netbook/notebook built roughly mid of 2011. It has got a not sooo powerful AMD E-350 CPU with related AMD chipset. It is serving as my gateway to the world when travelling around.

Lenovo is said to have a sort of strange BIOS / UEFI implenentations though.

Please report back if you require further (ie. more detailed) information !

Best regards,
Reinhard.

[Luis Rodriguez (laragones)]

Sure, this is happening on an IBM Tower System x3400 M3

Product name System x3400 M3
Machine type and model: 737954A

Firmware VPD
Firmware Type Version String Release Date
IMM YUOOH5A-1.55 01/15/2018
UEFI Y4E161A-1.17 06/07/2018
DSA DSYT83D-3.33 01/07/2011

[Quentin Skousen (qskousen)]

Also happened to me on an IBM rackmount System x3650 M3. I had a firmware
version to apply, flashing the firmware seems to have resolved it, at least
for now.

On Wed, Oct 3, 2018 at 7:30 PM Luis Rodriguez <email address hidden> wrote:

> Sure, this is happening on an IBM Tower System x3400 M3
>
>
> Product name System x3400 M3
> Machine type and model: 737954A
>
> Firmware VPD
> Firmware Type Version String Release Date
> IMM YUOOH5A-1.55 01/15/2018
> UEFI Y4E161A-1.17 06/07/2018
> DSA DSYT83D-3.33 01/07/2011
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1776271
>
> Title:
> Could not prepare Boot variable: No space left on device (package
> shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to
> install/upgrade: Unterprozess installed shim-signed package post-
> installation script gab den Fehler-Ausgangsstatus 1 zurück)
>
> Status in shim-signed package in Ubuntu:
> Confirmed
>
> Bug description:
> Bug report popped up during kernel upgrade
>
> ProblemType: Package
> DistroRelease: Ubuntu Kylin 18.04
> Package: shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu]
> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
> Uname: Linux 4.15.0-22-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Datei oder
> Verzeichnis nicht gefunden: '/proc/sys/kernel/moksbstate_disabled'
> ApportVersion: 2.20.9-0ubuntu7.2
> Architecture: amd64
> Date: Mon Jun 11 20:05:16 2018
> EFITables:
> Jun 11 21:21:17 kolibri-lnx kernel: efi: EFI v2.00 by Phoenix
> Technologies Ltd.
> Jun 11 21:21:17 kolibri-lnx kernel: efi: ACPI=0xc71d9000 ACPI
> 2.0=0xc71d9014 SMBIOS=0xc70ec000
> Jun 11 21:21:17 kolibri-lnx kernel: secureboot: Secure boot could not
> be determined (mode 0)
> Jun 11 19:59:04 kolibri-lnx fwupd[2803]: disabling plugin because:
> failed to startup uefi: UEFI firmware updating not supported
> ErrorMessage: Unterprozess installed shim-signed package
> post-installation script gab den Fehler-Ausgangsstatus 1 zurück
> InstallationDate: Installed on 2017-10-28 (226 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
> Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-3
> PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> 2.7.15~rc1-1
> RelatedPackageVersions:
> dpkg 1.19.0.5ubuntu2
> apt 1.6.1
> SourcePackage: shim-signed
> Title: package shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to
> install/upgrade: Unterprozess installed shim-signed package
> post-installation script gab den Fehler-Ausgangsstatus 1 zurück
> UpgradeStatus: Upgraded to bionic on 2018-05-07 (35 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271/+subscriptions
>

[Luis Rodriguez (laragones)]

I had flashed the latest firmware a few months back, did you re-flash the same version or a new one?

[Quentin Skousen (qskousen)]

It was a new version. If you are able to reflash the same version, it may work, it doesn't seem to be related to a specific firmware version from what I can tell, I think something in the process of flashing the firmware enables the boot device to be updated properly.

[Red Dress (reddress)]

I just need to do this:
sudo apt install --reinstall shim-signed
Thanks abssorb.

[Luis Rodriguez (laragones)]

thanks,
this
sudo apt install --reinstall shim-signed

didn't work for me.. still getting the same error

[Quentin Skousen (qskousen)]

I also tried that before I flashed my firmware and got the same error.

[Jim Oltman (jim-oltman)]

I have not been able to reboot my desktop in nearly two months. What is the fix? Do I have to reflash the BIOS? How do I ensure the desktop is bootable after I reflash? Thanks.

[Demon (demonrx)]

https://askubuntu.com/questions/1072618/could-not-prepare-boot-variable-no-space-left-on-device-grub-install-error-ef

Solved the issue for me by clearing out the dump files in /sys/firmware/efi/efivars (ubuntu 18)