Fix Kernel Panic: VFS Unable to Mount Root Filesystem

Symptoms

During Linux boot, the system displays a kernel panic with the message: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) or similar. The boot process halts, and the system may drop into a initramfs shell or a busybox prompt. Common variations include VFS: Cannot open root device or No such device.

Root Causes

• Missing or incorrect root filesystem driver (e.g., SATA, NVMe, or filesystem module not included in initramfs).
• Corrupted or missing initramfs (initial RAM filesystem).
• Incorrect kernel boot parameters (wrong root= UUID or device name).
• Filesystem corruption on the root partition.
• Hardware changes (disk controller, disk order) causing device name changes.
• LVM or LUKS configuration issues where the root volume is not unlocked or detected.

Step-by-Step Fix

1. Boot from Live USB/CD

Use a Linux live environment (e.g., Ubuntu Live USB) to access the system. Boot from the live media and open a terminal.

2. Identify the Root Partition

List available disks and partitions:

lsblk
fdisk -l

Identify the root partition (e.g., /dev/sda2 or /dev/nvme0n1p2). Note its UUID:

blkid /dev/sdXY

3. Mount the Root Filesystem

Create a mount point and mount the root partition:

mkdir /mnt/root
mount /dev/sdXY /mnt/root

4. Chroot into the System

Mount necessary virtual filesystems and chroot:

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

5. Check Boot Parameters

Examine /etc/default/grub and ensure GRUB_CMDLINE_LINUX contains the correct root= parameter (UUID or device). Example:

GRUB_CMDLINE_LINUX="root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Update GRUB:

update-grub

6. Rebuild Initramfs

Rebuild the initramfs to include necessary drivers:

update-initramfs -u -k all

Or for specific kernel:

mkinitramfs -o /boot/initrd.img-$(uname -r) $(uname -r)

7. Verify Filesystem Integrity

Check and repair the root filesystem (unmount first):

fsck -y /dev/sdXY

8. Reinstall GRUB (if needed)

If bootloader is corrupted, reinstall GRUB:

grub-install /dev/sdX
update-grub

Replace /dev/sdX with the disk (not partition), e.g., /dev/sda.

9. Exit and Reboot

Exit chroot, unmount everything, and reboot:

exit
umount -R /mnt/root
reboot

Alternative Fixes

• Use fallback initramfs: If you have a backup initramfs, boot with it from GRUB (select advanced options).
• Boot with nomodeset: Add nomodeset to kernel parameters if graphics driver causes issues.
• Switch to LVM/LUKS recovery: For LVM, run vgchange -ay in initramfs; for LUKS, use cryptsetup luksOpen.
• Restore from backup: If initramfs is missing, copy from a backup or reinstall the kernel package.

Prevention

• Always update initramfs after kernel updates: Run update-initramfs -u.
• Use UUIDs in boot parameters instead of device names (e.g., /dev/sda1).
• Maintain a backup kernel and initramfs in GRUB.
• Regularly check filesystem health with fsck.
• Test boot after hardware changes (new disk, controller).
• Keep LVM/LUKS configuration documented and test recovery procedures.

By following these steps, you can resolve the kernel panic and restore normal booting. If the issue persists, consider hardware failure or deeper filesystem corruption.