I’ve only gotten that when I’ve mistyped the encryption password. They really should improve the handling of that.
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.
Anytime I’ve seen this error is because I’m messing about with partitions, the last time was a few months ago when migrating to a larger disk, so I’m not too sure about those 90%.
In any case, sounds like a very helpful tip if the error just shows up out of the blue.
dd would like to have a word about that… But still, another tool in the arsenal is always useful.
Thanks for the tip.
Yeah, that’s the other 10%. 😂
Doing dd wrong or rm -rf on / aren’t gonna be salvaged this way, but if it’s a bad disk sector or somehow corrupted system file the above command will sort it out. You wouldn’t believe how many customers VMs I’ve had to use that on in the past when they were in a panic. It’s a 2 minute fix in most cases.
It’s kind of the Linux equivalent to Windows sfc/scannow, chkdsk, and dism restorehealth in one.
Why isnt it default?
It’s only needed is the OS isn’t booting. Running a repair every boot is not needed.
Oh, thanks for the info
If it’s going to grub rescue then that’s before it can even get to the grub menu (thus no kernel line at this point). It’s usually easiest to boot to live/rescue ISO and reinstall grub. Sometimes you can manually load grub modules from lib to manually boot from the grub rescue shell to the normal grub shell, but that’s more advanced.
Not true, it’s grub rescue, appears after grub if the OS can’t boot. I’ve encountered this countless times at work over the years in customer environments.
I never run into this. Mostly because I don’t use grub
“Time to go to your backups”
