September 20, 20241 yr Community Expert My Plex Media Server seems to have issues and I'm out of ideas on how to resolve. When I try to open the WebUI from Plex App in Unraid I just get: This just started happening, no idea why, was in the middle of doing a MetaData update (via Plex WebUI) and suddenly these issues? I tried uninstalling and re-installing Plex Media Server, but same issue? (although not entirely sure the uninstall/reinstall cleared out prior config/settings). Check permissions and all is good, so really have no idea what this is about? "sqlite3_statement_backend::prepare: file is not a database for SQL: PRAGMA cache_size=5120" ??
September 20, 20241 yr Community Expert Look for the support thread/Discord for the container you are using:
September 20, 20241 yr Author Community Expert I have posted on Plex Support forum but thought I'd post here also since Plex Media Server is commonly used with Unraid. There are many threads on "soci_error: sqlite3_statement_backend..." but none that contained "file is not a database ..."
September 21, 20241 yr Community Expert 12 hours ago, RobAinscough said: I'd post here also since Plex Media Server is commonly used with Unraid. It his, but each container should have a dedicated forum support thread/Discord link.
September 21, 20241 yr Author Community Expert Solution Ok, I believe I’ve managed to discover the issue. I had installed Unassigned Drive plug-in which seemed ok, but then it showed “reboot” on one of my external HDD USB drives … doesn’t seem to like having two external USB drives … not really sure, but it triggered a reboot grayed out button under the Unassigned Drive list for one external HDD? When that happened (I just noticed now) one of my SSD drives that made up 3 drive Cache (2 SSD and one M.2) disappeared. AppData is setup to use Cache to Array as well as Media share that is used by Plex (both used by Plex). After 2 weeks of finally getting all my data transferred over to Unraid, I noticed an Unraid update, so let that install this morning and did a reboot … this is when I noticed my cache SSD was set to unassigned and I re-added back to my Cache array. So I suspect Unassigned Drive plug-in “may” have been the source of this.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.