Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
This bug can probably be closed now. Feedback for other reading this: 1. After rebooting the mok management was shown 2. It rebooted by itself after a minute or so 3. No password was entered, even though it was asked twice by configuration of the shim-helpers package to enter such a password 4. The machine boot sequence continued 5. Once booted, i checked to see if secure boot was enabled and if tis was running the latest kernel in boot dir: $ mokutil --sb-state SecureBoot enabled (ok) $ uname -a Linux blauwbok 5.10.0-0.bpo.8-amd64 #1 SMP Debian 5.10.46-2~bpo10+1 (2021-07-22) x86_64 GNU/Linux (which was the latest installed) hth, Wim
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
Steve McIntyre schreef op vr 20-08-2021 om 14:50 [+0100]: > On Fri, Aug 20, 2021 at 03:40:48PM +0200, Wim Bertels wrote: > > Steve McIntyre schreef op vr 20-08-2021 om 14:29 [+0100]: > > > Nod. The problem is that your system is failing to create/update > > > an > > > EFI boot variable in its NVRAM. The most common issue that causes > > > this > > > is system log reports in /sys/fs/pstore/ . Could you check and > > > see if > > > there are any files there please? > > > > Yes, there are many files, all from 'nov 7 2019' which could be the > > installation date. > > > > # ls /sys/fs/pstore/ -altr > > totaal 0 > > -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250037001 > > -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250036001 > > -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250035002 > > -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250035001 > > -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250034002 > > > > An example of the content, most of them about nouveau: > > OK, that's junk that you can simply delete. If you do that, things > should clear up for you. Depending on the firmware of your computer > (and its handling of EFI variables), you *might* need to reboot for > the space to free up completely. In that case, I'd recomment that you > have an installer USB (or similar) handy just in case things don't > > boot. > ok, emptied it(, without rebooting) /sys/fs/pstore# rm dmesg-efi-1573* That seemed to do trick, --configure gives no errors, just reporting this, in case the system doesn't reboot (password for eufi change was asked) # dpkg --configure shim-helpers-amd64-signed Instellen van shim-helpers-amd64-signed (1+15.4+5~deb10u1) ... Installeren voor x86_64-efi-platform. Installatie is afgerond. Er werden geen fouten gerapporteerd. # dpkg --configure shim-signed Instellen van shim-signed:amd64 (1.36~1+deb10u2+15.4-5~deb10u1) ... Installeren voor x86_64-efi-platform. Installatie is afgerond. Er werden geen fouten gerapporteerd. hth, Wim
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
On Fri, Aug 20, 2021 at 03:40:48PM +0200, Wim Bertels wrote: >Steve McIntyre schreef op vr 20-08-2021 om 14:29 [+0100]: >> >> Nod. The problem is that your system is failing to create/update an >> EFI boot variable in its NVRAM. The most common issue that causes >> this >> is system log reports in /sys/fs/pstore/ . Could you check and see if >> there are any files there please? > >Yes, there are many files, all from 'nov 7 2019' which could be the >installation date. > ># ls /sys/fs/pstore/ -altr >totaal 0 >-r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250037001 >-r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250036001 >-r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250035002 >-r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250035001 >-r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250034002 > >An example of the content, most of them about nouveau: OK, that's junk that you can simply delete. If you do that, things should clear up for you. Depending on the firmware of your computer (and its handling of EFI variables), you *might* need to reboot for the space to free up completely. In that case, I'd recomment that you have an installer USB (or similar) handy just in case things don't boot. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say." -- Edward Snowden
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
Steve McIntyre schreef op vr 20-08-2021 om 14:29 [+0100]: > Control: reassign -1 grub-efi-amd64 > > Hi wim, > > On Tue, Aug 17, 2021 at 03:22:49PM +0200, wim wrote: > > Package: shim-helpers-amd64-signed > > Version: 1+15.4+5~deb10u1 > > Severity: normal > > > > Hello, > > > > This is the setup: > > OK, this is a problem being reported by grub-install, called by > shim-helpers-amd64-signed as it's installed. Reassigning to one of > the > grub packages. > > > # df -h > > BestandssysteemGrootte Gebruikt Besch Geb% > > Aangekoppeld op > > udev 32G0 32G 0% > > /dev > > .. > > /dev/mmcblk0p13,7G 64K 3,7G 1% > > /media/wim/MICROSD > > /dev/sr0 88M 88M 0 100% > > /media/wim/20190318_164558 > > > > So /boot/efi and /boot have free space > > Nod. The problem is that your system is failing to create/update an > EFI boot variable in its NVRAM. The most common issue that causes > this > is system log reports in /sys/fs/pstore/ . Could you check and see if > there are any files there please? Yes, there are many files, all from 'nov 7 2019' which could be the installation date. # ls /sys/fs/pstore/ -altr totaal 0 -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250037001 -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250036001 -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250035002 -r--r--r-- 1 root root 1799 nov 7 2019 dmesg-efi-157315250035001 -r--r--r-- 1 root root 1800 nov 7 2019 dmesg-efi-157315250034002 An example of the content, most of them about nouveau: # cat /sys/fs/pstore/dmesg-efi-157332678916001 Oops#1 Part16 <4>[ 105.363372] ? __switch_to+0x7a/0x3e0 <4>[ 105.363373] ? __switch_to_asm+0x34/0x70 <4>[ 105.363374] pm_runtime_work+0x82/0x90 <4>[ 105.363375] process_one_work+0x1a7/0x3b0 <4>[ 105.363375] worker_thread+0x30/0x390 <4>[ 105.363376] ? create_worker+0x1a0/0x1a0 <4>[ 105.363377] kthread+0x112/0x130 <4>[ 105.363378] ? __kthread_parkme+0x70/0x70 <4>[ 105.363378] ret_from_fork+0x1f/0x40 <4>[ 105.363379] ---[ end trace b62441a5f9a44a7c ]--- <2>[ 105.364066] nouveau :01:00.0: tmr: stalled at <4>[ 105.364067] [ cut here ] <4>[ 105.364067] nouveau :01:00.0: timeout <4>[ 105.364096] WARNING: CPU: 5 PID: 557 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmtu102.c:47 tu102_vmm_flush+0x128/0x140 [nouveau] <4>[ 105.364097] Modules linked in: nls_utf8 isofs fuse ctr ccm rfcomm cmac snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress arc4 iwlmvm intel_rapl mac80211 bnep iwlwifi btusb btrtl btbcm btintel bluetooth cfg80211 drbg ansi_cprng ecdh_generic hp_wmi ecc sparse_keymap snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_realtek kvm nls_ascii nls_cp437 snd_hda_codec_generic vfat irqbypass efi_pstore fat ledtrig_audio intel_cstate snd_usb_audio uvcvideo snd_hda_intel cdc_ether videobuf2_vmalloc usbnet videobuf2_memops snd_hda_codec intel_uncore videobuf2_v4l2 videobuf2_common snd_usbmidi_lib r8152 snd_rawmidi snd_hda_core snd_seq_device mii intel_rapl_perf efivars videodev snd_hwdep joydev rtsx_pci_ms iTCO_wdt snd_pcm mei_me iTCO_vendor_support serio_raw intel_wmi_thunderbolt pcspkr watchdog wmi_bmof pcc_cpufreq tpm_crb memstick sg usblp media snd_timer rfkill mei The ones that are not: # cat $(grep -L nouv * ) Oops#1 Part2 <4>[ 200.823189] RDX: 0029 RSI: 00b4 RDI: c03e <4>[ 200.823190] RBP: aa238675bd98 R08: R09: <4>[ 200.823191] R10: R11: R12: <4>[ 200.823192] R13: 7fff R14: 9530e3ea83c0 R15: <4>[ 200.823193] ? common_interrupt+0xa/0xf <4>[ 200.823195] ? __bpf_prog_run32+0x39/0x60 <4>[ 200.823196] ? __seccomp_filter+0x6a/0x680 <4>[ 200.823198] ? __seccomp_filter+0x7a/0x680 <4>[ 200.823199] ? devkmsg_read+0x73/0x2c0 <4>[ 200.823200] ? devkmsg_read+0x165/0x2c0 <4>[ 200.823202] ? syscall_trace_enter+0x192/0x2b0 <4>[ 200.823204] ? do_syscall_64+0x104/0x130 <4>[ 200.823205] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 <4>[ 200.823206] Modules linked in: snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress arc4 intel_rapl iwlmvm mac80211 btusb snd_hda_codec_hdmi btrtl btbcm btintel bluetooth uvcvideo x86_pkg_temp_thermal videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iwlwifi snd_hda_codec_realtek videobuf2_common intel_powerclamp videodev coretemp snd_hda_codec_generic kvm_intel ledtrig_audio cfg80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm rtsx_pci_ms memstick media kvm snd_timer processor_thermal_device
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
Control: reassign -1 grub-efi-amd64 Hi wim, On Tue, Aug 17, 2021 at 03:22:49PM +0200, wim wrote: >Package: shim-helpers-amd64-signed >Version: 1+15.4+5~deb10u1 >Severity: normal > >Hello, > >This is the setup: OK, this is a problem being reported by grub-install, called by shim-helpers-amd64-signed as it's installed. Reassigning to one of the grub packages. ># df -h >BestandssysteemGrootte Gebruikt Besch Geb% >Aangekoppeld op >udev 32G0 32G 0% /dev >tmpfs 6,3G 13M 6,3G 1% /run >/dev/mapper/root_ssd-lv_root_ssd_crypt1,9T 1,6T 152G 92% / >tmpfs 32G 92K 32G 1% /dev/shm >tmpfs 5,0M 4,0K 5,0M 1% /run/lock >tmpfs 32G0 32G 0% >/sys/fs/cgroup >/dev/loop0165M 165M 0 100% >/snap/gnome-3-28-1804/161 >/dev/loop1100M 100M 0 100% >/snap/core/11316 >/dev/nvme1n1p1504M 368M 112M 77% /boot >/dev/loop2 72M 72M 0 100% >/snap/carnet/15 >/dev/nvme0n1p1511M 49M 463M 10% /boot/efi >/dev/loop4159M 159M 0 100% >/snap/codium/166 >/dev/loop3163M 163M 0 100% >/snap/gnome-3-28-1804/145 >/dev/loop6 56M 56M 0 100% >/snap/core18/2128 >/dev/loop5 56M 56M 0 100% >/snap/core18/2074 >/dev/loop8100M 100M 0 100% >/snap/core/11420 >/dev/loop7 66M 66M 0 100% >/snap/gtk-common-themes/1515 >/dev/loop9151M 151M 0 100% >/snap/codium/162 >/dev/loop10 128K 128K 0 100% >/snap/hello-world/29 >/dev/loop1165M 65M 0 100% >/snap/gtk-common-themes/1514 >/dev/loop1242G 42G 0 100% >/home/wim/ucll/zolder_gt >/dev/loop1372M 72M 0 100% >/snap/carnet/16 >/dev/sdb1 3,6T 3,2T 307G 92% >/mnt/terra_1_5_story >/dev/mapper/data_1T 856G 254G 558G 32% /data_1T >tmpfs 6,3G 64K 6,3G 1% >/run/user/1000 >/dev/mmcblk0p13,7G 64K 3,7G 1% >/media/wim/MICROSD >/dev/sr0 88M 88M 0 100% >/media/wim/20190318_164558 > >So /boot/efi and /boot have free space Nod. The problem is that your system is failing to create/update an EFI boot variable in its NVRAM. The most common issue that causes this is system log reports in /sys/fs/pstore/ . Could you check and see if there are any files there please? -- Steve McIntyre, Cambridge, UK.st...@einval.com "I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop" -- Vivek Das Mohapatra
Bug#992335: shim-helpers-amd64-signed: grub install: error: failed to register the EFI boot entry, no space left on device
Package: shim-helpers-amd64-signed Version: 1+15.4+5~deb10u1 Severity: normal Hello, This is the setup: # df -h BestandssysteemGrootte Gebruikt Besch Geb% Aangekoppeld op udev 32G0 32G 0% /dev tmpfs 6,3G 13M 6,3G 1% /run /dev/mapper/root_ssd-lv_root_ssd_crypt1,9T 1,6T 152G 92% / tmpfs 32G 92K 32G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 32G0 32G 0% /sys/fs/cgroup /dev/loop0165M 165M 0 100% /snap/gnome-3-28-1804/161 /dev/loop1100M 100M 0 100% /snap/core/11316 /dev/nvme1n1p1504M 368M 112M 77% /boot /dev/loop2 72M 72M 0 100% /snap/carnet/15 /dev/nvme0n1p1511M 49M 463M 10% /boot/efi /dev/loop4159M 159M 0 100% /snap/codium/166 /dev/loop3163M 163M 0 100% /snap/gnome-3-28-1804/145 /dev/loop6 56M 56M 0 100% /snap/core18/2128 /dev/loop5 56M 56M 0 100% /snap/core18/2074 /dev/loop8100M 100M 0 100% /snap/core/11420 /dev/loop7 66M 66M 0 100% /snap/gtk-common-themes/1515 /dev/loop9151M 151M 0 100% /snap/codium/162 /dev/loop10 128K 128K 0 100% /snap/hello-world/29 /dev/loop1165M 65M 0 100% /snap/gtk-common-themes/1514 /dev/loop1242G 42G 0 100% /home/wim/ucll/zolder_gt /dev/loop1372M 72M 0 100% /snap/carnet/16 /dev/sdb1 3,6T 3,2T 307G 92% /mnt/terra_1_5_story /dev/mapper/data_1T 856G 254G 558G 32% /data_1T tmpfs 6,3G 64K 6,3G 1% /run/user/1000 /dev/mmcblk0p13,7G 64K 3,7G 1% /media/wim/MICROSD /dev/sr0 88M 88M 0 100% /media/wim/20190318_164558 So /boot/efi and /boot have free space Other background: # dmesg | grep "EFI v" [0.00] efi: EFI v2.60 by HP # efibootmgr -v BootCurrent: Timeout: 0 seconds BootOrder: ,0001,0003,0004,0005,0006,0002 Boot* debian HD(1,GPT,2f88813d-e6d3-41c2-91ef-4f100bbcb1e7,0x800,0x10)/File(\EFI\debian\shimx64.efi)ISPH Boot0001* ST1000LM049-2GH172 PciRoot(0x0)/Pci(0x17,0x0)/Sata(3,65535,0)N.YMR,Y.ISPH Boot0002 Pen Drive CE775D2724450050 PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/USB(0,0)/USB(0,0)/USB(2,0)N.YMR,Y.ISPH Boot0003* KXG60ZNV1T02 TOSHIBA-89JA61I4KS1N PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,8C-E3-8E-03-00-1B-80-FC)N.YMR,Y.ISPH Boot0004* Seagate Expansion Desk NA8F8PK8 PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(2,0)/USB(2,0)/USB(0,0)N.YMR,Y.ISPH Boot0005 Expansion PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(3,0)/USB(1,0)/MAC(040e3cb07f7b,0)/IPv4(0.0.0.00.0.0.0,0,0)N.YMR,Y.ISPH Boot0006 Expansion PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(3,0)/USB(1,0)/MAC(040e3cb07f7b,0)/IPv6([::]:<->[::]:,0,0)N.YMR,Y.ISPH # cat /proc/mdstat Personalities : [raid0] [linear] [multipath] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid0 nvme0n1p2[1] nvme1n1p2[0] 1999093760 blocks super 1.2 512k chunks The errors (and warnings) given are (dutch): # apt upgrade .. I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-0.bpo.8-amd64 /etc/kernel/postinst.d/dkms: Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.10.0-0.bpo.8-amd64 setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly. W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915 W: Possible missing firmware
