Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Error While Decoding Stream #0:1: No Space Left On Device

Featured Replies

I am using the binhex-plexpass docker container.  It worked fine for a very long time, but now I am having an issue with transcoding.  Whenever I stream something that needs to be transcoded it errors out.  I checked the container's logs and saw an error "decoder error".  I reached out to the Plex engineers and after looking at my log files we found out that it is erroring because there is "no space left on device".  It's strange because I have plenty of space on my device so I'm not entirely sure why it is thinking this.  I have included a screenshot of my transcoding path setup (I was told that /tmp is for RAM which is where I want the transcoded file to go), and I have also included a screenshot of my Plex log file that shows the error stating there isn't enough space.

 

Any help would be greatly appreciated.  I'm wondering if I have set the paths incorrectly, but then again, why would it work for so long and then begin to fail.  Unfortunately Plex has done all they can do so I'm wondering if there is something that this community could provide as a solution.  Thank you again!

 

Transcode setup.png

tmp setup.png

Plex Log File.png

Solved by Dolphin8564

  • 4 weeks later...

Also having this issue (and more similar issues with transcoding) lately with linuxserver-plex. Anyone have ideas why? Tried downgrading to Plex 1.29, but still no luck.

  • 2 weeks later...

Did you ever get this figured out? @ammonrose or @TheOnly2wo ? I'm currently running into this issue as well, the audio cuts out while playing, and I check the logs and it's nothing but thousands of entries of this kind of stuff:

 

Dec 27, 2022 20:43:06.085 [0x1548a2067b38] ERROR - [Req#e246207/Transcode/0b4c5fa62db6db55-com-plexapp-android/a3067125-0186-4238-adea-8a6a03c5e1ab] Error while decoding stream #0:1: No space left on device

 

I've had no issues streaming and transcoding locally to my stuff in my house, but outside of my house, other people are reporting audio issues, and I was able to replicate it on my phone connected to just 5G instead of WiFi. I'll note the media file in question I'm testing this with is defaulted to TrueHD 7.1 for audio, so unsure if it's related to that or not. I know I've seen issues in the past related to the audio codec/format for the default audio file, and switching to AC3 would fix other issues I've had in the past. May fix it here as well, but that's not really a fix in my view of things, just a work around. 

So yeah, this is the same issue I've seen before, and I've resolved it by simply selecting an audio file from the dropdown list other than TrueHD 7.1. So if I choose AC3 5.1, I don't run into this issue. In my docker logs in unRAID, I can see the error:

decoder error: 121
TrueHD processing failed with 121

I don't however know WHY this is happening. 

One person had suggested that the issue was with codecs folder needing to be deleted and restarting the docker. Another guy said that temporarily fixed it but the permanent fix was to increase the number of directories Linux can monitor:

https://forums.plex.tv/t/increase-the-number-of-directories-linux-can-monitor-notify/209156

That ones a bit beyond me, though I understand what they're saying, just not sure how to do that in a docker environment to make it persistent every time you restart the docker. 

I am also having this issue. When TrueHD 7.1 is used the audio cuts out and it get a lot of "No space left on device errors". I increased the number of directories linux can monitor but it didn't work.

  • 6 months later...

Did anyone ever get this fixed?

 

image.thumb.png.6fdab35df46eaa5587ae817536e45f4b.png

I don't think it's 7.1 audio because right now the file only has (EAC3 5.1) audio.

  • 2 weeks later...

I too have been getting this.  This happens while my Plex is idle, even.  Nothing is being watched.  Ive deleted EasyAudioDecoder before due to some suggestion i stumbled on before but clearly that hasnt worked.  I suspect it just gets redownloaded on the next restart or update.  Whats the answer here?

 

For the sake of thoroughness I'll also include the transcode settings i have in Unraid and in Plex to confirm that's not the issue:

 

Unraid lsio Plex containter
image.thumb.png.aa4450a0ef5a3f8d213d6ac440824b02.png

 

Plex

image.thumb.png.13ebacd8d11aa992b2c6b4525c62490d.png

image.png

  • Author

I have come to find out that this is Plex’s fault. They somehow break the audio codec every once in a while. The way to fix this is by deleting the files inside of the audio codec folder and restarting Plex. It’ll automatically redownload the proper codec and you should be good to go.

  • 5 months later...

I hate to necro this, but did anyone else come up with a solution for this? I've also deleted the audio codec and still have this issue. I even setup a job to just do this on the regular and restart the docker and I still get these filling up the entire log: 
 

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


image.png.2919cabd1fd31293e3dda69828312dc0.png

 

They just fill up the entire log and pegs the CPU, even when nobody is watching. Plex cranks up the CPU usage and maxes out for hours for no reason like this:

image.thumb.png.d02c7eedee05d3d1dc4ae3f648b871bf.png

 

Again - I've done the audio codec purge on the regular, it still does it after a reset once it sits idle for a spell.

 

I've rebuilt the entire docker, all stock, default transcode config:image.thumb.png.6d1dcf4a76e1e69ba5d87ce85e2b4330.png


Space is not an issue on the container. in my case it has 30gb free in the /transcode directory. I thought maybe it was a writing issue, so I even tried transcoding directly into ram and that didn't solve it either, so I went back and just use /tmp.
image.thumb.png.1f0eb4efacc210173b7103ccdd3c5934.png

 

If anyone has any insight, that would be amazing.

 

  • 11 months later...

Hi, Happy Christmas... just about :)

 

I was wondering if Plex team ever came up with an answer to this? 

 

I have the same issue.

 

Nothing is playing. So nothing should be having an error on decoding... 

 

The only thing happening on my server is that Plex running the following:

  • Checking Intros
  • Checking voice activity
  • Sonic analysis

Anyone any idea why people are getting 

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

constantly in the logs?

 

Thanks

 

 

 

 

 

  • 1 month later...

I was wondering the same thing. Has anyone come up with a definitive answer to this? 

  • Author
  • Solution

What others have mentioned and what has worked for me is deleting the files within the Codec folder. At first this didn't work, and it's because I realized that when I created the container, I saved it in a specific location and then deleted it later on, but it kept those files on my server. Down the road I created the container again in a different location. I realized I was looking at the old location's files and deleting the codec there. Once I found the correct one I deleted the Codec files and it worked! I cleaned up my files and systems after that to make sure they were all organized properly.

 

Beyond that I'm not sure what the solution is. This seems to be on Plex's end because when they come out with a new update it seems to break the codec files. I will say that I haven't had to do this for quite a while, but whenever I do, it's incredibly annoying.

 

EDIT: I'm marking this as the solution because it does work for people, but I encourage others to continue reading and contributing to this thread if this solution is not working for you.

Edited by Dolphin8564

  • 6 months later...

Looks like this is still an issue. I had crazy log spams with this same message, leading to hard server crashes I spent a month trying to nail down. Deleting the codec folder contents seems to have fixed the issue. Thank you for figuring this out, but frustrating that it's still a problem three years after the initial post.

  • 3 weeks later...

Had this exact issue. Deleting the codec directory contents and a restart of my container worked right away.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.