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

Support
143

one error

ERROR: mkdir /var/lock/dmraid


[manjaro /]# grub-mkconfig -o /boot/grub/grub.cfg
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

okay so exit and reboot?

144

ignore it,
exit
reboot

1 Like
145

This kernel is obsolete. What’s the result of mhwd-kernel -l && mhwd-kernel -li?

… having an obsolete kernel installed (whether using it or not) will likely cause errors with system upgrades.

1 Like
146

I’d say:
let him worry about that once the system boots again.
obsolete doesn’t mean it is no longer working
it used to work

Of course the next task will be to update the system as well.

2 Likes
147

nope man , the same god damn error and also i have a query
in the bootloader manjaro is listed as

Manjaro Linux (21.3.2) (on /dev/sdb7)
Advanced options for Manjaro Linux Linux (21.3.2) (on /dev/sdb7)

Advanced options for Manjaro Linux Linux (21.3.2) (on /dev/sdb7) has the following list
Manjaro Linux (on /dev/sdb7)
Manjaro Linux (Kernel 5.11.22-2-MANJARO x64) (on /dev/sdb7)
Manjaro Linux (Kernel 5.11.22-2-MANJARO x64 - fallback initramfs) (on /dev/sdb7)
Manjaro Linux (Kernel 4.14.268-1-MANJARO x64) (on /dev/sdb7)
Manjaro Linux (Kernel 4.14.268-1-MANJARO x64 - fallback initramfs) (on /dev/sdb7)
Memory Tester (memtes86+) (on /dev/sdb7)

the query is why is (21.3.2) , i don’t think its the right thing , i surely don’t remember what it used to be but my kernel is 5.11

148

I had tried this i even installed 610 from manjaro settings > kernal but it didn’t run , just got a tag of installed , this was done today only

149

do you want me to chroot and then run this command ?

150

yes - because:

you could not have done this from the live system - doesn’t work that way
and in chroot you wouldn’t have the graphical tool available

I don’t see an error btw.
which error?

this is the Manjaro version number, not the kernel

1 Like
151 
[manjaro /]# 

    mhwd-kernel -l && mhwd-kernel -li?
available kernels:
   * linux419
   * linux510
   * linux515
   * linux54
   * linux61
   * linux610
   * linux611
   * linux66
   * linux69
   * linux61-rt
   * linux610-rt
   * linux66-rt
   * linux69-rt
Error: Invalid argument (use -h for help).
[manjaro /]#

oh okay then its fine , i was worried about this

152

pay attention when copy/pasting
the question mark is not part of the command

mhwd-kernel -l lists the available kernels
mhwd-kernel -li lists the installed kernels

the & in between means:
do this command and then, if successful, do that command

1 Like
153

You apparently included the ? on the end of the command. :wink: Sorry, I should have put a space there to make it clearer.

@Nachlese is evidently a better typist than myself … :wink:

154

oh my apologies ,

[manjaro /]#     mhwd-kernel -l && mhwd-kernel -li 
available kernels:
   * linux419
   * linux510
   * linux515
   * linux54
   * linux61
   * linux610
   * linux611
   * linux66
   * linux69
   * linux61-rt
   * linux610-rt
   * linux66-rt
   * linux69-rt
Currently running: 6.9.10-1-MANJARO (linux69)
The following kernels are installed in your system:
   * linux414
   * linux511
   * linux610
155

ahahah , yeah that would have been better , considering how noob i’am ,
there’s also a saying here ''Even copying requires intelligence ‘’ :joy:

1 Like
156

I’ll leave you to it - I have no idea what error he is talking about.

1 Like
157 
Failed to stat resume device '/dev/disk/by-uuid/8eb80e10-0b17-4e68-8d79-e1c69a79
2054` : No such file or directory

this error brother :))
also can i show you my bios boot order ? there’s some manjaro listed there , idk why ?
i don’t think it was there before i ran the manjaro live usb , even after removing it’s there

158

linux511 is also obsolete; I’d recommend removing the old ones (via chroot naturally) and installing at least one LTS e.g. linux66 before attempting to do an upgrade.

My thoughts are that if EFI is now populated and GRUB installed (this is a long thread!) if you then (after dealing with the kernels) run a system upgrade, it might fix the boot issues?

1 Like
159

now when you are ready to help me find the solution why not help me copy the code and paste it as well :joy: :wink: ahaha , but wait , i’ll try to google it and should i install linux 66 directly or first install the linux 610, which is on my system , its installed but not running , how to run it

sudo mhwd-kernel -i linux66

is the above command okay to execute?

1 Like
160

it should be - but:
from within chroot !

and on that occasion, from within chroot
check whether you actually edited the right file and correctly:

grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub

1 Like
161

get in lewis :face_with_peeking_eye:
i guess you caught the problem its still the old one but how ?

162

because you previously did edit the file on the live system :sunglasses:
that explains why the line was empty

so now you correct the error

or you simply delete that wrong resume device statement from that line

and do the whole process again:

mkinitcpio -P
grub-mkconfig -o /boot/grub/grub.cfg

1 Like