Efi no more free storage space

After today’s kernel update I got the following message:

install: Errors when writing '/efi/f329784de44446948b3869b7b1d20a31/6.9.1-zen1-1-zen/linux': No more storage space available on the device
Error: could not copy '/usr/lib/modules/6.9.1-zen1-1-zen/vmlinuz' to '/efi/f329784de44446948b3869b7b1d20a31/6.9.1-zen1-1-zen/linux'.
/usr/lib/kernel/install.d/90-loaderentry-fallback.install failed with exit status 1.

➜  lsblk 
sda           8:0    1 931,5G  0 disk 
└─sda1        8:1    1 931,5G  0 part /srv/nfsv4/Share
sdb           8:16   1 931,5G  0 disk /srv/nfsv4/Filme
sdc           8:32   1 223,6G  0 disk 
└─sdc1        8:33   1 223,6G  0 part /srv/nfsv4/edit
sr0          11:0    1  1024M  0 rom  
nvme0n1     259:0    0 232,9G  0 disk 
├─nvme0n1p1 259:3    0   500M  0 part /efi
└─nvme0n1p2 259:4    0 232,4G  0 part /
nvme1n1     259:1    0 931,5G  0 disk 
└─nvme1n1p1 259:2    0 931,5G  0 part /home

➜  inxi -Faz
  Kernel: 6.9.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: initrd=\f329784de44446948b3869b7b1d20a31\6.9.1-arch1-1\initrd
    nvme_load=YES nowatchdog rw
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.2.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: EndeavourOS base: Arch Linux
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: F17 date: 03/22/2024
  Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000F
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 562 high: 2994 min/max: 400/4673 scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 400
    4: 2994 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400
    14: 400 15: 400 16: 400 bogomips: 121427
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Gigabyte
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-2,HDMI-A-2 empty: DP-1,HDMI-A-1,Writeback-1 bus-ID: 03:00.0
    chip-ID: 1002:73ff class-ID: 0300
  Display: wayland server: X.org v: with: Xwayland v: 23.2.7
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 3840x1080 display-ID: 0
  Monitor-1: DP-2 pos: right res: 1920x1080 size: N/A modes: N/A
  Monitor-2: HDMI-A-2 pos: primary,left res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.7-arch1.3
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
    LLVM 17.0.6 DRM 3.57 6.9.1-arch1-1) device-ID: 1002:73ff memory: 7.81 GiB
    unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 3 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6600 (RADV NAVI23) driver: mesa radv v: 24.0.7-arch1.3
    device-ID: 1002:73ff surfaces: xcb,xlib,wayland
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 09:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 09:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: Logitech V10 Notebook Speakers
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-1:2 chip-ID: 046d:0a10 class-ID: 0300
  API: ALSA v: k6.9.1-arch1-1 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, nfsd, systemd-timesyncd
  Local Storage: total: 3.17 TiB used: 2.18 TiB (68.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QGXA7 temp: 33.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 29.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWD110
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A8R0 scheme: MBR
  ID-4: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD110
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A8R0
  ID-5: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT240BX500SSD1
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 052 scheme: GPT
  ID-1: / raw-size: 232.39 GiB size: 227.69 GiB (97.97%)
    used: 70.05 GiB (30.8%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-2: /home raw-size: 931.51 GiB size: 915.82 GiB (98.31%)
    used: 481.11 GiB (52.5%) fs: ext4 dev: /dev/nvme1n1p1 maj-min: 259:2
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 16 GiB used: 5.8 MiB (0.0%) priority: -2
    file: /swapfile
  System Temperatures: cpu: 37.2 C mobo: 28.0 C gpu: amdgpu temp: 36.0 C
    mem: 36.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
  Memory: total: 16 GiB available: 15.47 GiB used: 3.92 GiB (25.4%)
  Processes: 361 Power: uptime: 33m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.17 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1863 libs: 413 tools: pacseek,yay pm: flatpak
    pkgs: 0 Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.26 running-in: konsole inxi: 3.3.34

Is there a way to create storage space? And if so, how do I do that?

journalctl -b -1



Do you have unused kernels installed? Uninstalling those would be the easiest way to make room.

Just check what’s filling up /efi, since it only has 500 MB.

1 Like

I have linux-lts, normal and zen kernel. I usually use zen and normal kernel.

How do i check whats filling up /efi?

Just use a file tool of your choice, but you need admin rights (e.g. Dolphin in admin mode).

This should give you a rough outline: sudo du -h --max-depth=3 /efi | sort -hr

1 Like

You may have a too small EFI partition for systemd-boot.

EnOS’ installers should, by default, create a 1000 MB EFI partition to have enough space for all the kernels.

1 Like

When I installed it three years ago, that was probably enough.
Do you think I should increase efi or should I do a new installation with at least 1Gb efi?

➜  sudo du -h --max-depth=3 /efi | sort -hr
[sudo] Passwort für swh: 
500M    /efi
499M    /efi/f329784de44446948b3869b7b1d20a31
183M    /efi/f329784de44446948b3869b7b1d20a31/6.9.1-zen1-1-zen
181M    /efi/f329784de44446948b3869b7b1d20a31/6.9.1-arch1-1
136M    /efi/f329784de44446948b3869b7b1d20a31/6.6.30-2-lts
216K    /efi/EFI
104K    /efi/EFI/systemd
104K    /efi/EFI/BOOT
40K     /efi/loader
20K     /efi/loader/entries
4,0K    /efi/EFI/Linux

You could try disabling the generation of the fallback images.

Disable the generation of the fallback initrd

Edit config file located at /etc/eos-dracut.conf or /etc/kernel-install-for-dracut.conf and set NO_DRACUT_FALLBACK to NO_DRACUT_FALLBACK="true"

This will stop future fallback initrds from being generated.

Please note that this will not remove any existing fallback initrds that already exist. When using kernel-install-for-dracut(systemd-boot), this will change automatically as new kernel updates happen. For eos-dracut(grub), you will need to remove them manually.


Depending on the disk layout, increasing the size of the EFI might be a bit of a hassle involving resizing an moving other partitions. There is always a certain risk for data loss or filesystem corruption.


Thanks, but efi is still full and as far as I can read it will not delete any existing fallbacks.

I will probably not be able to avoid a new installation with a much larger efi partition

After disabling the fallback generation in the conf file, try running sudo reinstall-kernels.

If that won’t help, you could delete them manually.

Where are they located?

Look under these directories. I guess they should be in there. I’m not on EnOS so unfortunately I cannot be more exact. Please have a look and verify.

Ok, just to be clear. I have delete all these kernerls, then do reinstall-kernels or only delete the fallbacks?


Then run sudo reinstall-kernels


 initrd
 initrd-fallback
 linux

delete initrd-fallback

Will try later for now I am getting advice from my grandchildren

1 Like

OK, when it comes to the Linux boot-magic I’m totally clueless.

But this:

183M    /efi/f329784de44446948b3869b7b1d20a31/6.9.1-zen1-1-zen

stands out as to big with 183MB. Can you do a

sudo ls -lah /efi/f329784de44446948b3869b7b1d20a31/6.9.1-zen1-1-zen

to show what’s in that directory?

➜  sudo ls -lah /efi/f329784de44446948b3869b7b1d20a31/6.9.1-zen1-1-zen
[sudo] Passwort für swh: 
insgesamt 183M
drwxr-xr-x 2 root root 4,0K 18. Mai 12:55 .
drwxr-xr-x 5 root root 4,0K 18. Mai 11:18 ..
-rwxr-xr-x 1 root root  45M 18. Mai 12:55 initrd
-rwxr-xr-x 1 root root 126M 18. Mai 11:22 initrd-fallback
-rwxr-xr-x 1 root root  14M 18. Mai 12:55 linux

Yeah, something looks off, this is my zen:

sudo ls -lah /efi/90d52f9af2d545d3a720a073d399d48d/6.9.1-zen1-1-zen
total 59M
drwx------ 2 root root 4,0K 18. Mai 12:45 .
drwx------ 6 root root 4,0K 18. Mai 12:45 ..
-rwx------ 1 root root  23M 18. Mai 12:45 initrd
-rwx------ 1 root root  23M 18. Mai 12:45 initrd-fallback
-rwx------ 1 root root  14M 18. Mai 12:45 linux

But I have no clue about those things, this has become a @dalto question. :wink:

1 Like

fallback images are for backup in case you change hardware, like mice, keyboard pci cards, etc. Since you boot fine with the normal image, and don’t change HW, it is not needed.
Also, if you don’t actually use all three kernels, you can choose one to remove.

Do as suggested to disable fallback kernels for now, so you can have a working system, and you think about enabling later.

1 Like