Deleted EFI Folder , how to recover it or make a new one?

Support
183

Mine would possibly not be any good - I only have Manjaro (Gnome, Xfce4, Cinnamon, Plasma …) in several VM’s
not even one on real hardware.
And not in multi boot configuration, but a separate VM for each one.
… and I have altered some of them - to not show a menu or to not wait for any input to select a different kernel …

I trust @Teo to be able to decode the possible issue.

as you can see:
sudo grub-mkconfig -o /boot/grub/grub.cfg
is the equivalent

The package / the command was always available by default in any Manjaro system I installed.

You can install it:
sudo pacman-mirrors -c Germany
or
sudo pacman-mirrors -f
to update the mirrors

sudo pacman -Syu update-grub

(will try to update the whole system and also install that package)

1 Like
184

well i did edit /etc/default/grub

  GNU nano 8.1                   /etc/default/grub                              
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on apparmor=1 security=apparmor r>
GRUB_CMDLINE_LINUX=""

and then sudo grub-mkconfig -o /boot/grub/grub.cfg
but nothing changed , still on 5.11.22-2-MANJARO

okay @teo can this problem be solved by chroot into garuda linux , who’s boot loader is opening and then try to edit it’s grub file and turn it into hidden just as we changed manjaro’s into menu and then update-grub , is that worth a shot?

185

that is quite some information … :facepalm: (if I’m interpreting this correctly)

This really is a puzzle - and a mess.

186

well this worked and also sudo update-grub is working but still i don’ think it will make a difference , as you rightly said sudo update-grub and sudo grub-mkconfig -o /boot/grub/grub.cfg is same

187

not the same - it just does the same job - the here relevant part of it
… equivalent :sunglasses:

1 Like
188

haha wait , i try to simplify it for you ,
currently the bootloader i’m getting is of garuda linux
what if i boot through manjaro live usb and then mnt into garuda OS
and then using chroot , i’ll try to edit /etc/default/grub
won’t this be the grub bootloader of garuda? and there i will change GRUB_TIMEOUT_STYLE=menu into GRUB_TIMEOUT_STYLE=hidden
, so that garuda bootloader doesn’t open and this will force manjaro’s or some other grub bootloader

189

no need to simplify - I think I got it

When you boot using that distro’s boot loader
why are you trying to adjust things on Manjaro’s boot loader configuration?

You would need to boot Garuda and update it and it’s Grub.

You are really stretching things here - but we are still having fun. :wink:

2 Likes
190

because i want manjaro’s bootloader , garuda’s bootloader is breaking garuda os and also i don’t like the look n feel of garuda os , also it always points to garuda os when i boot , unlike manjaro , where it boots into the last selected os

191

It doesn’t work like that. You need to change the boot priority in the UEFI to change which bootloader is used.

In the grub menu, select Manjaro (Advanced Options) then select the kernel you want.

192

Whatever you may want:
you mixed up info over the course of close to 200 posts

I can’t and won’t decode it.

btw:

you only need one (1) boot loader - not several.

193

I did , only the old one’s were mentioned and i think its because garuda’s grub hasn’t been updated
, also when i go into bios to setup boot sequence , i have three similar names , which is indicating , three grub’s of Manjaro , EOS and garuda , now how do i choose which is which?

194

okay i’ll turn off other’s , once i’m able to have manjaro’s bootloader :))

195

So boot into garuda and update grub.

Or change the boot priority to manjaro’s grub.

Try out each one until you find the right one.

1 Like
196

Garuda can’t be booted through garuda’s bootloader

okay wait , i try this one :slight_smile:

the best part of it is i got a reader tag in the forum for reading a 100 posts of one topic only , also i’ll summarise all the answers in one post , so next time someone doesn’t have to go through 200 posts

197

that’s a bit unusual - don’t you think? :sunglasses:

198

Well , that’s because i had tried to Qemu virtualisation and i had to disconnect it

199

admirable project
can’t wait to see it :grimacing:

… why even have that many distros when you could just have one that you know
and do the rest as VM’s ?
(rhetorical question …)

I have several Manjaro VM’s,
all kvm / qemu / virt-manager
one EOS and some variants of Windows
all running under:
Mint (LTS, but not the most current)

you could also just revert the changes that you did to it - and it would behave like before …

2 Likes
200

because i learned about lv, qemu vm’s later on and then i try to use more of then and that’s why most of my systems are outdated ,

yeah , but like it was never a concern so , i was never worried about it :slight_smile:

okay so i did ,so currently there were 5 options in boot sequence , listed as below

  • UEFI : WD Elements 2621 1026 but mentioned as UEFI : WD Elements 2621 1026 (Garuda)
  • windows boot manager which is unchecked , so it was not in the list
  • manjaro mentioned as manjaro
  • UEFI : WD Elements 2621 1026 mentioned as UEFI : WD Elements 2621 1026
  • UEFI : WD Elements 2621 1026 mentioned as UEFI : WD Elements 2621 1026

i tried all besides windows boot manager , and on trying, manjaro and one UEFI : WD Elements 2621 1026 , the computer start and trips and then redirects me to boot sequence and i had to rechoose it and on trying last UEFI : WD Elements 2621 1026 , the bios gave me a clear message of ’ no bootable device ’

201

I agree 100% on the suggestion by @Nachlese to use VMs. Far simpler to have just one OS on bare metal; you can experiment with and explore as many other distros as will fit in your storage, save snapshots, duplicate or delete them, whatever. :wink:

2 Likes
202

yeah - but now it is - apparently

I don’t have any personal knowledge or experience to offer in this regard.
Zero! (0)

I could just search and read and learn just like you - if I needed to,
which … I don’t and won’t do, in this case.

Because:
I have no conceivable application case for myself for this kind of knowledge - at the present moment.

1 Like