PLEX UNRAID Issues

Plex Media Server
,
1

Server Version#: 1.31.1.6733
Player Version#: 4.100.1
Been running into some weird issues and I’ve also opened a topic on the unraid forums as well thinking possibly hardware issues, but can’t seem to narrow it down.

My unraid server has been chugging along for years with little to no issues until recently. Nothing hardware wise has changed or software (minus a few OS / docker updates as they roll out, usually waiting a few weeks just in case).

For some reason though, I started seeing MCE hardware error logs in unraid. Then I noticed in PLEX, each morning, it would be stuck scanning credits on a show or movie. Always different, but would never progress. If I try to stop the docker, I get a error in unraid. I can’t kill the docker either as it is still accessing the file or is locked. I have to force unmount the cache drive and /or stop the docker service completely.

This just started happening. Unsure what logs or info you need form me. First time really posting anything as I’ve been pretty lucky with my setup. I ran a full MEMTest and all passed with no errors reporting. No other obvious errors showing up within unraid (SMART errors or otherwise).

Thanks in advance for any help!

2

I had to forcefully bounce my runraid server as plex became unresponsive and i couldn’t kill the docker. Plex docker will now no longer start. I get this when i open the logs on the docker.

services.d] starting services
Starting Plex Media Server.
[services.d] done.
Error: Unable to set up server: sqlite3_statement_backend::loadOne: attempt to write a readonly database (N4soci10soci_errorE)
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]
Starting Plex Media Server.
Error: Unable to set up server: sqlite3_statement_backend::loadOne: attempt to write a readonly database (N4soci10soci_errorE)
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]

3

so i fixed the database issue. somehow the appdata / docker folder lost some permissions. reset and it came right up, no errors.