sudo fsck -f -v /dev/sda10 ✔
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for manjaro:
fsck from util-linux 2.36.1
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
519263 inodes used (15.85%, out of 3276800)
3904 non-contiguous files (0.8%)
728 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 440355/323
7923946 blocks used (60.54%, out of 13088768)
0 bad blocks
1 large file
407969 regular files
28172 directories
0 character device files
0 block device files
2 fifos
70404 links
83108 symbolic links (78572 fast symbolic links)
3 sockets
------------
589658 files
Did you recently change any partitioning between now and before these grub issues?
A last attempt I can think of is to try disabling a couple ext4 features on your root file system. Outside of a chroot, and make sure /dev/sda10 is not currently mounted:
What is the output of:
tune2fs -l /dev/sda10
One finicky option to disable is metadata_csum_seed:
Doesn’t look like your root file system is using any unsupported features for Grub to work with.
This is very strange.
What is the output for
sudo parted -l
I’m nearly out of ideas and hopefully someone who has better nuance with Grub problems can chime in. The last-ditch solution might be to re-install Manjaro and copy over your home directory from a backup or extra copy.
Your EFI System Partition (esp) is /dev/sda2, not /dev/sda11. What is sda11? I noticed you treated sda11 as your “esp” earlier in this thread. It’s also a bit on the smaller side (sda2) at only 105MB. Might not make a difference now, but 256MB+ is a safe future-proof size.
According to your GPT partition layout, it’s sda2. sda11 is just another FAT32 partition. Either sda11 used to be your esp in the past, and something about Windows 10 might have changed it to sda2; or sda2 always was your esp, and I’m not sure what sda11 was created for.
Each device can only have one exclusive esp, as noted by the flag “EFI system partition”
Try this hail-mary attempt. The steps you took in your very first post, redo them once again from a fresh live session boot, but this time change just one thing:
@sonal check out the Wiki page @linux-aarhus linked to. And while you’re in a live session, what are the contents of the following directories, in this order:
sudo mkdir /mnt/sda2
sudo mkdir /mnt/sda11
sudo mount /dev/sda2 /mnt/sda2
sudo mount /dev/sda11 /mnt/sda11
ls -lhaR /mnt/sda2
ls -lhaR /mnt/sda11
Make sure nothing is already mounted. I know it’s repetitive, but booting into a new live session is your best bet to get the right output, especially if you’re been mounting and chrooting already.
EDIT: Added the -R recursive option to the ls commands.