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.

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.

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.

That’s great, until you want to switch devices while still keeping your progress.

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.