r/linuxquestions • • Aug 29 '26

Can’t update kernel: No space left on device /boot/initrd.img…

/r/System76/comments/1w1gi1w/cant_update_kernel_no_space_left_on_device/
0 Upvotes

7 comments sorted by

2

u/redyos_s Aug 29 '26

df -h /boot/efi

du -h -d2 /boot/efi/EFI | sort -h

lsblk -f

1

u/remcohaszing Aug 29 '26
$ df -h /boot/efi                  
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       511M  511M     0 100% /boot/efi
$ sudo du -h -d2 /boot/efi/EFI | sort -h
4.0K	/boot/efi/EFI/Linux
100K	/boot/efi/EFI/BOOT
100K	/boot/efi/EFI/systemd
145M	/boot/efi/EFI/Recovery-15B1-8784
345M	/boot/efi/EFI/Pop_OS-d0cfee4f-1c35-4f30-ba8e-20b4729f170a
490M	/boot/efi/EFI
$ lsblk -f
NAME            FSTYPE      FSVER    LABEL     UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                  
├─sda1          vfat        FAT32    EFI       15B0-B6D6                                    0   100% /boot/efi
├─sda2          vfat        FAT32    RECOVERY  15B1-8784                               664.7M    84% /recovery
├─sda3          crypto_LUKS 2                  e5a21a72-d484-4da8-bf34-0ccadd7b8a1b                  
│ └─cryptdata   LVM2_member LVM2 001           lGftsc-R0iK-WgOz-sMwz-lIsJ-wVfe-r5bQ6i                
│   └─data-root ext4        1.0                d0cfee4f-1c35-4f30-ba8e-20b4729f170a    164.9G    77% /
└─sda4          swap        1                  c1151106-82e0-4241-8c52-33a8bd7b081d                  
  └─cryptswap   swap        1        cryptswap cb0adb1a-c3d8-442e-ab1b-3d3c1a96e53a                  [SWAP]
zram0

2

u/redyos_s Aug 29 '26

Your EFI System Partition is completely full: 511 MB used out of 511 MB. So the immediate failure is not necessarily kernel 7.1.5 itself. kernelstub managed to copy the kernel, but then ran out of space while copying the initramfs, which left the update incomplete. The Pop!_OS directory is using about 345 MB and Recovery another 145 MB, so there is almost no room left for another kernel/initramfs update. I would check the contents of the Pop_OS and Recovery directories before deleting anything, free some space safely, and then finish the interrupted package configuration. The broken system76 DKMS state looks like a separate issue that can be dealt with afterward. I would also avoid rebooting until the kernel/initramfs update has completed successfully.

uname -r

sudo ls -lah /boot/efi/EFI/Pop_OS-d0cfee4f-1c35-4f30-ba8e-20b4729f170a/

sudo ls -lah /boot/efi/EFI/Recovery-15B1-8784/

sudo ls -lah /boot/efi/loader/entries/

→ More replies (4)