Ok… I think I resolved the issue.
Firstly, anyone reading this, I can’t recommend enough making sure you have scheduled backup’s of things such as your database. I learned that lesson a couple of years ago. Thank god I still practice it today.
I ended up pulling the com.plexapp.plugins.library.db from my server, onto my desktop.
I then used SQLite to verify the integrity of my db. Sure enough, it popped out a bunch of errors talking about how the database was malformed.
So I ran the commands (https://support.plex.tv/articles/201100678-repair-a-corrupt-database/) to repair it. 3 minutes later, I’m all done with a “new” .db file.
I go back to my plex server. I backup my messed up DB, because… back ups. Better to have it and not need it than not have it.
I then deleted the .com.plexapp.plugins.library.db-wal and -shm files. Once done, I imported my rebuilt db to it’s original folder, and started the server up.
If anyone is having this issue, I can’t stress enough, if you don’t delete the wal and shm file, you’ll see in your unraid logs “Starting Plex Media Server” repeating… forever.
Got my server up and running on a database that’s about 2 weeks ago. Ran an optimize database. Took a little longer than usually (about 2minutes), but I watched it rebuild the wal and shm files (shm is only like 1.5mb, while my wal file is the same size as my db (240mb).
We’re back online, I can run my optimization. I’ve went a head and backed everything up again as of today.
We’re good to go.
If any users have this issues, feel free to reply to this thread with questions on what exactly I did in better detail and I will help.
tl;dr - Couldn’t optimize my database. Database ended up being badly corrupt. Used SQLite 3 to repair/rebuild. We’re g2g.
