grub-install: error: efibootmgr failed to register the boot entry: No such file or directory

Hey all! I have been trying for the last while to revive a Manjaro install that I have on my laptop. The system configuration before was Windows 10/Manjaro/Ubuntu, with my system using Ubuntu's GRUB. However, my Ubuntu OS got borked and I decided to migrate all my working files to Manjaro and delete the ubuntu partition and extend the Manjaro one (smart right? :stuck_out_tongue:) However, as I anticipated, the Ubuntu grub was broken because Ubuntu is gone. However, I have been following the Restore the GRUB Bootloader article, hoping that I can help my Manjaro install's GRUB to take over...

After trying relentlessly to follow the Grub Rescue article, when I run:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck

I get the response that efibootmgr cannot complete the task because there is no file or directory. Any help would be greatly appreciated!

can you boot on iso USB manjaro
open a terminal and a browser on this topic

inxi -Fxxxza
sudo parted -l
sudo efibootmgr -v

inxi -Fxxxza

System:    Host: manjaro-gnome Kernel: 5.6.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC driver=free 
           nouveau.modeset=1 i915.modeset=1 radeon.modeset=1 misobasedir=manjaro 
           misolabel=MANJARO_GNOME_2001 quiet systemd.show_status=1 apparmor=1 security=apparmor 
           Desktop: Gnome 3.36.2 wm: gnome-shell dm: GDM 3.34.1 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: XPS 15 9560 v: N/A serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: Dell model: 05FFDN v: A00 serial: <filter> UEFI: Dell v: 1.18.0 date: 11/17/2019 
Battery:   ID-1: BAT0 charge: 48.0 Wh condition: 48.0/97.0 Wh (49%) volts: 12.6/11.4 
           model: SMP DELL GPM0365 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCP arch: Kaby Lake 
           family: 6 model-id: 9E (158) stepping: 9 microcode: CA L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 44817 
           Speed: 1203 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 1301 2: 1294 3: 1240 4: 1255 
           5: 1293 6: 1244 7: 1217 8: 1242 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: 
           conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:591b 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Dell driver: nouveau v: kernel 
           bus ID: 01:00.0 chip ID: 10de:1c8d 
           Display: x11 server: 1.20.8 driver: nouveau compositor: gnome-shell 
           resolution: <xdpyinfo missing> 
           OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.6 
           direct render: Yes 
Audio:     Device-1: Intel CM238 HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a171 
           Sound Server: ALSA v: k5.6.11-1-MANJARO 
Network:   Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
           vendor: Bigfoot Networks driver: ath10k_pci v: kernel port: e000 bus ID: 02:00.0 
           chip ID: 168c:003e 
           IF: wlp2s0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 1-4:2 chip ID: 0cf3:e301 
Drives:    Local Storage: total: 491.66 GiB used: 179.2 MiB (0.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: PM961 NVMe 512GB size: 476.94 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: CXY74D1Q 
           scheme: GPT 
           ID-2: /dev/sda type: USB model: UFD 3.0 Silicon-Power16G size: 14.72 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / raw size: N/A size: 11.62 GiB used: 179.2 MiB (1.5%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 45.5 C mobo: N/A gpu: nouveau temp: 37 C 
           Fan Speeds (RPM): cpu: 2493 fan-2: 2506 
Info:      Processes: 234 Uptime: 50m Memory: 15.49 GiB used: 1.76 GiB (11.3%) Init: systemd v: 245 
           Compilers: gcc: N/A Shell: zsh v: 5.8 running in: gnome-terminal inxi: 3.0.37 

sudo parted -l

Model: UFD 3.0 Silicon-Power16G (scsi)
Disk /dev/sda: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      2777MB  2781MB  4194kB  primary               esp

Model: PM961 NVMe SAMSUNG 512GB (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  525MB  524MB   fat32        EFI system partition          boot, esp
 2      525MB   660MB  134MB                Microsoft reserved partition  msftres
 3      660MB   150GB  150GB   ntfs         Basic data partition          msftdata
 4      150GB   151GB  952MB   ntfs                                       hidden, diag
 5      151GB   151GB  1049kB
 6      151GB   151GB  1049kB
 8      151GB   512GB  361GB   ext4

sudo efibootmgr -v

BootCurrent: 0008
Timeout: 0 seconds
BootOrder: 0000,0003,0004,0005,0006,0007,0008
Boot0000* Windows Boot Manager	HD(1,GPT,ab2d2e4c-8f00-464d-9268-d3b5ad9dcff1,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.}...1................
Boot0003* Diskette Drive	BBS(Floppy,Diskette Drive,0x0)..BO
Boot0004* M.2 PCIe SSD	BBS(HD,P0: PM961 NVMe SAMSUNG 512GB,0x0)..BO
Boot0005* USB Storage Device	BBS(USB,UFD 3.0 Silicon-Power16G1100,0x0)..BO
Boot0006* CD/DVD/CD-RW Drive	BBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
Boot0007* Onboard NIC	BBS(Network,Onboard NIC,0x0)..BO
Boot0008* UEFI: UFD 3.0 Silicon-Power16G1100, Partition 1	PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/HD(1,MBR,0x0,0x52c200,0x2000)..BO


manjaro-chroot -a ( select 1 if only one line appears )
cat /etc/fstab
lsblk -fs

wait return infos ( do not quit )

In the chrooted environment:

cat /etc/fstab

# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=c4a57043-a2bf-4afc-b12c-4bd6bd1e671b /              ext4    defaults,noatime 0 1

lsblk -fs

nvme0n1p8                          258.2G    17% /

you can

exit ( quit chroot )
sudo lsblk -fs 

does UUID for nvme0n1p1 appears ?


nvme0n1p1 vfat   FAT32  ESP                E420-B649                                           

ok we go in chroot

manjaro-chroot -a 
nano /etc/fstab ( add UUID for /boot/efi )  *** use TAB ***
# < file system >                           < mount point >  < type >  < options >  < dump >  < pass >
UUID=E420-B649				  /boot/efi      vfat    defaults,noatime 0       2

quit ( leave chroot )

Okay, I did this, does this mean that I am okay to reboot? Or is there something else I need to do?

now you can

manjaro-chroot -a 
cat /etc/fstab
lsblk -fs ( UUID should be ok for /boot/efi )
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --verbose
efibootmgr -v
exit ( quit chroot )
1 Like

That totally did it! I guess I need the EFI partition in the FStab of the OS I am trying to boot, :man_facepalming: Thank you so much!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by