Hello! I am hoping someone can help me as I am desperate to not have to start over with plex. I recently upgraded my unraid server from 6.9.2 to 6.12.10 and upon doing so plex failed to start after the upgrade.

 

It kept showing the error
 

Unable to set up server: sqlite3_statement_backend::prepare: attempt to write a readonly database for SQL

 

I started searching for answers and I have tried following the advice found in this topic:

I also followed along to this guide to try and fix a corrupt database:

https://www.reddit.com/r/PleX/comments/qitj8k/database_errors_seemingly_unrepairable/

This reported "OK" and I was able to make it through the entire guide without issue.

Neither of those worked and the error persists.

Here is where it gets interesting. I decided to downgrade again to see if that fixed it. It did! Plex was working again. This made me feel it wasn't an issue with the database. This created a new problem though, as during the downgrade process Community Apps was removed  (along with my pre-clear plugin and my wireguard plugin). I was unable to get Community Apps installed again (even using the legacy install link) so this left me with really no choice but to upgrade yet again.

 

One final note: I am using linuxserver/plex
I tried setting up another plex instance using the official Plex-Media-Server docker and copying over the database files but that still throws the same error.

 

I have no idea what else to try and I would really appreciate some help! I have attached the diagnostics in case that can help.

 

 

tower-diagnostics-20240529-1343.zip

I am having the exact same problem. Plex (lscr.io/linuxserver/plex) was running fine until I ran an update last night. The docker log just shows the same error you received. I used ChuckPA's Plex DB Repair tool and my database passed all the checks but that did not solve the problem. I will try to downgrade versions of the docker.

I just noticed that both com.plexapp.plugins.library.db and com.plexapp.plugins.library.blobs.db were owned by root/root. Changing that to nobody/users at least allowed the database migration script to start running.

Awesome find Savik! I am going to give that a shot and see if that solves the issue.

 

Edit: Switching the file owner fixed my issue as well. Plex was able to start.

Edited June 3, 20241 yr by itsmepetey