Fix Kernel Panic VFS Unable to Mount Root Filesystem on Linux

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 similar. The boot process halts, and the system drops to a initramfs shell or presents a black screen with the panic message. This typically occurs after a kernel update, disk reconfiguration, or filesystem corruption.

Root Causes

Missing or Corrupted initramfs/initrd: The initial RAM filesystem lacks necessary kernel modules (e.g., filesystem or storage controller drivers).
Incorrect root= Kernel Parameter: The boot loader passes a wrong root device (e.g., /dev/sda1 vs /dev/nvme0n1p1).
Missing Storage Driver: Kernel does not have the driver for the disk controller (e.g., SATA, NVMe, or SCSI).
Filesystem Corruption: The root partition is damaged or contains errors preventing mounting.
GRUB Configuration Error: Boot loader points to a non-existent kernel or initrd.

Step-by-Step Fix

1. Boot from Live USB or Recovery Mode

Use a Linux live USB to access the system's root partition. Mount the root partition (e.g., /dev/sda2) to /mnt and bind necessary directories:

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

2. Rebuild initramfs

Rebuild the initial RAM filesystem to include all necessary modules:

Debian/Ubuntu: update-initramfs -u -k all
RHEL/CentOS/Fedora: dracut -f
Arch Linux: mkinitcpio -p linux

Ensure the correct kernel version is targeted. If the kernel was recently updated, confirm the new initramfs is generated.

3. Verify GRUB Configuration

Check /boot/grub/grub.cfg or /etc/default/grub for the correct root= parameter. Use blkid to find the UUID of the root partition and update the GRUB entry:

blkid /dev/sda2
# Example output: UUID="1234-5678"
# Edit /etc/default/grub and set GRUB_CMDLINE_LINUX="root=UUID=1234-5678"
update-grub   # Debian/Ubuntu
grub2-mkconfig -o /boot/grub2/grub.cfg   # RHEL/CentOS

4. Check Filesystem Integrity

Run fsck on the root partition (unmount it first):

umount /mnt
fsck -y /dev/sda2

5. Test Boot

Reboot and remove the live USB. If the system still panics, boot into GRUB and edit the kernel line to add break (for dracut) or debug to drop into a shell before mounting root. This helps identify missing modules.

Alternative Fixes

Manual Module Loading: At the initramfs shell, manually load the storage driver: modprobe ahci or modprobe nvme, then exit.
Use Fallback initramfs: Some distributions keep a fallback initramfs (e.g., /boot/initramfs-5.10.0-fallback.img). Boot with that image from GRUB.
Reinstall Kernel: If the kernel image is corrupted, reinstall the kernel package: apt install --reinstall linux-image-5.10.0 or yum reinstall kernel.

Prevention

Always rebuild initramfs after kernel updates: Use automatic hooks (e.g., update-initramfs -u in Debian).
Use UUID in GRUB: Avoid device names like /dev/sda1 which can change. Use root=UUID=....
Keep a backup kernel: Maintain at least one older kernel in GRUB menu.
Test boot after major changes: After disk or filesystem changes, reboot with a live USB ready.
Enable serial console logging: If headless, capture kernel messages via serial console for debugging.