GRUB Unknown Filesystem: How to Fix Linux Bootloader Error

What the GRUB "unknown filesystem" Error Means

When booting Linux, you see the message error: unknown filesystem or end up at the grub rescue> prompt? This means GRUB (Grand Unified Bootloader) cannot recognize the file system type on the partition where its modules, the grub.cfg configuration file, or the kernel image are stored. As a result, the system cannot proceed past the bootloader stage.

The error typically appears immediately after BIOS/UEFI, before the Linux kernel starts loading. The full text may vary depending on the GRUB version, but the essence is the same: the bootloader encountered a partition it cannot read.

Common Causes

The unknown filesystem error occurs due to several specific reasons:

1. File system corruption on the /boot partition — if the partition containing bootloader files (e.g., /boot) has errors, GRUB may fail to recognize it.
2. Incorrect file system type in GRUB configuration — an incorrect type is specified in grub.cfg or module settings (e.g., ext2 instead of ext4 or btrfs).
3. Missing GRUB module for file system support — if you use a less common file system (Btrfs, ZFS, exFAT), the corresponding module may not be loaded or installed.
4. The /boot partition is not mounted or is mounted incorrectly — particularly relevant for systems with a separate /boot partition.
5. File system superblock corruption — critical damage to the file system structure that prevents GRUB from reading metadata.
6. Using a file system not supported by GRUB by default — for example, NTFS or exFAT without additional modules.

Solutions

Method 1: Quick Fix via grub rescue

If you're already at the grub rescue> prompt, you can manually boot into the system to fix the configuration later.

1. At the grub rescue> prompt, run ls to see the list of partitions. GRUB labels them as (hd0), (hd0,msdos1), (hd0,gpt1), etc.
2. Find the partition containing /boot or kernel files (usually vmlinuz and initrd). To check, use ls (hd0,1)/ to view its contents.
3. Set the correct partition as GRUB's root:

   set root=(hd0,1)
   

   Replace (hd0,1) with your actual partition.
4. Load the normal menu module:

   insmod normal
   

5. Switch to the normal GRUB menu:

   normal
   

6. Now select the appropriate menu entry and boot into the system.

After successfully booting, you must fix the GRUB configuration to prevent the issue from recurring. Reinstalling GRUB or updating the configuration usually helps (see Method 2).

⚠️ Important: If the error returns after a reboot, the problem lies in the configuration or file system, not temporary settings. Proceed to the next methods.

Method 2: Recovery Using a Live USB

This is the most reliable method if grub rescue doesn't work or you cannot boot at all.

1. Boot from a bootable medium (Live USB/DVD) of any Linux distribution.
2. Open a terminal.
3. Identify partitions using lsblk or fdisk -l. Find your root partition (e.g., /dev/sda2) and the /boot partition (if separate, e.g., /dev/sda1).
4. Mount the root partition:

   sudo mount /dev/sda2 /mnt
   

   If you have a separate /boot:

   sudo mount /dev/sda1 /mnt/boot
   

5. Mount system virtual file systems for chroot:

   sudo mount --bind /dev /mnt/dev
   sudo mount --bind /proc /mnt/proc
   sudo mount --bind /sys /mnt/sys
   

6. If using UEFI, mount the ESP (EFI System Partition):

   sudo mount /dev/sda1 /mnt/boot/efi   # path may vary
   

7. Enter the chroot environment:

   sudo chroot /mnt
   

8. Reinstall GRUB to the disk (not the partition!). For BIOS:

   grub-install /dev/sda
   

   For UEFI:

   grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
   

9. Update the GRUB configuration:

   update-grub
   

   This command automatically detects the kernel and generates the correct grub.cfg.
10. Exit chroot and reboot:

    exit
    sudo reboot
    

Method 3: Checking and Repairing the File System

If the issue is file system corruption, you need to run fsck.

1. Boot from a Live USB (as in Method 2).
2. Before mounting the /boot (or root, if /boot is inside it) partition, run a check:

   sudo fsck -y /dev/sda1   # replace with your /boot partition
   

   For ext-based file systems, add -f to force a check.
3. If fsck found and fixed errors, try mounting the partition again and reinstalling GRUB (Method 2).
4. For Btrfs or ZFS file systems, use their native utilities (btrfs check, zpool scrub).

💡 Tip: Only run fsck on unmounted partitions. Otherwise, further corruption may occur.

Method 4: Updating the GRUB Configuration

Sometimes grub.cfg is outdated or contains errors.

1. Boot into the system (via grub rescue or Live USB with chroot).
2. If using chroot, ensure the partition is mounted.
3. Regenerate the configuration:

   update-grub
   

   Or, if update-grub is unavailable:

   grub-mkconfig -o /boot/grub/grub.cfg
   

4. Verify that grub.cfg correctly specifies paths to the kernel and initrd. Open the file and locate the linux and initrd lines.
5. If you use a non-standard file system, ensure the necessary modules are loaded at the start of grub.cfg (e.g., insmod btrfs).

Method 5: Support for Specific File Systems

If you use Btrfs, ZFS, exFAT, or NTFS for /boot, GRUB may lack the necessary modules.

1. Install additional packages:
   • For Btrfs: sudo apt install grub-btrfs (Debian/Ubuntu) or sudo pacman -S grub-btrfs (Arch).
   • For ZFS: sudo apt install grub-zfs (if available) or configure manually.
   • For exFAT/NTFS: install grub-ntfs or build GRUB with support.
2. After installation, rerun update-grub.
3. Manually add module loading in /etc/grub.d/40_custom or the main config if not added automatically.

Prevention

To avoid the unknown filesystem error in the future:

• Use file systems supported by GRUB for the /boot partition. ext2, ext3, and ext4 are recommended. Avoid NTFS/exFAT for /boot.
• Do not edit grub.cfg manually. Instead, configure parameters via /etc/default/grub and scripts in /etc/grub.d/, then run update-grub.
• Keep GRUB updated alongside your system: sudo apt upgrade grub or equivalent.
• Back up your configuration before making changes:

  sudo cp /boot/grub/grub.cfg /boot/grub/grub.cfg.backup
  

• Avoid interrupting a GRUB update (e.g., by cutting power).
• For UEFI systems, ensure the EFI System Partition is formatted as FAT32 and mounted correctly.