Unraid 7.0.1 Update Killed my plex server

Server Version#: 1.41.5.9522
Player Version#:N/A All
Hi All,

After updating to the latest version of Unraid, i noticed my plex docker container was unable to start, i had a quick look at the logs and found that there was a database error, all good, ive had that before, i downloaded the latest version of the DB repair tool, and this time it didn’t work. nothing i tried worked. i told it to ignore errors, everything It just failed. When trying to restore from backup, each of my backups were corrupted too, for the time being, i’ve created a second appdata folder, and let plex build a new database, but i’m hoping someone out there can help me to fix my old one, its been around for quite a few years, so i’d like to not loose all the watch status ect that it still has for me and my family.

I’m hoping there’s someone with a bit more knowledge than me that can have a crack at the DB? if thats even possible, in the years i’ve been running plex i’ve never had a fatal issue like this before, bit of a kick to the teeth when it happened days after buying a plex lifetime pass (after being on a yearly subscription for all these years).

Happy to share logs if needed, but for the time being i’m trying to get something running so my mum can watch her show, once i get that stable i’ll be able to spin down the server, and point plex back at the old appdata folder.

Any and all suggestions are welcome!

What kind of error are you getting?
Can you show me ? (Server logs ?)

Hi Mate,

Just spun up the server pointing to the original appdata folder and this is what i get:

text error warn system array login

kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 40-plex-first-run: executing…
Plex Media Server first run setup complete
[cont-init.d] 40-plex-first-run: exited 0.
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing…
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
[cont-init.d] 50-plex-update: executing…
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version (N4soci10soci_errorE)
Stopping Plex Media Server.
Starting Plex Media Server.

Also the Main error i seem to keep getting in the repair tool is:

“Main database is too small/truncated, repair is not possible. Please try restoring a backup”

Your main DB is completely blown.

The DBRepair tool checks to see if the .DB is minimally 300 KB in size (minimum for a valid PMS DB). If it’s less than that. it will refuse to try.

Your choice is as it instructs or to wipe it all out and start over.

Bugger, well, new one is up and running again so i’ll just go from there.

Any idea what caused it? I’m a bit confused how updating unraid could have done it, maybe an ungraceful shutdown of the docker?

Ok, for anyone who stumbles on this in the future, the issue was with my file system, not plex. I had some weird issues pop-up trying to clean out the now useless files from the drive, turns out one of the disks in my array had a corrupt file system, following this guide:Checking and fixing file systems | Unraid Docs likely would have resolved my initial issue, sadly i had already deleted most of it, so by the time i realized what the problem was it was too late.

Todays lesson is: Check not only your docker container logs but your unraid OS logs, it was detecting issues plain as day and i didn’t see them until it was too late.

Live and Learn.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.