Kernel update problem - no space left on device

TheVE

Hey everyone, I'm having a problem I'm hoping someone can help with. After my last update, there was an error updating. See screenshot.

I don't know how to fix this. I checked installed kernels and there were 9 current and 8 lts. So I removed all but 2 current and 1 lts, but clr-boot-manager update still fails with a "no space left on device" error.

Any ideas?

Much appreciated!

pomon

Take a look at this

TheVE

As mentioned, I've already removed the old kernels. 195 free on /boot. 512MB default install size partition.

Trying to run clr-boot-manager update gives me the following

brent

TheVE . 512MB default install size partition

1GB is the standard rec now and that rec is about a year old or more.

I've done this in gparted. shrink root. add to /boot. something like that. 512 no longer sustainable.

/as I remember it/

TheVE

pomon

joe@serenity-lin ~ $ ls -lh /boot/EFI/com.solus-project/ total 194M -rwxr-xr-x 1 root root 928K Nov 10 16:24 bootloaderx64.efi -rwxr-xr-x 1 root root 152 Nov 10 16:24 BOOTX64.CSV -rwxr-xr-x 1 root root 136K Nov 10 16:24 grubx64.efi -rwxr-xr-x 1 root root 85M Nov 7 19:36 initrd-com.solus-project.current.6.16.12-323 -rwxr-xr-x 1 root root 81M Nov 7 19:36 initrd-com.solus-project.lts.6.12.52-273 -rwxr-xr-x 1 root root 14M Nov 7 19:36 kernel-com.solus-project.current.6.16.12-323 -rwxr-xr-x 1 root root 14M Nov 7 19:36 kernel-com.solus-project.lts.6.12.52-273 -rwxr-xr-x 1 root root 829K Nov 10 16:24 mmx64.efi

I should have plenty of space for updates to complete? Especially after deleting like 10 old kernels that were already there.

brent

Well, my install is from 2018!

stocc

efibootmgr just gives me nonsense. 🙁

pomon

Show after mounting /boot:

sudo clr-boot-manager mount-boot
ls -l /boot/EFI/com.solus-project/

stocc

What does efibootmgr show? (Use sudo eopkg it efibootmgr to install it if it's not already installed.)

You may just need to delete some old boot entries (sudo efibootmgr -Bb <boot entry number>) to clear some space before doing the clr-boot-manager update.

brent

TheVE Well, my install is from 2018!

that's cool!

alfisya

TheVE efibootmgr just gives me nonsense. 🙁

Post the nonsense here. You might not understand it but the person helping you might.

stocc

TheVE efibootmgr just gives me nonsense. 🙁

As @alfisya says, post the output and we may be able to help. I suspect this may point to the root of your problem.

pomon

If there’s nothing unusual in other directories with sudo du -d1 -h /boot, then even with a 512 MB partition, the update should proceed. If it doesn’t, you’ll need to look for another cause.

TheVE

I hope this makes sense to someone!

joe@serenity-lin ~ $ efibootmgr BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0009,000A,0008,0002,0003,0004 Boot0001* Solus Linux Bootloader HD(1,GPT,a508dd55-25eb-4c8d-bb9c-0041de6c95c7,0x40,0xf4240)/\EFI\COM.SOLUS-PROJECT\BOOTLOADERX64.EFI Boot0002* UEFI:CD/DVD Drive BBS(129,,0x0) Boot0003* UEFI:Removable Device BBS(130,,0x0) Boot0004* UEFI:Network Device BBS(131,,0x0) Boot0008* CD/DVD Drive BBS(CDROM,,0x0)0000474f00004e4fb9000000010000007500540053005300540063006f007200700020004300440044005600440057002000530048002d005300320034003300440000000501090003000000007fff040002010c00d041030a0000000001010600030101010600010003120a000200ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce643003000330073003500480037003600390038004c0050004e004d0050004f00200020002000200000007fff04000000424f Boot0009* UEFI OS HD(1,GPT,a508dd55-25eb-4c8d-bb9c-0041de6c95c7,0x40,0xf4240)/\EFI\BOOT\BOOTX64.EFI0000424f Boot000A* Hard Drive BBS(HD,,0x0)0000474f00004e4fbb000000010000007500530061006d00730075006e006700200053005300440020003700350030002000450056004f0020003500300030004700420000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6330053005300360057004e004800420038003600300034003500380020005a00200020002000200000007fff04000000424f00004e4fb30000000100000075005700440043002000570044003100300030003100460041004c0053002d00300030004a0037004200300000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000300ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000570020002d0044004d005700540041003600560035003600370032003900300000007fff04000000424f00004e4fad00000001000000750053005400320030003000300044004d003000300031002d0031004500520031003600340000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce620002000200020002000200020002000200020002000200034005a0033005a00440036003700300000007fff04000000424f00004e4fad00000001000000750053005400320030003000300044004d003000300031002d0031004500520031003600340000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce620002000200020002000200020002000200020002000200034005a0033005a005000410035004e0000007fff04000000424f00004e4fab000000010000006b00570044005f0042004c00410043004b00200053004e003800350030005800200032003000300030004700420000000501090002000000007fff040002010c00d041030a000000000101060001010101060000000317100001000000001b448b4b0897cf7fff040001042e00ef47642dc93ba041ac194d51d01b4ce632003200320035003000330041003000300034004100450000007fff04000000424f

And

joe@serenity-lin ~ $ sudo du -d1 -h /boot 195M /boot/EFI 20K /boot/loader 195M /boot

I appreciate everyone trying to help!

stocc

I can't see anything obvious from the efibootmgr output, though I don't completely recognise entry 000A... Sorry, I don't really have any other ideas. If you enter into the setup menu on your PC and look at the boot options, are there any extra entries that you don't need? Just guessing now...

pomon

You can also show bootctl status. Maybe it will tell us something?
So even after clearing it, you still have the same error?

TheVE

I'm not one to go through the fuss of reinstalling anymore. Haha. So I was hoping to save this install from 2018. But it's looking like maybe that's what I'll have to do. Hopefully, everything works fine until Christmas and I'll wipe and reinstall everything. 😢

`joe@serenity-lin ~ $ bootctl status
System:
Firmware: UEFI 2.60 (American Megatrends 5.13)
Firmware Arch: x64
Secure Boot: disabled
TPM2 Support: no
Measured UKI: no
Boot into FW: supported

Current Boot Loader:
Product: systemd-boot 257.10
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Load drop-in drivers
✓ Support Type #1 sort-key field
✓ Support @saved pseudo-entry
✓ Support Type #1 devicetree field
✓ Enroll SecureBoot keys
✓ Retain SHIM protocols
✓ Menu can be disabled
✓ Multi-Profile UKIs are supported
✓ Boot loader set partition information
Partition: /dev/disk/by-partuuid/a508dd55-25eb-4c8d-bb9c-0041de6c95c7
Loader: └─/EFI/COM.SOLUS-PROJECT/grubx64.efi
Current Entry: solus-current-6.16.12-323.conf

Random Seed:
System Token: not set`

TraceyC

Since you're running the current kernel, you can try removing the LTS kernel that's also installed, and then try the update again.

If you still get the same error, see how much disk space is free on your /boot partition, after mounting it

sudo clr-boot-manager mount-boot
df -h | egrep "File|boot"

It may be easiest to just resize the partition to 1GB at this point.

TheVE

TraceyC

102/512MB used. Still a no go, which really doesn't make sense to me. I'll try to resize the partition tomorrow.

Will update progress.

Thanks everyone.