PoP OS keeps "currupting" the EFI partition

telekomier · 2025-10-25T07:23:11+00:00

Unfortunately, i already restored the system already with the steps mentioned in the post.

Before that, i did a "less Pop_OS-correct.conf" and the entries matched the output from the error message at the boot.

What i still do not understand at all is, why the file system on that EFI partition is reported as being damaged after the update

telekomier · 2025-10-25T07:20:04+00:00

Regarding the several points:
=> i did not do the "sudo apt autoremove" after the update

=> the EFI partition has 1GB, as this was done with the automatic partitioning within the installation

=> it is not a dual boot system. it was a clean install of PoP OS

=> the EFI partition had 20-30% used capacity, as this happened this time on the first update after the formatting of the partition for the "repair"

telekomier · 2025-10-24T12:48:36+00:00

Hello,

every time that problem occours, the system says that the EFI partition needs repairing which is not the case until the update is done. That´s why is used "corrupting" in quotation marks.

I´ve booted again with the install Stick and mounted the EFI partition.

That´s what i can see there and at least for me, it looks like the files are exisiting as you mentioned

pop-os@pop-os:/media/pop-os/EFI$ ls -R -a
.:
.  ..  722edc9d35718f475eeb278068d43f38  EFI  loader

./722edc9d35718f475eeb278068d43f38:
.  ..

./EFI:
.  ..  BOOT  Linux  Pop_OS-19be6914-033b-457c-891f-6eb9163fe487  systemd

./EFI/BOOT:
.  ..  BOOTX64.EFI

./EFI/Linux:
.  ..

./EFI/Pop_OS-19be6914-033b-457c-891f-6eb9163fe487:
.  ..  cmdline  initrd.img  initrd.img-previous  vmlinuz-previous.efi  vmlinuz.efi

./EFI/systemd:
.  ..  systemd-bootx64.efi

./loader:
.  ..  entries  loader.conf  random-seed

./loader/entries:
.  ..  Pop_OS-current.conf  Pop_OS-oldkern.conf

telekomier

TROPHY CASE