Failed to open \EFI\com.solus-project - Not Found

silke

Axios What happens if you run:

sudo clr-boot-manager mount-boot
sudo bootctl --esp-path=/boot --no-pager

Axios

silke I had do the latest system update to install efibootmngr so not sure what prob fixed it
but if I run (sudo bootctl --no-pager) I get the following ouput with no error.
Thanks I learned some stuff.
(Note) Solus only thing installed on this laptop Oops did run those two commands.

System:
      Firmware: UEFI 2.40 (INSYDE Corp. 24600.259)
 Firmware Arch: x64
   Secure Boot: disabled
  TPM2 Support: no
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 254
     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
               ✓ Boot loader sets ESP information
          ESP: /dev/disk/by-partuuid/2da6a45a-624b-42a1-8b5b-1bc43ba1c57a
         File: └─/EFI/com.solus-project/grubx64.efi

Random Seed:
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/2da6a45a-624b-42a1-8b5b-1bc43ba1c57a)
         File: └─/EFI/BOOT/BOOTX64.EFI
systemd-boot not installed in ESP.

Boot Loaders Listed in EFI Variables:
        Title: Solus Linux Bootloader
           ID: 0x0006
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/2da6a45a-624b-42a1-8b5b-1bc43ba1c57a
         File: └─/EFI/com.solus-project/bootloaderx64.efi

        Title: Lenovo Recovery System
           ID: 0x0003
       Status: active
    Partition: /dev/disk/by-partuuid/42241219-3ea3-4555-a604-dd3df018064a
         File: └─/EFI/Microsoft/Boot/LrsBootMgr.efi

        Title: Lenovo Recovery System
           ID: 0x0004
       Status: active
    Partition: /dev/disk/by-partuuid/42241219-3ea3-4555-a604-dd3df018064a
         File: └─/EFI/Microsoft/Boot/LrsBootMgr.efi

        Title: Windows Boot Manager
           ID: 0x0005
       Status: active
    Partition: /dev/disk/by-partuuid/d73affd3-b1c1-40a4-89d0-b35db0d58268
         File: └─/EFI/Microsoft/Boot/bootmgfw.efi

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/2da6a45a-624b-42a1-8b5b-1bc43ba1c57a)
        token: solus

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: Solus 4.5 Resilience (Solus-current-6.9.10-295.conf)
           id: Solus-current-6.9.10-295.conf
       source: /boot//loader/entries/Solus-current-6.9.10-295.conf
        linux: /boot//EFI/com.solus-project/kernel-com.solus-project.current.6.9.10-295
       initrd: /boot//EFI/com.solus-project/initrd-com.solus-project.current.6.9.10-295
      options: root=PARTUUID=dbc0580c-2a7e-4c71-bf06-e7b5dc2a3072 quiet splash rw resume=UUID=5da8e90c-63c9-4270-bd22-e52563a369ce

If I run (sudo env CBM_DEBUG=1 clr-boot-manager mount-boot) now this is the ouput

[INFO] cbm (../src/bootman/bootman.c:L787): Current running kernel: 6.9.10-295.current
[INFO] cbm (../src/bootman/sysconfig.c:L179): Discovered UEFI ESP: /dev/disk/by-partuuid/2da6a45a-624b-42a1-8b5b-1bc43ba1c57a
[INFO] cbm (../src/bootman/sysconfig.c:L256): Fully resolved boot device: /dev/sda1
[DEBUG] cbm (../src/bootman/bootman.c:L141): shim-systemd caps: 0x26, wanted: 0x26
[DEBUG] cbm (../src/bootman/bootman.c:L156): UEFI boot now selected (shim-systemd)
[INFO] cbm (../src/bootman/bootman.c:L503): Checking for mounted boot dir
[INFO] cbm (../src/bootman/bootman.c:L555): Mounting boot device /dev/sda1 at /boot
[SUCCESS] cbm (../src/bootman/bootman.c:L568): /dev/sda1 successfully mounted at /boot

silke

BuzzPCSOS

I wonder now if it was there all along but just cleared so fast that I never noticed it before week 12 & 13 updates when the time it displayed on the screen suddenly became several seconds.

Strange, I don't see anything in the changed packages that I would suspect of causing this. It seems harmless anyway, so I'm not going to keep digging 😅

Many thanks for support and advice from everyone. There may still be an answer to my question but don't beat yourselves up if you can't beat this one as it could just be down to old hardware.

Glad to be of help!

HomerSp

Looking through the systemd boot/efi code, the message doesn't seem to be from there, so my guess would be that it's the UEFI/firmware. Could you run efibootmgr (eopkg install if necessary) and post the output here?

BuzzPCSOS

HomerSp I'm not sure if this was aimed at me or @Axios
Anyhow here is my efibootmgr output just in case. Cheers.

BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0007,0000,0001,0002,0003,0004
Boot0000* Diskette Drive        BBS(Floppy,,0x0)
Boot0001* Internal HDD  BBS(HD,,0x0)50303a2053616d73756e6720535344203834302045564f2035303047422000
Boot0002* USB Storage Device    BBS(USB,,0x0)
Boot0003* CD/DVD/CD-RW Drive    BBS(CDROM,,0x0)50313a204f707469617263204456442b2f2d52572041442d37353835482000
Boot0004  Onboard NIC   BBS(Network,,0x0)
Boot0007* Solus Linux Bootloader        HD(1,GPT,c00902bf-9665-4184-bd51-4123b308a4b3,0x1000,0x200000)/\EFI\com.solus-project\bootloaderx64.efi

HomerSp

BuzzPCSOS Thanks, and sorry, that message was indeed for you 🙂 That output looks completely normal to me, so I'm not sure.
The error message is a bit weird though, for one it's missing the leading backslash, and secondly it's missing the actual efi loader file from the path name. Since it works I wouldn't worry about things breaking though, probably just some bug in the UEFI firmware.

BuzzPCSOS

HomerSp Thank you for your input and reassurance. My laptop is something of a museum piece as it is well over ten years old now. It has been dragged into the present with a F2FS formatted SSD and a new WiFi card that works better than the original (sometimes).
I saw a similar glitch on some old low end Windows laptops about ten years ago which I never really got to the bottom of. At the time I put it down to more information needing to be read at boot after upgrading the OS, probably just leaving the hardware struggling to metaphorically catch it's breath. Hence the "not found" message and then just carrying on as normal after a short pause. A rather artistic explanation instead of a technical one but that is the way it all felt to me. ;-]]
That's progress I suppose, my powerful fifth generation i5 processor has got old and now rates as low end. I will have to ignore these minor inconveniences because I kind of like the weighty feel of it, the built-in DVD writer and I still have an unused spare battery. There is plenty of life left there yet!

Axios

BuzzPCSOS Thanks for posting that question I watch threads and prob get myself
in more trouble than I should..lol

Again thanks.

Axios

Kinda interesting checked my lenovo t420 the other laptop was lenovo to
And had the same issue on it.
So ran these two commands sudo clr-boot-manager mount-boot sudo bootctl --esp-path=/boot --no-pager
and the issue was again fixed.
Seems to have a performance effect somewhat on laptops more so on the slower machine.
Dont know if thats poss but appears that way.

Again thanks silke.

Note not sure how why or when the issue

Axios

silke Just did the #30 update today and this error returned.
When I run the (sudo bootctl --no-pager) command it says (Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.) -In red.
So Not sure now. maybe its not something to worry about?
Those other two commands still get rid of the error.

Note Updated my t420 this more and again the error returned so I guess updates is doing it for some reason.
Running those 2 commands again got rid of error.
(Was just checking make sure it wasnt just the one computer all are budgie)

silke

Axios

When I run the (sudo bootctl --no-pager) command it says (Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.) -In red.

Did you execute sudo clr-boot-manager mount-boot before bootctl? bootctl is never going to work without sudo clr-boot-manager mount-boot, as that mounts the EFI system partition for bootctl. Note that those are purely diagnostic commands, and shouldn't change anything about your system.

What issues are you having aside from the bootctl error?

As for the old entries (I completely missed that last time): you have both LTS and current kernel installed, so that is somewhat expected. Can you give the output of sudo clr-boot-manager list-kernels?

Axios

silke Yes you are right I checked again error is still there so not sure what went on last time then.
I ran the commands as you listed.
But as you can see it went away because I pasted it in a reply but its back now (Just info)
As far as I know everything is working have not done the latest update.
It shows up on all my budgie installs all on lenovo laptops.

Need anymore info let me know.

com.solus-project.current.6.9.10-295
com.solus-project.lts.6.6.41-249

silke

Axios In that case I wouldn't worry about it, as long as your kernels update there's not much to worry about 🙂

Axios

silke Ok and thanks

BuzzPCSOS

@Axios @silke @HomerSp This is a very old thread but I did some more digging to try and work out what was wrong.
When I boot from the a USB (ventoy or Etcher not tried anything else) or a freshly burned DVD using Solus 4.6 I see the same warning just before the start Solus B+W loading screen comes up. This means that even though I selected UEFI boot the system has entered into a fallback legacy environment.
I have confirmed this by running a UEFI boot (GPT) into the Live environment. At this point I can access the root partition on the hard drive.
If I now reboot and choose Legacy boot (MBR) into the Live environment I can still access the root partition on the hard drive. If the hard drive had been a GPT install I would not be able to see the drive contents. The drive partitions were all set up by using the 'Erase Disc' option in the installer and identified the install as UEFI and GPT.
I think the problem here is with old hardware which does not work well with the long path name to the .efi file required to enter into the correct UEFI state.
If I try to manually set the BIOS path to /EFI/com.solus-project/grubx64.efi the result truncates to /EFI/com.solus-project/grubx64.e - the end of the address is lost.
An internet search indicates that there are many other BIOS/UEFI computers out there with similar issues but so far I have not had much luck finding a fix. The search phrase I ended up using was "Failed to open \EFI\" which opens up the search to a much wider field.
For the moment I have installed in Legacy and am using GRUB which seems to work well enough.

Axios

BuzzPCSOS I got the computers will have to dust off old laptop and see if I run into
issues installing.
I ran a search got dizzy and closed it for now..lol
Not sure why you having all the GPT issues.
But I can say this since I have been using newer hardware have seen my issues go down it seems to be more forgiving in that respect. (But I know what you are saying)
Little quirk somewhere prob bios related or something who knows (that all I can think of at the moment)

BuzzPCSOS

Axios it kind of looks like the bios has a maximum filename length threshold. Now I want to install windows again in UEFI because I know that worked, so that I can look at the efi boot address set in the bios for that. I'm guessing the address for the .efi file would be shorter.
It would be interesting to be able to rename the grub64.efi file to something shorter and then try pointing my bios at that. If it didn't wreck my computer it would certainly prove my theory one way or the other 😄. Unfortunately not sure I would be too confident working with the efi partition. These things are meant to be hard to access for our own protection.

Axios

BuzzPCSOS https://uefi.org/specs/UEFI/2.10/13_Protocols_Media_Access.html
The firmware automatically creates handles for any block device that supports the following file system formats:

FAT12

FAT16

FAT32

I would think file length would not be a problem
interesting

BuzzPCSOS

Axios Agreed. Although the Windows path is much simpler \EFI\Microsoft\Boot\bootmgfw.efi
I wonder if it could be that simple, just dumb down where Solus puts it's .efi loader.
Almost definitely a bios issue, as you say more modern UEFI machines have considerably less issues and they seem to enter UEFI without any issues. Although most boot so quickly that only eagle eyes would spot the Failed to open message.
Back in the days of BIOS/UEFI combined loaders there were considerably less universal standards so this sort of fallout figures.

BuzzPCSOS

Axios So a little more.
I compared the path for Windows UEFI boot with the path for Solus and finally with the path that my BIOS returns if I try to navigate to the .efi file manually
\EFI\Microsoft\Boot\bootmgfw.efi /EFI/com.solus-project/grubx64.efi /EFI/com.solus-project/grubx64.e

The number of characters in the Windows path = 32
The number of characters in the Solus path = 34
The number of characters that my BIOS truncates the path to = 32
This looks to me like this is the problem, whatever the install software sets the path to does not matter because my
BIOS only recognises the first 32 characters. If it is more than that it cannot find the .efi file and displays a "failed to open" message and drops back into a hybrid state, where the installer will go through the motions of creating a GPT install complete with an efi boot partition but the format of the drive will be MBR.

brent

BuzzPCSOS I compared the path for Windows UEFI boot with the path for Solus and finally with the path that my BIOS returns if I try to navigate to the .efi file manually

wow. fantastic work. where did you see the line/EFI/com.solus-project/grubx64.e ? In the file manager? Or in the bios? 32 can't be that common, can it, as far as bios limitations?
again, nice find.

Axios

BuzzPCSOS I see what your saying you got figure a process of elimination to really be sure

/EFI/com.solus-project/grubx64.efi
/EFI/com.solus-project/grubx64.e
If this is what you mean that it just deleted the (fi) am having hard time wrapping that around my head
something just doesnt ring right.
I say that because gubx64.efi is short filename why would it care how deep or what the directories are called?

(Got to ponder)
Note if grux was wildly long filename i can see it shorting it (at least with early windows kinda how it worked)

« Previous Page Next Page »