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

but bro i did chroot and then changed it , how come it didn’t get reflected ?

  GNU nano 8.1                                             /etc/default/grub                                                        
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on apparmor=1 security=apparmor resume=UUID=f3261ca0-9a81-409a-a3d1-503b64ef5e0b udev>
GRUB_CMDLINE_LINUX=""

see this is the proof that its done now :))

also i was already in manjaro chroot so i didn’t execute this command

and directly executed

==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.10-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful

Found Ubuntu 20.04.1 LTS (20.04) on /dev/nvme0n1p5
Found EndeavourOS Linux (rolling) on /dev/sdb13
Found Garuda Linux (Soaring) on /dev/sdb4
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

1 Like

If you don’t know - how can I? :wink:
I suspected it - that’s why I suggested the check/verification

don’t forget
grub-mkconfig -o /boot/grub/grub.cfg

Genius Gentleman :saluting_face:
so now its done so exit chroot and reboot

done sir , pasted the outcome as well :))

don’t celebrate early

1 Like

you were right :slight_smile: and it’s the same error in red color , can i share a picture of my bios boot sequence , because i never saw manjaro before there , now its on top , can that be an issue

this time UUID was also correct

[manjaro /]#  grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on apparmor=1 security=apparmor resume=UUID=f3261ca0-9a81-409a-a3d1-503b64ef5e0b udev.log_priority=3"

should we run this command at last ?

sudo mhwd-kernel -i linux66

It wouldn’t hurt. Then run

mhwd-kernel -r linux414
mhwd-kernel -r linux511

(can’t remember if sudo is needed or if it uses polkit; try without sudo first to see).

1 Like

Nothing much happened

[manjaro /]# sudo mhwd-kernel -i linux66
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
error: no targets specified (use -h for help)

:: grub-mkconfig output:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.10-x86_64.img
Found initrd fallback image: /boot/initramfs-6.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.11-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.11-x86_64.img
Found initrd fallback image: /boot/initramfs-5.11-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sdd1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdd1.  Check your device.map.
Found Ubuntu 20.04.1 LTS (20.04) on /dev/nvme0n1p5
Found EndeavourOS Linux (rolling) on /dev/sdb13
Found Garuda Linux (Soaring) on /dev/sdb4
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

I don’t think that was it , no download , no install?

Could this be the reason?

Maybe your mirrors are not up to date. sudo pacman-mirrors --continent should work.

I do see you have community shown in the repo list so you definitely haven’t tended your pacnews in over a year! But this might not be a show-stopper as such.

in chroot, sudo is not needed - you are already root from the outset

2 Likes

so just

mhwd-kernel -i linux66
1 Like

Temporarily forgot it’s chroot :wink:

2 Likes
::INFO Writing mirror list

::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist

so after that i ran

mhwd-kernel -i linux66

same output like last time

That’s got me a bit stumped. What happens if you try installing using Pacman instead?

pacman -S linux66

pacman -S linux66
resolving dependencies…
looking for conflicting packages…

Packages (1) linux66-6.6.44-1

Total Download Size: 129.10 MiB
Total Installed Size: 134.76 MiB

:: Proceed with installation? [Y/n] y

Looks like it will hopefully be good to go. :crossed_fingers: :wink:

1 Like
=> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(5/5) Updating Kernel initcpios for Nvidia-DRM..

update done
i’m not removing the earlier kernels for now , also its almost 2:30 am here , i don’t wanna risk my health while recovering manjaro’s health :sweat_smile: so i’ll go sleep for now , hope someone can help me tomorrow as well , take care , goodnight :smiley:

1 Like

okay , new update , after exploring few other arc distros for the same error , i found out a guy commenting that he gets the same issue but all he does is press ‘enter’ and the system will boot normally and to my surprise , he was right , i pressed enter and the system booted , then i again restarted and didn’t press anything and i was returned to grub bootloader and then again i pressed enter after that error and here i’m in manjaro , idk what’s happening but how can an ‘enter’ make so much difference when its not even listed , also system has been updated but on doing

uname -r
5.11.22-2-MANJARO

now i have done

sudo mhwd-kernel -i linux66

but it said

==> Warning:
	 -> Kernel has been updated. Modules of the current kernel
	 -> have been backed up so you can continue to use your
	 -> computer. However, the new kernel will only work
	 -> at next boot.

okay so after rebooting , this time i didn’t had to press ‘enter’ and the manjaro booted up after that error on its own , but now i checked the kernel version still the same 5.11.22-2-MANJARO

You may have installed the kernel (per your previous post, two up)
But you did not tell Grub about it’s existence.

sudo grub-mkconfig -o /boot/grub/grub.cfg

Installing kernels using pacman is not lege artis in Manjaro.

you could use update-grub - no idea why you don’t have it installed
It would probably be there if your system would be current (updated).

No idea why you apparently do not get a menu to choose your kernel.
Must be something with /etc/default/grub

Can you paste your /etc/default/grub , I’ll try to match it word by word

ran this command , it worked . checked uname -r , still the same
after that i looked for update-grub , and found out it doesn’t exist in arch distros

[parasetu@Pasec ~]$ sudo nano /etc/default/grub

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on apparmor=1 security=apparmor resume=UUID=f3261ca0-9a81-4>
GRUB_CMDLINE_LINUX=""

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically
GRUB_ROOT_FS_RO=true

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false


Change timeout style from hidden to menu.
Then
sudo grub-mkconfig -o /boot/grub/grub.cfg
And on reboot you will see the menu for 5 sec to choose kernel 6.6 (probably under advanced). It will then be remembered.

3 Likes