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

Nachlese · 16 August 2024 18:08

That’s an error, yes.
But you didn’t say that it was fatal - that it prevented your system from booting.

You can use that swap partition with the live system as well - I would have thought that it is even used automatically by it.

If it is unused, you can recreate the swap space:
sudo mkswap /dev/sda9

but by doing that, the UUID will change - and you’d need to adapt it in /etc/fstab and in
/etc/default/grub for/in your real system

I’m really out of ideas to try with this … puzzle.

I lost the plot like at least 20 posts ago.

Sorry.

BG405 · 16 August 2024 18:16

Shouldn’t the first swap actually be none?

anukul · 16 August 2024 18:18

huh means ?

I just did this

changed the UUID

and now i don’t find any place to change in grub

  GNU nano 8.1                                  /etc/default/grub                                             
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT=""
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 Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true

# 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 `vbeinfo'
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="/path/to/gfxtheme"

BG405 · 16 August 2024 18:20

Means you have swap twice in that line, instead of e.g.:

Edited to add:
Your cmdline is missing the resume UUID. Here’s an example:

GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=8eb80e10-0b17-4e68-8d79-e1c69a792054"

anukul · 16 August 2024 18:22

oh lord , where were you ? ahaha , i again did something unnecessary , wait , i’ll try to change it now . hope my mistake of re-partitioning it won’t cause any more trouble

did that , so should i un-mount from here and give it a try ?

oh thanks for pointing that

BG405 · 16 August 2024 18:24

I just edited my above post; please check that first before rebooting.

EDIT: Didn’t see your edit!

anukul · 16 August 2024 18:28

ahah , i’m so happy to find some support again

GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=f3261ca0-9a81-409a-a3d1-503b64ef5e0b"

well does it look okay now?,umm, that’s the new UUID
and now umount and restart?

BG405 · 16 August 2024 18:30

If that is the correct UUID for your swap partition, then yes. It’s different than the one I picked up from your previous post. I may have pasted the wrong one.

anukul · 16 August 2024 18:32

yes sir
lsblk -f

├─sdb9    swap     1                           f3261ca0-9a81-409a-a3d1-503b64ef5e0b

also do i need to configure boot for now ? or i can do that in manjaro later?

Nachlese · 16 August 2024 18:33

Once you changed this, once you change that file,
you need to run
sudo mkinitcpio -P
or only:
sudo update-grub

But from within the system - if it is not booting right now, you’ll need to chroot

anukul · 16 August 2024 18:34

I haven’t tried booting it till now, why take risk and why not chroot it now and try to update ? will that be okay?
or should i try booting first?

Nachlese · 16 August 2024 18:38

What risk are you afraid of taking?
You said it didn’t boot - and you are now in a live system.
You can always go back there.
If it didn’t work before - it will not work now is my prediction.
But there is no risk.

anukul · 16 August 2024 18:39

alright sir , i’ll try to boot , ahaha that was pretty logical , yeah it wasn’t working but what if it will , but yeah rightly said no risk , give me 2 mins

anukul · 16 August 2024 18:44

well @Nachlese you were right , it didn’t work , same error was displayed as

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

and it still showed the old UUID , even tho it doesn’t exist anymore

BG405 · 16 August 2024 18:49

One thing I’ve noticed is that nano sometimes introduces line-breaks when you edit long lines (wider than the number of columns you are displaying in your Terminal). I’ve had to remove these line breaks on a number of occasions. Worth double-checking the file.

Just a thought; might not be the case, but it happens.

Nachlese · 16 August 2024 18:50

so, time to chroot

from the live system, mount your / partition to /mnt
and then mount the efi partition to where it belongs

sudo mount /dev/sdb9 /mnt
sudo mount /dev/sdb10 /mnt/boot/efi

then
manjaro-chroot /mnt /bin/bash

then verify that this worked and that you are now inside the correct system

proceed with:

mkinitcpio -P

and
update-grub

exit
reboot and check result

… haven’t we been here before?

anukul · 16 August 2024 18:53

ah ,i know you must not be aware of this , but still reaffirming so that i don’t end up making a mess , sdb9 is swap and sdb7 is root and sdb10 is boot efi , so first you want me to mount sdb7 that is my / aka root, true?

Nachlese · 16 August 2024 18:55

True.
yes - it is /dev/sdb7 - it is all so spread out now, I lost track

anukul · 16 August 2024 19:00

oh thanks , don’t worry , you still guiding me , that’s what important

well in the end generation successful but a ton of warnings and some errors and how can i compress the number of lines of this post

sudo mount /dev/sdb7 /mnt                                                                     
 sudo mount /dev/sdb10 /mnt/boot/efi                                                         
manjaro-chroot /mnt /bin/bash                                                                
[manjaro /]# mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img
==> Starting build: '4.14.268-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
==> ERROR: module not found: 'crypto_lzo'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> ERROR: file not found: '/lib/modules/4.14.268-1-MANJARO/modules.builtin.modinfo'
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.RxiOqP/root/lib/modules/4.14.268-1-MANJARO: No such file or directory
==> Creating gzip-compressed initcpio image: '/boot/initramfs-4.14-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
==> Starting build: '4.14.268-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
==> ERROR: module not found: 'crypto_lzo'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> ERROR: file not found: '/lib/modules/4.14.268-1-MANJARO/modules.builtin.modinfo'
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.Cv35K1/root/lib/modules/4.14.268-1-MANJARO: No such file or directory
==> Creating gzip-compressed initcpio image: '/boot/initramfs-4.14-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux511.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.11-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.11-x86_64.img
==> Starting build: '5.11.22-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.11-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux511.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.11-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.11-x86_64-fallback.img -S autodetect
==> Starting build: '5.11.22-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.11-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux610.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.10-x86_64.img
==> Starting build: '6.10.3-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.10-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux610.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.10-x86_64-fallback.img -S autodetect
==> Starting build: '6.10.3-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.10-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful

also update-grub command not found means i’ll have to install it , right?

[manjaro /]#  update-grub
bash: update-grub: command not found

so grub-install? or sudo grub-install

Nachlese · 16 August 2024 19:06

neither -
update-grub just a helper script for convenience

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

achieves the same effect

the rest of it should be o.k.