Yesterday , I had plugged a USB into my system , it was a Live USB(Bootable one), but it didn’t get recognized ,seeing this , i had an EFI Partition in my system , whose folder i first deleted and then later on formatted it , thinking this was the EFI of Live USB , still when nothing happened , I checked from disk management and realized , i had formatted the wrong partition, at first , I didn’t realize it , until i had to restart my system and the grub had changed on loading Manjaro it failed to load and displayed error , on some research , I found out that it can be made working if we have that storage unused , which is in my case , also I don’t want to ruin the system anymore so i didn’t try for any solutions.
I have also found something similar on Manjaro forum , but don’t want to risk doing more thing ,
I’ll post my system details in five mins , sorry to make you wait
Use a live USB to re-create the partition, using either gparted or KDE partition manager. The filesystem should be FAT32, and it should have the boot and esp flags.
Then follow this guide:
EDIT:
Before you chroot and fix grub, edit manjaro’s /etc/fstab to account for the new UUID.
The partitioning is no problem, you can use any distro for that.
The chroot and fixing (installing and updating) grub may (or may not) work. I can’t think of any reason it wouldn’t, but I don’t use endeavour.
You should be able to use arch-chroot instead of manjaro-chroot.
Well only you know your system, we can only guess. How many EFI partitions did you have?
Based on what you say, I’d guess that sdb10 is an EFI for windows, sdb12 is an EFI for endeavour, and you deleted sdb6.
There should be some unused space where you deleted the partition. Look using a partition editor such as gparted or kde partition manager.
Not sure if endeavour can boot manjaro, but being arch based it may well be able to. If so you could make sure os-prober is enabled in /etc/default/grub and update grub from there, then endeavour’s grub could boot manjaro.
If you just deleted the folder (the directory) - then create it again
on the right partition
Which one it is/was is difficult (aka: impossible) to say from your fdisk output
You could look up /etc/fstab - the info should be there.
The /boot directory is already there - in the / (root) of the file system
the EFI partition is mounted to it -
all you would have likely done is to delete the efi directory inside it.
The small box is the one i think it was, i had deleted in windows explorer , there its mentioned as disk ‘l’ , but if i look at the first image i have shared , the failed for system check on … , do not match with any i see here
and what is media items , i have tried posting a ss but it doesn’t allow it.
?
… “the small box” does not compute …
and:
I really do not know Windows well - but well enough to know that it (by default) can’t see Linux partitions
But the EFI is different - the file system is FAT.
A Windows native file system.
</> # /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=3B51-861D /boot/efi vfat umask=0077 0 2
UUID=c4596ece-df47-4850-b449-a3d299717e9c / ext4 defaults,noatime 0 1
UUID=965006b0-1683-4dd3-8e93-fd482161729d /home ext4 defaults,noatime 0 2
UUID=94829c5d-b261-4d3d-87c5-0f25511c93e2 swap swap defaults,noatime 0 0
sudo grub-mkconfig -o /boot/grub/grub.cfg
[sudo] password for parasetu:
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-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.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Ubuntu 20.04.1 LTS (20.04) on /dev/nvme0n1p5
Found Garuda Linux (Soaring) on /dev/sdb4
****Found Manjaro Linux (21.3.2) on /dev/sdb7****
Adding boot menu entry for UEFI Firmware Settings ...
done
it found manjaro , and sorry i know , my system looks trash with so many distros , i have thought of fixing it , but have some data on every distro :((
man , it was a blunder , i don’t know how could i be so careless , i usually format from disk manager , this way i always get to know if i formatting the right device or not , but last night , idk what made me do it from file explorer
can it be repaired ? , because i miss the manjaro bootloader , all the other one’s are too flashy
