error: unknown filesystem. Entering rescue mode... grub rescue>
GRUB can’t find or read the partition holding its files — common after resizing/deleting partitions or installing Windows alongside Linux.
Seen on:
Linux
Meaning
GRUB’s core image remembers where /boot/grub lives. Moving, resizing or deleting that partition (or Windows overwriting the boot loader) leaves it pointing nowhere.
Common causes
- Partition containing /boot deleted, moved or resized
- Windows installation/update changed the boot setup
- Disk order changed (new disk added)
⚡ Quick fix
- From grub rescue: find the partition with ls, set prefix/root, insmod normal, normal
- Then reinstall GRUB from Linux
- Or boot a live USB and reinstall GRUB (boot-repair)
Detailed fix by platform
GRUB
- bash
grub rescue> ls grub rescue> ls (hd0,gpt2)/boot/grub grub rescue> set root=(hd0,gpt2) grub rescue> set prefix=(hd0,gpt2)/boot/grub grub rescue> insmod normal grub rescue> normal
Ubuntu
sudo grub-install /dev/sda && sudo update-grub # after booting into the system
How to diagnose
- Partitions — ls in grub rescue
- Change — Recent partitioning/Windows install?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 0xC000000F Your PC needs to be repaired: The Boot Configuration Data file is missing some required information (0xc000000f)
- Argument list too long bash: /bin/rm: Argument list too long
- Automatic Repair couldn't repair your PC Automatic Repair couldn't repair your PC — Log file: C:\Windows\System32\Logfiles\Srt\SrtTrail.txt
Most viewed in Linux
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026