GRUB INSTALL ERROR: Unknown filesystem

here is the output, i did as you said:

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

Can you try repeating the above steps, starting from manjaro-chroot, on this fresh live session?

it gave me the same error again :frowning:

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:

tune2fs -O ^metadata_csum_seed /dev/sda10

You can retry from scratch after doing so.

This is quite odd. :confused:

no i have not changed anything, just booted into windows 10 doing my usual stuff.

here is the output

sudo tune2fs -l /dev/sda10                                     1 ✘ 

[sudo] password for manjaro: 
tune2fs 1.45.6 (20-Mar-2020)
Filesystem volume name:   <none>
Last mounted on:          /mnt
Filesystem UUID:          7f933636-d9d7-4565-b9e9-734b967e5530
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              3276800
Block count:              13088768
Reserved block count:     654438
Free blocks:              5164822
Free inodes:              2757537
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Tue Feb 16 06:50:23 2021
Last mount time:          Fri Apr  2 15:14:39 2021
Last write time:          Fri Apr  2 15:26:50 2021
Mount count:              1
Maximum mount count:      -1
Last checked:             Fri Apr  2 15:09:46 2021
Check interval:           0 (<none>)
Lifetime writes:          251 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      e88e69d3-87e2-462e-8d17-b5bd5d450da3
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0xe8704762

Now its saying i cannot mount sda10

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.

Here is the output

Is that in a clean live session?

Yes, its a clean live environment

Type it as a single command: sudo parted -l

check below:

 sudo parted -l                                                   ✔ 
[sudo] password for manjaro: 
Model: ATA WDC WD10JPCX-24U (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  473MB   472MB   ntfs         Basic data partition          hidden, diag
 2      473MB   578MB   105MB   fat32        EFI system partition          boot, esp
 3      578MB   595MB   16.8MB               Microsoft reserved partition  msftres
 4      722MB   160GB   159GB   ntfs         Basic data partition          msftdata
 5      160GB   160GB   866MB   ntfs                                       hidden, diag
11      160GB   161GB   922MB   fat32                                      msftdata
 6      161GB   524GB   363GB   ntfs         Basic data partition          msftdata
 9      524GB   527GB   3221MB  ext4                                       hidden
10      527GB   581GB   53.6GB  ext4
 7      581GB   936GB   355GB   ntfs         Basic data partition          msftdata
 8      936GB   1000GB  64.4GB  ntfs         Basic data partition          msftdata


Model: hp v150w (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 1      1049kB  16.0GB  16.0GB               Ventoy   msftdata
 2      16.0GB  16.0GB  33.6MB  fat16        VTOYEFI  hidden, msftdata

Looking at it now, but is it possible to copy + paste the text rather than take a photo? Makes it easier to read and select.

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.

sda11 is my efi boot partition

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”

may be my windows changed something,
windows is such a sneaky OS :angry:

please tell me what should i do now

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:

mount /dev/sda11 /mnt/boot/efi

Change it to…

mount /dev/sda2 /mnt/boot/efi

did the same–its giving me the same error

There’s a very interesting set of troubleshooting options on the Arch Wiki - for use when Windows has made changes as it they own the system.

@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.