Why bootctl command shows "Failed to open /boot/efi/loader/loader.conf": No such file or directory ?

Solution Verified - Updated -

Issue

  • Post bootctl execution system fails to open /boot/efi/loader/loader.conf.

      # bootctl 
      System:
         Firmware: n/a (n/a)
      Secure Boot: disabled
       Setup Mode: user
    
       Current Loader:
          Product: n/a
              ESP: n/a
             File: └─n/a
    
        Boot Loader Binaries:
              ESP: /boot/efi     (/dev/disk/by-partuuid/333bdab6-c180-4985-921c-10dd64b575da)
        systemd-boot not installed in ESP.
             File: └─/EFI/BOOT/BOOTX64.EFI
    
        Boot Loader Entries in EFI Variables:
            Title: Red Hat Enterprise Linux
               ID: 0x0003
           Status: active, boot-order
        Partition: /dev/disk/by-partuuid/333bdab6-c180-4985-921c-10dd64b575da
             File: └─/EFI/redhat/shimx64.efi
    
        Default Boot Entry:
         Failed to open "/boot/efi/loader/loader.conf": No such file or directory
         Failed to read boot config from "/boot/efi/loader/loader.conf": No such file or directory
        Failed to load bootspec config from "/boot/efi/loader": No such file or directory
    

Environment

  • Red Hat Enterprise Linux 8
  • UEFI

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content