Fix Kernel Panic: VFS Unable to Mount Root Filesystem

Symptoms

During Linux boot, the system displays a kernel panic with the message: VFS: Unable to mount root fs on unknown-block(0,0) or Kernel panic - not syncing: VFS: Unable to mount root fs. The boot process halts, dropping to a shell or freezing. Common variants include mount: unknown filesystem type 'ext4' or No filesystem could mount root.

Root Causes

1. Missing or corrupted initramfs/initrd – The initial RAM disk lacks necessary kernel modules (e.g., for the root filesystem driver).
2. Incorrect root= parameter in GRUB – The kernel command line points to a wrong partition (e.g., /dev/sda1 vs /dev/sda2).
3. Filesystem corruption – The root partition has a damaged superblock or filesystem structure.
4. Missing filesystem driver – The kernel was compiled without support for the root filesystem type (e.g., ext4, btrfs, xfs).
5. Changed disk identifiers – After disk reordering or moving drives, UUID or device names no longer match.
6. GRUB misconfiguration – Bootloader points to a wrong kernel or initramfs file.

Step-by-Step Fix

Prerequisites

• Live CD/USB of the same Linux distribution (or any recent Linux live environment).
• Root access to the live system.

Procedure

1. Boot from live media and open a terminal.
2. Identify disk partitions with lsblk -f or fdisk -l. Note the root partition (e.g., /dev/sda2).
3. Mount the root partition:

   mount /dev/sda2 /mnt

4. Mount other necessary filesystems:

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

5. Chroot into the system:

   chroot /mnt

6. Check /etc/fstab for correct root device UUID or path. Use blkid to get current UUIDs. Edit if needed: nano /etc/fstab.
7. Rebuild initramfs:
   • Debian/Ubuntu: update-initramfs -u -k all
   • RHEL/CentOS: dracut -f
   • Arch: mkinitcpio -p linux
8. Reinstall and update GRUB:

   grub-install /dev/sda
   update-grub

9. Exit chroot: exit
10. Unmount all:

    umount -R /mnt

11. Reboot and remove live media.

Alternative Fixes

• Filesystem check: If corruption is suspected, run fsck.ext4 -f /dev/sda2 (adjust filesystem type) from live environment before chroot.
• Manual kernel parameter: At GRUB menu, press e and edit root= to use UUID: root=UUID=xxxxxxxx. Boot with Ctrl+X.
• Restore from backup: If initramfs cannot be rebuilt, restore from a known good backup of /boot.
• Use fallback initramfs: Some distributions keep a fallback initramfs (e.g., initramfs-linux-fallback.img). Boot with that kernel line.

Prevention

• Always keep a live USB handy for recovery.
• Regularly update GRUB and initramfs after kernel updates: update-grub and update-initramfs -u.
• Use UUIDs in /etc/fstab and GRUB instead of device names (e.g., /dev/sda1).
• Backup /boot partition and /etc/fstab.
• Enable kernel crash dumps to capture logs for debugging.
• Test boot after disk changes (e.g., adding/removing drives).

Additional Notes

If the error persists after all steps, the kernel itself may be missing support for the root filesystem. Recompile the kernel with the required driver built-in (not as module). For custom kernels, ensure CONFIG_EXT4_FS=y (or your filesystem) is set. In virtualized environments, check that the correct storage controller driver (e.g., virtio, ahci) is included in initramfs.