did you try booting into 4?
1 Like
I tried it. But didnât work.
can you run these two:
lsblk -o NAME,FSTYPE,PARTUUID,MOUNTPOINT
sudo efibootmgr -v
so we can get an idea where 4 pointed to.
1 Like
lsblk -o NAME,FSTYPE,PARTUUID,MOUNTPOINT
NAME FSTYPE PARTUUID MOUNTPOINT
loop0 squashf /snap/core18/1885
loop1 squashf /snap/core18/1705
loop2 squashf /snap/gnome-3-34-1804/24
loop3 squashf /snap/snap-store/467
loop4 squashf /snap/gnome-3-34-1804/36
loop5 squashf /snap/gtk-common-themes/1506
loop6 squashf /snap/snap-store/433
loop7 squashf /snap/snapd/8790
loop8 squashf /snap/snapd/7264
sda
ââsda1 ntfs 225b152c-a06a-4cd3-aa88-34acdca45f43 /mnt/sda1
sdb
ââsdb1 vfat 7dd82bda-620f-4731-9e70-cda9365d8fc3 /boot/efi
ââsdb2 ext4 717748c4-f98c-414b-b6eb-41b193dc7904 /
sr0
BootCurrent: 0004
Timeout: 2 seconds
BootOrder: 0004,0003,0005
Boot0000* Fedora HD(1,GPT,0e1ab6cf-97b2-4e07-9dc5-f7f62530140e,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
Boot0001* gentoo HD(2,GPT,61666d7b-3de4-4e2c-a409-ef89eaabbbd9,0x1800,0x40000)/File(\EFI\gentoo\grubx64.efi)
Boot0002* Windows Boot Manager HD(2,GPT,61666d7b-3de4-4e2c-a409-ef89eaabbbd9,0x1800,0x40000)/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.4.7.9.5.}âŚaâŚ
Boot0003* ubuntuefi HD(1,GPT,2813fbbc-1d22-4c84-bbaf-ff39ae30a7eb,0x800,0x100000)/File(\EFI\ubuntu\grub.efi)
Boot0004* ubuntu HD(1,GPT,2813fbbc-1d22-4c84-bbaf-ff39ae30a7eb,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0005* UEFI: SanDisk SD9SN8W128G1014, Partition 1 HD(1,GPT,7dd82bda-620f-4731-9e70-cda9365d8fc3,0x800,0x100000)/File(\EFI\boot\bootx64.efi)âŚBO
according to your boot repair summary that is the partuuid for the usb you are using to boot. not sure why your system would create that at all 
going off of what is on this page, hopefully you can create an entry that finally points to the right file. the generic command is this:
efibootmgr -c -d /dev/sda -p 7 -L -l \EFI\label\grubx64.efi
-c to create, -d to choose the disk, -p to choose the partition, -L gives it a label and -l (that is a small letter L, not a 1 in case you are typing it in instead of copying and pasting) points to the loader. you created one before so you know all of that. i am mostly posting it for myself for reference.
-d defaults to /dev/sda so you should set it to /dev/sdb. -p defaults to 1, but donât think it will hurt to set it just to be sure. since the boot repair summary specifically mentions using EFI/ubuntu/shimx64.efi, that is what i would use for -l.
so the final command should be something like:
sudo efibootmgr -c -d /dev/sdb -p 1 -L ubuntu20 -l \EFI\ubuntu\shimx64.efi
1 Like
This message is showing again and again after doing it:
can you run
sudo efibootmgr -v
again to see if it created an ubuntu20 entry?
1 Like
Yes.
Boot0006* ubuntu20 HD(1,GPT,2813fbbc-1d22-4c84-bbaf-ff39ae30a7eb,0x800,0x100000)/File(EFIubuntushimx64.efi)
thatâs the wrong partuuid. that is for your usb drive
did you have your usb drive in when you ran lsblk -f before? it didnât show in the listing (trying to make sure the partuuid is the same as listed above). did you reboot at all between when you posted the output for lsblk and when you created the ubuntu20 entry?
1 Like
no
no.
Should I consider installing a different distro?
that might be an option (or possibly a re-install) that i would consider as well. trying to create the correct entry was my last real idea before trying to run bootinfoscript to see if something had changed between that repair summary and now, but i can imagine you just want to get back to using your system.
i had hoped someone with an efi system like yours would pop their head in the discussion and offer some helpful words.
my efi system boots legacy grub from the mbr and works just fine. it takes a bit of extra work to keep it updated, but not much.
1 Like
ok. thank you so much for your patience and time. 
if you are done trying to solve this, i would totally understand. if not, have you tried askubuntu or linuxquestions? getting a different perspective might be helpful.
edit: i was happy to try and help. thank you for trying all of the commands i suggested and providing feedback. i am sorry it didnât get you sorted.
1 Like
yeah. I had posted the same question on askubuntu. But got no reply 
in case a third option is of interest: https://www.linuxquestions.org/questions/ubuntu-63/
2 Likes
Now, I have installed fedora. And there is same problem.
I had installed gentoo before ubuntu. I think I messed up something there. 
Is there any way to completely reset efibootmgr (because I tried to boot gentoo using efibootmgr instead of grub2, although it didnât work at that time, and probably I made some mistake there.)
Wipe the entire storage medium and install everything anew and fresh.
1 Like
Already done that twice. While installing Ubuntu, and then while installing fedora.
Hello. I found the solution. For ubuntu, all you have to do is run the following commands:
$ sudo su
cd /boot/efi/EFI
mv BOOT BOOT_bak
cp -R ubuntu BOOT
cd BOOT
mv shimx64.efi bootx64.efi
I donât exactly know what happened or why it works. But it worked. Here is the full answer:
https://www.dell.com/community/Inspiron/Dell-G3-15-3579-System-BootOrder-not-found/td-p/6242049
Thank you all and especially @01101111 for helping me so much. Linux community is the best!!!
1 Like