Re: efivarfs_set_variable: writing to fd 8 failed
Apologies for the delayed response - really busy festive period
here... :-/
On Sat, Dec 28, 2019 at 03:39:32PM +0000, junky@mail.sheugh.com wrote:
>Dear Maintainer,
>
>Subject: efivarfs_set_variable: writing to fd 8 failed
>Package: shim-signed-common
>Version: 1.33+15+1533136590.3beb971-7
>Severity: normal
>
>Dear Maintainer,
>
>Grub threw an error message while apt was running an update:
>Setting up shim-signed-common (1.33+15+1533136590.3beb971-7) ...
>Installing for x86_64-efi platform.
>grub-install: warning: Cannot set EFI variable Boot0000.
>grub-install: warning: efivarfs_set_variable: writing to fd 8 failed: No space left on device.
>grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: No space left on device.
>grub-install: error: failed to register the EFI boot entry: No space left on device.
>dpkg: error processing package shim-signed-common (--configure):
> installed shim-signed-common package post-installation script subprocess returned error exit status 1
>dpkg: dependency problems prevent configuration of shim-signed:amd64:
> shim-signed:amd64 depends on shim-signed-common (= 1.33+15+1533136590.3beb971-7); however:
> Package shim-signed-common is not configured yet.
>
>I have an SSD and a 10Tb HGST hard drive
>
>IIRC the boot sector is the first 1Gb sector on the hard drive
>
>df says this:
>Filesystem 1K-blocks Used Available Use% Mounted on
>udev 16426340 0 16426340 0% /dev
>tmpfs 3296004 9684 3286320 1% /run
>/dev/sda2 479567536 9352844 445784256 3% /
>tmpfs 16480004 8 16479996 1% /dev/shm
>tmpfs 5120 4 5116 1% /run/lock
>tmpfs 16480004 0 16480004 0% /sys/fs/cgroup
>/dev/sda1 9745696 5220 9740476 1% /boot/efi
>/dev/sda4 960185376 12220944 899119940 2% /var
>/dev/sda5 7265425656 1530107956 5369090348 23% /home
>tmpfs 3296000 4 3295996 1% /run/user/111
>tmpfs 3296000 0 3296000 0% /run/user/1000
OK. The error here is not from failing to write to the hard
disk. grub-install is trying to write a UEFI boot variable, and that's
what is failing. This would suggest the UEFI variable storage on your
computer is full. This normally lives in NVRAM, not on disk. What
computer are you using, out of interest? There have been quite a few
bugs found over recent years with various systems not managing this
storage space well :-(.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
as meaning someone who's only ever written one device driver." -- Daniel Pead
Reply to: