Important Edit
The information below applies to emergency mode boot when grub is intact but OS isn’t booting. It doesn’t apply to grub rescue. Sorry about that folks, I screwed up here and don’t wanna misinform.
—————-
Protip: If you see this error, press”e” on grub boot to edit your commands and add the following to the end of the kernel line in grub:
fsck.repair=yesThen boot.
Fixes the issue like 90% of the time.
I remember my dad telling me a joke about FSCK and the reason it looks like a censored form of “FUCK” is because if you ever had to use it, you were basically fucked.
Personally, I had never had a problem with it. It just repaired errors on the disk or at least searched for them, IIRC. It’s been a long ass time since I even heard the joke, let alone used the tool. This just reminded me of it.
I know it’s a meme, but I’ve never had this happen to me. What causes this?
Usually anything where the BIOS can find and boot Grub itself but Grub can’t finish the boot chain for whatever reason, like /boot being on a separate partition and your main partition gets corrupted or something
I’ve only gotten that when I’ve mistyped the encryption password. They really should improve the handling of that.
cryptomount -a insmod normal normalBut yes, it’s super annoying. Especially if you mistype it multiple times and you have to type that in multiple times.
deleted by creator