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

[anukul]

just give me a min Sir , let’s test it out :)) hehe

on mounting the root and then using
sudo nano /mnt/etc/fstab
I did get that UUID , which is shown in the first image , now do i need to replace it with the new UUID ?

# edit the file
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# edit the file

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=25E1-96DF                            /boot/efi      vfat    umask=0077 0 2
UUID=411dc37c-e651-4220-b380-d3306c59e042 /              ext4    defaults,noatime 0 1
UUID=30fde1a2-8594-4a14-86fa-6cdad59bc450 /home          ext4    defaults,noatime 0 2
UUID=8eb80e10-0b17-4e68-8d79-e1c69a792054 swap           swap    defaults,noatime 0 0

[dmt]

@anukul

on mounting the root and then using
sudo nano /mnt/etc/fstab
I did get that UUID , which is shown in the first image , now do i need to replace it with the new UUID ?

Yes that’s it.

[anukul]

okay changed the name , but i didn’t use the gparted to partition the space , will it make any difference and now , after i changed the UUID address , what next to do ?

[Nachlese]

@dmt

If you’re using endeavour then follow manual chroot, but replace manjaro-chroot with arch-chroot. I think that should work.

it would, anytime

arch-chroot is not present by default in Arch or EOS

chroot - ArchWiki

it may be present on the installation medium
but not on the resulting, installed system
after system installation, it needs to be installed explicitly
see the link - section 4.1

just like manjaro-chroot is only present on the installation medium - but can be installed to the final system

[dmt]

@anukul

but i didn’t use the gparted to partition the space

Then where did the UUID come from?

Perhaps it’s best to check things so far

lsblk -f
cat /mnt/etc/fstab  # manjaro / needs to be mounted

[anukul]

idk , but things look pleasant for now

lsblk -f

sdb
├─sdb1 swap 1 4ddeeafa-1e01-40b5-9acd-1964b5d7d904
├─sdb2 ext4 1.0 deaf8b37-bb62-4476-b25b-01cfa045338e 23.2G 85% /run/media/parasetu/deaf8b37-bb62-4476-b25b-01cfa045338e
├─sdb3 vfat FAT32 97D4-30D3
├─sdb4 ext4 1.0 427984c1-6f4d-4c2c-84da-d8455e70fd15 9G 79% /run/media/parasetu/427984c1-6f4d-4c2c-84da-d8455e70fd15
├─sdb5 ext4 1.0 965006b0-1683-4dd3-8e93-fd482161729d 45.9G 48% /home
├─sdb7 ext4 1.0 411dc37c-e651-4220-b380-d3306c59e042 64.6G 29% /mnt
│ /run/media/parasetu/411dc37c-e651-4220-b380-d3306c59e042
├─sdb8 ext4 1.0 30fde1a2-8594-4a14-86fa-6cdad59bc450 56.3G 56% /run/media/parasetu/30fde1a2-8594-4a14-86fa-6cdad59bc450
├─sdb9 swap 1 8eb80e10-0b17-4e68-8d79-e1c69a792054
├─sdb10 vfat FAT16 E62F-7A17 511.7M 0% /run/media/parasetu/E62F-7A17
├─sdb11 swap 1 94829c5d-b261-4d3d-87c5-0f25511c93e2 [SWAP]
├─sdb12 vfat FAT32 NO_LABEL 3B51-861D 987.5M 3% /boot/efi
└─sdb13 ext4 1.0 c4596ece-df47-4850-b449-a3d299717e9c 256G 62% /

there’s some info ahead of sdb7,8,9,10

cat /mnt/etc/fstab

</># /etc/fstab: static file system information.
#
</># Use 'blkid' to print the universally unique identifier for a device; this may
</># be used with UUID= as a more robust way to name devices that works even if
</># disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=E62F-7A17                            /boot/efi      vfat    umask=0077 0 2
UUID=411dc37c-e651-4220-b380-d3306c59e042 /              ext4    defaults,noatime 0 1
UUID=30fde1a2-8594-4a14-86fa-6cdad59bc450 /home          ext4    defaults,noatime 0 2
UUID=8eb80e10-0b17-4e68-8d79-e1c69a792054 swap           swap    defaults,noatime 0 0

is it fixed??

[Nachlese]

can you not - just like
lsblk -f
above

highlight all the output and format it in the same way?
as </>
so it is actually readable?

for example:

sdb
├─sdb1 swap 1 4ddeeafa-1e01-40b5-9acd-1964b5d7d904
├─sdb2 ext4 1.0 deaf8b37-bb62-4476-b25b-01cfa045338e 23.2G 85% /run/media/parasetu/deaf8b37-bb62-4476-b25b-01cfa045338e
├─sdb3 vfat FAT32 97D4-30D3
├─sdb4 ext4 1.0 427984c1-6f4d-4c2c-84da-d8455e70fd15 9G 79% /run/media/parasetu/427984c1-6f4d-4c2c-84da-d8455e70fd15
├─sdb5 ext4 1.0 965006b0-1683-4dd3-8e93-fd482161729d 45.9G 48% /home
├─sdb7 ext4 1.0 411dc37c-e651-4220-b380-d3306c59e042 64.6G 29% /mnt
│ /run/media/parasetu/411dc37c-e651-4220-b380-d3306c59e042
├─sdb8 ext4 1.0 30fde1a2-8594-4a14-86fa-6cdad59bc450 56.3G 56% /run/media/parasetu/30fde1a2-8594-4a14-86fa-6cdad59bc450
├─sdb9 swap 1 8eb80e10-0b17-4e68-8d79-e1c69a792054
├─sdb10 vfat FAT16 E62F-7A17 511.7M 0% /run/media/parasetu/E62F-7A17
├─sdb11 swap 1 94829c5d-b261-4d3d-87c5-0f25511c93e2 [SWAP]
├─sdb12 vfat FAT32 NO_LABEL 3B51-861D 987.5M 3% /boot/efi
└─sdb13 ext4 1.0 c4596ece-df47-4850-b449-a3d299717e9c 256G 62% /

just like I just did?

[anukul]

sorry , what should i do ? i wish there was a way to add photo but wait i’ll try to bold
oh wait how did you do it ? wait i’ll copy paste yours

[Nachlese]

@anukul

i wish there was a way to add photo

no, no photos or screenshots, please!

where you copy/paste your text, there are some symbols above - in the top row

…

</> is what you want to recreate terminal output in a readable way

you already did it with some of it - now apply that to the rest
please!

@anukul

is it fixed??

you can see the difference, no?
and the resemblance to the actual terminal output that you saw, no?

[anukul]

@Nachlese

you can see the difference, no?

yes , looks more presentable and easy to read as well

[Nachlese]

I will indeed shut up now.

[anukul]

haha ,why ? and thanks for teaching me , i just corrected all the above posts :))

someone tell me , if its fixed or more to do ? ah , i’m so curious

[dmt]

@anukul

is it fixed??

Looks like you decided to use an existing EFI partition. I suspect that’s the one used by windows, but I’m not sure. I havent used windows in a long time so I’m not sure if it’ll break anything.

I suggested making a new partition because I didn’t want you to have to fix another bootloader, or change your setup.

Perhaps someone else can tell us if it will break window’s bootloader. So maybe give it a few minutes for someone to say something.

Other than that it looks good. If and when you’re happy to proceed, you can chroot into the system and fix grub.

[Nachlese]

… the intention being to not constantly interfere with @dmt
and I’d like to watch some videos …

[dmt]

Feel free to take over if you wish.

@Nachlese

I’d like to watch some videos

Me too.

[anukul]

brother my window partition is on SSD , and this sdb is a HDD , how can a ssd thing be on windows ? i don’t know much , but i think that way

[Nachlese]

@dmt

Me too.

well - it’s not a paid job here

I struggle with it myself - when I think I know “the answer”.
But it’s often difficult to convey.

When you know, it’s two minutes.
To explain it can amount to hours - or even be in vain.

[dmt]

Ah ok, if your windows EFI is on another drive, then chroot in and fix grub then.

[anukul]

manjaro-chroot -a ?? or arch-chroot -a
and do i have to mount first or first chroot?

also its showing already mounted , do i even need to chroot? can i not directly update grub?

[dmt]

Not if you’re using endeavour.

First install arch-chroot:

sudo pacman -S arch-install-scripts 

Then:

@dmt

If you’re using endeavour then follow manual chroot, but replace manjaro-chroot with arch-chroot. I think that should work.

@anukul

also its showing already mounted , do i even need to chroot? can i not directly update grub?

AFAIK you can only fix grub from within the manjaro install, so you need to chroot.