Resolving a Grub Rescue Unknown Filesystem error during a Windows 11 and Artix Linux dual-boot setup requires identifying the correct boot partition and reinstalling GRUB. This issue typically stems from mismatched UUIDs or missing bootloader files on the EFI System Partition. By chrooting into your Artix installation and regenerating the configuration, you can restore access to both operating systems without data loss.
Understanding the Root Cause
The "Unknown filesystem" message in GRUB rescue mode indicates that the bootloader cannot read the partition containing its own configuration files or the kernel images. In a dual-boot environment with Windows 11 and Artix Linux, this almost always occurs because the GRUB configuration points to an incorrect Universally Unique Identifier (UUID) for the EFI System Partition (ESP) or the root filesystem. When you install Artix Linux, it uses specific init systems like runit, openrc, or s6. Unlike Arch Linux, which relies heavily on systemd, Artix does not use systemd by default. Consequently, standard tools likebootctl are irrelevant unless you have manually installed systemd-boot alongside GRUB. Since the error specifies GRUB, we must focus on repairing the GRUB instance rather than switching bootloaders. The discrepancy usually arises when disk partitions are reformatted, moved, or when the initial installation script failed to write the correct UUIDs to /boot/grub/grub.cfg.
Before proceeding, ensure you have a live USB of Artix Linux available. You will need to boot from this media to access the terminal and repair the broken bootloader on your internal drive.
Distinguishing Artix from Standard Arch
It is crucial to recognize that Artix Linux is a rolling release distribution that eschews systemd. If you followed generic Arch Linux guides, you might have attempted commands that assume systemd services. For example, runningsystemctl enable grub will fail because the service does not exist. Instead, Artix users must rely on manual configuration files or package-specific hooks provided by their chosen init system. This distinction prevents confusion when navigating directory structures and service management during the repair process.
Identifying the Correct Partitions
The first step in recovery is to map out your current disk layout. Boot into your Artix Linux live USB and open a terminal. Use thelsblk command to list all block devices along with their sizes and mount points. This visual aid helps you distinguish between the EFI System Partition, which is typically FAT32 formatted and around 500MB, and your root partition, which may be ext4, btrfs, or xfs.
You should also verify the UUIDs using blkid. Compare these UUIDs against what GRUB expects. If the UUID stored in your GRUB configuration does not match the actual partition UUID, the bootloader will fail to locate the necessary files. Note down the device path (e.g., /dev/nvme0n1p1) for your ESP and your root partition.
Chrooting into the Broken Installation
To fix the bootloader, you must operate within the context of your installed Artix system. Begin by mounting your root partition to/mnt. If you have a separate home partition, mount it to /mnt/home. Next, mount your EFI System Partition to /mnt/boot/efi. It is vital that the ESP is mounted at this specific location if your Artix installation was configured to store GRUB files there.
After mounting the filesystems, bind the essential virtual filesystems to allow the chroot environment to function correctly:
mount --bind /dev /mnt/devmount --bind /dev/pts /mnt/dev/ptsmount --bind /proc /mnt/procmount --bind /sys /mnt/sys
arch-chroot /mnt. Although the command name suggests Arch, it is compatible with Artix because it simply changes the root directory and executes a shell. Inside this environment, you now have access to your installed packages and configuration files as if you were booted into the main system.
Reinstalling and Configuring GRUB
With the chroot active, the next step is to reinstall GRUB to ensure all binary files are present and correctly linked. Use thegrub-install command targeting your EFI partition. For NVMe drives, the command might look like grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB. This command writes the bootloader code to the EFI partition and creates the necessary NVRAM entries.
After installation, generate a fresh configuration file. Run grub-mkconfig -o /boot/grub/grub.cfg. This command scans your system for kernels and initramfs images, detects the current UUIDs of your partitions, and writes them into the new configuration file. This step directly addresses the "unknown filesystem" error by aligning the bootloader's expectations with reality.
If you are using a specific init system like openrc, ensure that any required hooks are enabled. For Artix, this often involves checking that the grub package is properly integrated with your init system's update mechanisms. However, manual regeneration via grub-mkconfig is the most reliable method for immediate fixes.
Verifying the Fix
Exit the chroot environment by typingexit, then unmount the partitions in reverse order: umount -R /mnt. Reboot your machine. You should now see the GRUB menu offering choices for Artix Linux and Windows 11. Select each option to confirm they boot correctly. If Windows fails to appear, you may need to disable Secure Boot temporarily or check the Windows bootloader entry in GRUB.
For further assistance with dual-boot configurations, consider reviewing related troubleshooting guides. See Dual-Booted Laptop Can't Shut Properly, Causing Overheating: A Comprehensive Guide for insights on power management conflicts, or check Double Booting Windows 11 and Ubuntu 20.04 LTS on a New HDD for general hardware partitioning advice.
Frequently Asked Questions
Why doesn't my Artix system use systemd-boot?
Artix Linux is designed to be free of systemd, offering alternative init systems like runit, openrc, and s6. While you can install systemd-boot, the majority of Artix users stick to GRUB for its broader compatibility and simpler configuration structure. Using systemd-boot requires additional setup steps that are not standard in base Artix installations.What if I don't have a separate EFI partition?
Modern UEFI systems require an EFI System Partition formatted as FAT32. If you lack one, you must create it using a tool likefdisk or gdisk before installing GRUB. Without this partition, the bootloader has no compliant storage location for its firmware interface files, leading to boot failures.
Can I fix this from Windows 11?
No, you cannot repair GRUB from within Windows. Windows lacks the tools to modify Linux bootloader configurations or mount ext4/btrfs partitions natively. You must use a Linux live USB to access the terminal and execute the repair commands described above.Does disabling Secure Boot help?
Disabling Secure Boot can resolve issues where GRUB signatures are rejected by the motherboard firmware. However, it is not a direct fix for unknown filesystem errors. Secure Boot primarily affects authentication; the filesystem error indicates a path or UUID mismatch that must be corrected in the configuration file.How do I prevent this from happening again?
Avoid modifying partition tables while the OS is installed. Always regenerate GRUB configuration after changing disk layouts or upgrading kernels. Regularly backing up yourgrub.cfg file allows for quick restoration if manual edits introduce syntax errors or incorrect UUID references.