Server Version#: 1.42.2.10122
Player Version#: Any of them
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
These are all I have been getting suddenly out of the blue for the past 3 weeks. I made no changes prior to this. The server has been running consistently with no changes for years. None of my friends are able to play anything from any player, be it Web, Android, ios, etc. They all get one of these errors. I went back to a Windows image I created 3 months ago, just in case and the same happens.
I’ve read of similar errors going back years, but have been unable to find a solution. I even wanted to wipe everything and start from scratch, but stopped short of doing so after seeing some people who did this just to have it happen a week or so later. Please any solution to this would be appreciated.
I’m not a windows guy, but your logs scream, “no space left on device”:
Sep 18, 2025 04:46:33.487 [5356] ERROR - [Req#5b86c3/Transcode/4316b675-2e42-4581-9b1f-526ec1d04d5b/e9cf28be-9f4a-4ab4-b5d1-50bab491b04d] Error while decoding stream #0:1: No space left on device
Well, that would be completely unacceptable wouldn’t it. I find their silence on the matter to be baffling to say the least.
This is AFFECTING SO MANY USERS on DIVERSE PLATFORMS. How can it be ignored?
Starting from scratch to recreate something to painstakingly curated over years of Server ownership cannot be the solution.
I had considered that as a last resort until I saw on Plex Reddit that it came back for some people even after they started from scratch. So, it is not even a permanent Fix. It clearly points to the Media Server software being the issue.
If one wipes, only to reinstall the bad software, the issue will just return eventually.
I agree with the above. Don’t use a recoverable drive for the transcoder folder. Plex exists these files to get created fairly quickly and your drive may be too slow. Also don’t use the root folder.
It indeed is a RAM driver and has been functioning flawlessly for years. I had even increased it to 12GB and it resulted in the same error.
I later on changed it to my C:\ drive and not the root, and it still provides the same error. Thanks for pointing out the network part. That was indeed wrong. I have since corrected that.
That’s what I had too for about 8 years with no issues. But I don’t think that’s the issue as I have changed it to regular disk and still the issue persists. It
EDIT: So i missed a line in the log file. So editing this post in case it helps people in the future.
An example of the error below.
ERROR - SQLITE3:0x80000001, 11, database corruption at line 84326
Using the DBRepair script helped fix the issue. Thanks ChuckPA for developing that.
Throwing my hat in the ring. PMS has been working fine for years installed on Unraid. Yesterday in between plays i started getting this error.It still works through the Google TV device but everything else is broken.
Will start the rebuild of PMS to fix the issue but i hope Plex fix this one day…
Wow. Incredibly this worked for me too. Even though the scan returned no error or corruption.
All I did was restore my Database from a Windows Image I created way back in July. The Database from that month of July did the trick. I just had to rescan my entire library after that. But it all works for now. I will report back if the issue returns. Thanks. I hope everyone else at least have an old database that didn’t have an issue.
Hey @ChuckPa this appears to be a database issue then?
I have a backup from April 2025, hopefully I can recover my Plex DB and test.
I have previously ran your DB repair tool but it didn’t resolve my issue. Is there anything I can do in advance to help resolve this issue for others? Maybe OP here could as well?
I always perform a full Windows Image Backup of my Server every 3 Months. The Last time Plex worked well for me was in July and I luckily had backed up.. All I did was mout the image, went to the Plex Database folder and copied the July Database backup and replaced the current one, after wiping out everything in the Datase folder. Relaunched Plex, and it updated the database, then I just did a scan for the entirety of my media directories.
Everything started working. Which leads me to believe 2 things.
1 - It is a corrupt Database that is indeed causing the issue, but most people don’t know it because the Database repair tool says all is fine.
2 - I am just lucky and this replacement worked for me.
I do not want to jump to joy quite quickly because I have seen it work for others, only to then get bad again.
What are the below types and their uses
– Local (part of the machine) devices PMS uses
– Local logical devices PMS uses (e.g. software ramdisk)
– Network (LAN) storage devices
Size of the files (Directory listing) of the “Databases” directory
A “DEBUG server logs” ZIP file which captures a playback actually failing.
I unfortunately do not have this issue anymore. So I do not have the old database that caused the issue in question. Thanks for reaching out to assist. Much appreciated.
But to amswer:
PMS server uses the C: drive for installation and database storage.
The logical drive (which I’ve since stopped using) was Ramdisk software and 4GB in storage.
