It’s only needed is the OS isn’t booting. Running a repair every boot is not needed.
It’s only needed is the OS isn’t booting. Running a repair every boot is not needed.
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.
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=yes
Then boot.
Fixes the issue like 90% of the time.
I knew it was gonna be Audiobookshelf as soon as I saw the headline. Great software. My wife has all her books hosted on it on our NAS, and it barely takes any resources. I have it hosted alongside Plex in a VM on a teeny tiny Ryzen 5500u Mini-PC.
Edit - I’m even more amused that I have almost the same configuration as the article author, Proxmox server hosting the guest, just mine’s an Ubuntu 24.04 server VM instead of LXC. That little server hosts Plex, Audiobookshelf, Lyrion, and AssetUPnP, pretty much handles all my media stuff, plus a separate Home Assistant VM, and has resources to spare.
Well shit. You’re right, I’m mixing up grub rescue and emergency mode. Yeah, you would need a USB rescue disk to fix this most likely.
My bad, I’ll update the original comment to avoid confusion.