Error while decoding stream #0:1: No space left on device

Server Version#: 1.32.6.7557

This is getting ridiculous… Plex has been thrashing my NAS, SSD’s, and CPU for months with this error message –

[Req#3e6e312/Transcode/d18b2a71-01af-4c41-be89-b47c9106c023/6cb25dc6-7931-4bdb-b220-0090ef0145a8] Error while decoding stream #0:1: No space left on device

I have all forms of transcoding disabled and it’s definitely not a storage issue, yet the problem still occurs. There are no active streams and the errors start spewing a few minutes after service restart. I’d toss Plex entirely if it weren’t for PlexAmp, but even that is barely usable with a consistent 80% CPU usage. Any ideas on how to address the problem?

Does this happen when transcoding TrueHD audio?

There was a bug in the early 1.30 releases.

It should have been fixed in 1.30.1.6562.

I have no idea what it’s trying to transcode. As I said, there are no active streams and all transcoding is disabled. The directory in the error message is empty, so I have no real way of identifying what file it’s hung up on without installing a bunch of forensic tools. I’m also well beyond 1.30.1.6562 and running 1.32.6.7557 and it’s also been going on for months through various upgrades (and even trying beta versions).

  1. Verify Plex Media Server is configured for debug, not verbose, logging.
    Settings → Server_Name → General + Show Advanced

  1. Restart Plex Media Server

  2. When the problem re-occurs, pull the server log files (Settings → Troubleshooting) and upload the zip file to the thread.

The transcoder is used when rendering images even for display in the library, so without debug logs it would be hard to tell what’s going on.

Can you give us the output of df -h on your machine so we can confirm your disks aren’t full.

Unfortunately, it looks like the Plex Transcoder goes into a recursive loop if it comes across a corrupt file and the log files only display the process hash, along with a confusing (and probably incorrect) error message. This was occurring during the “Detect Intros” job, but the “Activity” window in the web interface was showing the prior job, “Detecting Loudness” in my case, making it even more challenging to identify what was really going on. Here was my solution to the problem.

Identify which file is causing the error (using /path/filename.ext as an example) –

$ ps -ef | grep 'Plex Transcoder'
plex       71075   56813 37 16:08 ?        00:00:14 /usr/lib/plexmediaserver/Plex Transcoder -codec:1 truehd_eae -eae_prefix:1 9ef92bc1-4198-4b03-a9aa-3a2ed4cdbe5a_ -analyzeduration 20000000 -probesize 20000000 -i /path/filename.ext -filter_complex [0:1] aresample=async=1:ochl='5.1':rematrix_maxval=0.000000dB:osr=48000[0] -map [0] -metadata:s:0 language=eng -codec:0 flac -b:0 4096k -f flac -map_metadata -1 -map_chapters -1 -t 1299.3054999999999 /tmp/ple /Transcode/Detection/914c53fe-7055-4746-b19b-ca0791add262 -y -nostats -loglevel quiet -loglevel_plex error -progressurl http://127.0.0.1:32400/video/:/transcode/session/9ef92bc1-4198-4b03-a9aa-3a2ed4cdbe5a/349b255f-4d8a-42ca-b591-c5fe3c945273/progress
ubuntu     74870   70817  0 18:22 pts/0    00:00:00 grep --color=auto Plex Transcoder

Optionally, verify the integrity of file in question using ffmpeg –

$ ffmpeg -v error -i /path/filename.ext -f null - 2>error.log

error.log showing a corrupt file –

[matroska,webm @ 0x55ca47547680] Element at 0x400f89f6 ending at 0x3a1a5d01b exceeds containing master element ending at 0x401742b4
Error while decoding stream #0:1: Invalid data found when processing input
    Last message repeated 2 times
/path/filename.ext: Stale file handle
    Last message repeated 4 times

Remove or replace the offending file. Once deleted, Plex should move on. You could also try extracting and remuxing the audio and video streams if the file is critical, but I’ll leave that up to the reader to Google how to do that with ffmpeg.

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