[parasetu@Pasec ~]$ sudo mount /dev/sdb10 /mnt
[sudo] password for parasetu:
[parasetu@Pasec ~]$
tar xfv ~/efi.tar -C /boot/efi
tar: /home/parasetu/efi.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
[parasetu@Pasec ~]$ sudo tar xfv ~/efi.tar -C /boot/efi
[sudo] password for parasetu:
tar: /home/parasetu/efi.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
[parasetu@Pasec ~]$ sudo mount /dev/sdb10 /boot/efi
[parasetu@Pasec ~]$ sudo tar xfv ~/efi.tar -C /boot/efi
tar: /home/parasetu/efi.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
idk what else to do , been troubling you all from past 2 days
this: ~/efi.tar
is where your file is (or should be)
I don’t know why it is not there - it may be in /root
I haven’t kept track closely here.
If you are working from a live system and have rebooted in the meantime - the file will be nowhere
or perhaps in oblivion
… you should know where you have put it
Also:
you have mounted /dev/sdb10 to /mnt
but it should be at /boot/efi - that is where the command expects it to be
I just saw that you did that in the end
but the .tar file is not where it should be
and thus the command fails
UEFI firmware supports booting from removable storage devices such as USB flash drives. For that purpose, a removable device is formatted with a FAT12, FAT16 or FAT32 file system
It’s difficult to say with so many distros and EFI partitions. We don’t know exactly how everything is configured, or the boot priority.
Don’t turn your computer off, until this is fixed. If you do you may need a live USB to fix it. Create a live USB before you do anything else, just in case.
Assuming you’re running manjaro…I’d say the best course of action is to make sure that /dev/sdb10 is mounted at /boot/efi, then run sudo install-grub, this should install grub, and detect the other distro’s.
That was a lot of effort and problems with just creating and extracting a tarball. I’m reluctant to just say some commands to bring an old snapshot to your root, if you can’t at least try to understand what each step does. (And act accordingly with things like errors.) Plus, I will make assumptions like, that you know you cannot make a new filesystem on a currently mounted one. (But I guess you don’t?)
But since were on a post about your EFI partition, why don’t we clean it it up some more. I thought others found the FAT16 partition was for another OS. But if not? I noticed the layout is different than all my Manjaro installs.
Inside that EFI paritition, you’re missing a directory/file. I have:
It shouldn’t be hurting anything, but you have had a (older) Windows OS take a **** in it. You may as well clean it up: sudo rm -r /boot/efi/\$RECYCLE.BIN /boot/efi/System\ Volume\ Information
With find /boot/efi you should see the same as mine above.
Then you can create the tarball. (the tar cfv command.)
Oh man , we are back to stage 0 , the pc went off and now again it didn’t boot up with manjaro , and that same boring garuda bootloader came up :)) well i guess its better to give up now
all i feel like is FAT16 wasn’t kicking my b##t , why did i take the challenge , it was working fine.
well no doubt , that other systems grub bootloader is picking up manjaro , but the real issue , is the UUID was changed and on trying
i get nothing after mounting and it says no such directory exist and even tho @Molski has mentioned as to copy and paste it , i’m sure , i’ll need a ton of information to execute that only , so maybe take a leave , and if someday i get to understand it , i’ll execute it further
okay people , so i tried fixing it again with live usb
so my efi partition was FAT32 , and flagged with boot and esp
then the first step that i did was mounted the root partition of Manjaro
next step was editing the /etc/fstab file and putting the new UUID
saving and exiting and then un-mounting ,all this i have understood now
now it was time to restore grub bootloader
so i did root and manjaro-chroot -a
which listed all my linux os and asked me to choose the number for manjaro , which i did
so i further tried pacman -Syu grub
but this command didn’t get executed as my system hasn’t been updated from long and it resulted in error , so i closed the terminal and restarted my comp
this time i got to login and access my manjaro
there i tried to install grub using sudo update grub which installed some 0.1 mb file
and to configure it , grub-mkconfig -o /boot/grub/grub.cfg
after a few restarts the system was working , even tho the manjaro grub bootloader didn’t load up on boot , and then i turned of computer and later came back removed the live usb and tried to boot into manjaro and now i’m welcomed by another error
Failed to stat resume device '/dev/disk/by-uuid/8eb80e10-0b17-4e68-8d79-e1c69a79
2054` : No such file or directory
_
again i have booted with live usb and lsblk -f and realised now it’s something with swap memory of manjaro,i.e - sdb9
in the discussion , they point out using hibernation as a cause , which would have resulted into some dummy storage on swap and its not accessible , in my case the pc went off due to power cut , does that mean , swap got corrupted and can i format and remake it just like efi and then change the UUID in /etc/fstab?
yes sir , i did it , it matches with the one lsblk -f
# /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=6E2B-F8D9 /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
ah , how is that to be checked ? i’m currently in live usb ,and all the swap partitions have the option to turn them on as swapon in gparted , but , i don’t think it will be a valid solution to the problem ,
