gribse/recettes
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
recettes/Homelab/fix grub if linux doesn't boot.md
gribse ecdfa2f7c4 Squashed 'temp-repo/' content from commit 6688605 
git-subtree-dir: temp-repo
git-subtree-split: 6688605ad41f49d1eccead8d29421c658cad0100
2025-10-06 19:14:58 +02:00

1.4 KiB
Executable file
Raw Blame History

sudo nano /etc/fstab

The error indicates that the system is trying to mount /dev/nvme0n1p3, but it’s not listed correctly in /etc/fstab or the UUIDs/labels don’t match. Here’s how to resolve this issue:

  1. Boot into the System Temporarily

Use GRUB commands to boot into your system, as you did previously:

set root=(hd0,gpt6) linux /boot/vmlinuz-5.15.0-130-generic root=/dev/nvme0n1p3 ro initrd /boot/initrd.img-5.15.0-130-generic boot

Replace /dev/nvme0n1p3 with the correct partition if needed.

  1. Check /etc/fstab

Once the system boots, open /etc/fstab to verify the partition setup:

Look for the line referring to the root filesystem (/). It should match the correct UUID or device name.

  1. Find the Correct UUID

Run the following command to list all partition UUIDs:

lsblk -f

Identify the UUID of /dev/nvme0n1p3 (or your root partition).

  1. Update /etc/fstab

Replace the incorrect entry in /etc/fstab with the correct UUID for the root partition. For example:

UUID=correct-uuid / ext4 defaults 0 1

Save and exit.

  1. Update GRUB

After fixing /etc/fstab, update GRUB to ensure the correct configuration is saved:

sudo update-grub sudo grub-install /dev/nvme0n1

  1. Reboot

Reboot the system and verify that it starts correctly:

sudo reboot

If you still encounter issues, share the output of lsblk -f and the contents of /etc/fstab for further troubleshooting.

source : chatgpt