zmaint Well here is one answer I suppose. Here is a screenshot from a junk box laptop that I installed Solus on last year. I'm guessing that I set \root as the boot partition by mistake. Certainly no chance of the EFI partition getting too full😄

Looked at my main laptop and tablet and both have about 200MB EFI used space in a 1GB partition. Both have intel embedded graphics so it looks like NVIDIA is your problem and the link supplied by @Sebastian is the the one you need to watch for answers.

      BuzzPCSOS That's what I'm thinking. Looks like for whatever reason that clr-boot-manager is failing to always delete those older kernels on nvidia systems. Unsure why, but there's a ticket already open so hoping it gets fixed sooner than later. Doesn't seem like just increasing partition size is a long term fix if it just continues to stockpile old kernels.

        I have one older Solus system with 512 MB EFI partition (now default should be 1GB) and I have 2 kernels installed - current and LTS. Few months ago I got an error during update. I managed to solve it by removing older kernel.

        I would just reinstalled Solus with bigger EFI partition but I am lazy. I think next time I install Solus I will set 2GB EFI partition just in case 🙂

          Solarmass My PC has had Solus Plasma on it for 4+ years, Nvidia the entire time, and this is the first time I've ever had an issue or more than 2 kernels installed. Something is different.

              zmaint My PC has had Solus Plasma on it for 4+ years, Nvidia the entire time, and this is the first time I've ever had an issue or more than 2 kernels installed. Something is different.

              Solarmass has Budgie. @Sebastian noted this was a known bug (I think its DE-exclusive personally but I have no proof but anecdotal; or Nvidia) where the mechanism to remove the last kernels after an update stopped working in certain cases, leading to accumulation.
              I think Solus will have this fixed soon -Serebit is on it, with Tracy, probably more.

              That said @Solarmass , 512MB should house the kernels if that failed "mechanism" I am calling it is working. (That's why I said DE-specific maybe). But you still have to make it bigger sometime! I have to think back a couple years when Solus Officially Announced their endorsement of a 1GB boot partition. I don't remember a Forum "how the hell do I do that?"-thread. I remember searching for it and doing it myself in a live environment with gparted. And not worrying since.

                Just checked, and my EFI is still 512 MB, but so far no issues. Running Solus Budgie.

                Happened only one time to me. Solus Budgie and AMD GPU 🙂

                I'm quite worried as I'm a Budgie Nvidia user.

                1. Can someone kindly advise me what is the definitive way to check if I'm affected by this bug?

                2. How do I check the current status of my EFI partition, to what extent has it already been filled up, percentage-wise?

                3. How can I safely remove all the old unused kernels and their correspondings nvidia files?

                Thank you.

                  snowee

                  can only answer #2:

                  this ^ is my solus in gparted.
                  have a 1GB boot and I' using 183MB of it.

                  1 and 3, I don't know

                      snowee
                      Check partition size.
                      sudo clr-boot-manager mount-boot
                      sudo du -d1 -h /boot

                      See installed kernels.
                      sudo clr-boot-manager list-kernels
                      And/or
                      ls /boot/EFI/com.solus-project/

                      If needed you can then delete the old kernels, typically you should have 2 currently installed, or maybe 3 if you also keep LTS around.
                      sudo clr-boot-manager remove-kernel <kernel-name>

                      Be careful to not try and delete the kernel you are currently using. Might want to confirm what you're booted with before removing stuff.
                      uname -r

                      I don't know how to see if the bug impacts you other than checking to see if you have an excessive amount of kernels. The older ones should be getting deleted by clr-boot-manager. They're working on figuring that out and getting it corrected.

                          brent
                          My 1GB EFI Partition is 38% full.
                          Is this considered normal?

                            zmaint

                            sudo clr-boot-manager list-kernels

                            gives me the following output :

                            * com.solus-project.current.6.12.19-315
  com.solus-project.current.6.12.17-314

                            is this considered normal?

                              Yes to both.

                              The cases I have seen with a full EFI/boot partition is because of a combination of these things:

                              1. They did not follow the recommended 1GB minimum advice.
                              2. They have installed -current and -lts kernels.
                              3. They multi-boot with multiple different operating systems each of which will take up their own space in the partition.