Insane number of errors claiming no space left since 1.41.7.9799, now on 1.41.8.9834

Server Version#: 1.41.8.9834

Plex Media Server Logs_2025-06-02_13-29-07.zip (1.8 MB)

Attaching logs, pinging @BigWheel for visibility.

Prior to this, I thought my issue was due to DB bloat. Cleared the bloat a week or so ago, but now I have a number of issues that just dont’ seem to be true, though Plex seems to think it is.

Just thousands of messages:
ERROR - [Req#1cfc4ed/Transcode/80eee178-3a2e-4a99-8d26-b1a1fa07fa15/5d4afea3-ab1b-4481-bb15-cd5b48b5882d] Error while decoding stream #0:1: No space left on device

All the arrays that the system Plex is on are (at the most) 50% full, the one plex runs on is 88% free space. So I think this is some permissions issue. Can anyone tell me where to begin to track this down? DB has remained happily at it’s normal size since fixing in this thread.

This is running in Docker, and is not a new installation, but I guess maybe it’s possible that there’s some path change in the latest linuxserver.io build(s)? The symptoms of this issue are the same as when the DB was bloated… slow library loads, really slow and sometimes failing forward/rewind actions. This may be related to the DB growth issue. is there some other file that may have grown to an unmanageable size due to that massive DB bloat I had?

My primary client is nVidia Shield.

Are you using a ram drive or a non-default location for transcoder directory?

1 Like

Yes - I’ve defined the transcode directory in docker as /share/CACHEDEV4/transcode and put /transcode in the directory location in Plex settings.

That said, for all intents and purposes, I don’t really have anyone that transcodes… 95% of my streaming is direct play with the exception being the prerolls.

I looked further into this and my server is set to 262,000 (and change), I only have about 13,000 directories, so it’s not that! Thanks for the direction, though!

it could be doing something like making chapter thumbs or other task that uses the transcoder. Your server logs have completely rolled over so I cannot see the request that started it. Just that error is in most of the plex media server.logs except the newest one which at the end shows it failed trying to transcode an episode of the show Lost.

Jun 02, 2025 02:19:58.320 [139625895590712] ERROR - Failed to transcode file (69): /tv/Lost - {tvdb-73739}/Season 04/S04E05 - The Constant - (2008-02-28) - [Bluray-1080p h265 (TrueHD 5.1)].mkv

there is also this which mentions TrueHD which may be related EAE ( dolby’s Easy Audio Encoder) Jun 02, 2025 02:19:58.306 [139625925851960] ERROR - [Req#1d04425/Transcode/80eee178-3a2e-4a99-8d26-b1a1fa07fa15/5d4afea3-ab1b-4481-bb15-cd5b48b5882d] [truehd_eae @ 0x7f66604bbb80] error reading output: -1313558101 (Unknown error occurred)

You could maybe increase the number of logs it retains ( default is 5) by editing LogNumFiles in advanced settings https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/ to hopefull some number that it does not roll over. and we can see the start of request for transcoder

@BigWheel

New logs, maybe there’s more information in here.
Plex Media Server Logs_2025-06-04_09-48-27.zip (1.6 MB)

The thing about lost is, it’s never been watched by anyone, ever:

This may be credit-detection related as I’m also seeing a number of credit detection errors:

Jun 04, 2025 04:20:39.080 [140141879286584] ERROR - [CreditsDetectionManager] Mis-matching media items detected, skipping
Jun 04, 2025 04:20:39.084 [140141879286584] ERROR - [CreditsDetectionManager] Mis-matching media items detected, skipping
Jun 04, 2025 04:20:39.087 [140141879286584] ERROR - [CreditsDetectionManager] Mis-matching media items detected, skipping
Jun 04, 2025 04:20:39.090 [140141879286584] ERROR - [CreditsDetectionManager] Mis-matching media items detected, skipping
Jun 04, 2025 04:20:39.093 [140141879286584] ERROR - [CreditsDetectionManager] Mis-matching media items detected, skipping

I would expand my logging, but I’m running in Docker, and that article doesn’t give me the docker environment variable to set that. Is there another article that explains that?

The new logs contain the same error messages as the first set, and at the same time.

Jun 04, 2025 02:18:38.436 [140141868698424] ERROR - [Req#e9acc0/Transcode/502c51eb-b822-47ae-8eb9-e6add8fab738/0c6245d6-8e30-4301-b8fc-31898d2b4f34] Error while decoding stream #0:1: No space left on device
Jun 04, 2025 02:18:38.437 [140141800176440] ERROR - [Req#e9acc1/Transcode/502c51eb-b822-47ae-8eb9-e6add8fab738/0c6245d6-8e30-4301-b8fc-31898d2b4f34] Error while decoding stream #0:1: No space left on device
Jun 04, 2025 02:18:38.438 [140141873736504] ERROR - [Req#e9acc2/Transcode/502c51eb-b822-47ae-8eb9-e6add8fab738/0c6245d6-8e30-4301-b8fc-31898d2b4f34] [truehd_eae @ 0x7f2ae7480b80] error reading output: -1313558101 (Unknown error occurred)
Jun 04, 2025 02:18:38.438 [140141866359608] ERROR - [Req#e9acc3/Transcode/502c51eb-b822-47ae-8eb9-e6add8fab738/0c6245d6-8e30-4301-b8fc-31898d2b4f34] Error while decoding stream #0:1: Unknown error occurred
Jun 04, 2025 02:18:38.445 [140141868698424] ERROR - [Req#e9acc4/Transcode/502c51eb-b822-47ae-8eb9-e6add8fab738/0c6245d6-8e30-4301-b8fc-31898d2b4f34] [truehd_eae @ 0x7f2ae7480b80] error reading output: -1313558101 (Unknown error occurred)
Jun 04, 2025 02:18:38.445 [140141800176440] ERROR - [Req#e9acc5/Transcode/502c51eb-b822-47ae-8eb9-e6add8fab738/0c6245d6-8e30-4301-b8fc-31898d2b4f34] Error while decoding stream #0:1: Unknown error occurred
Jun 04, 2025 02:18:38.450 [140141879286584] ERROR - Failed to transcode file (69): /tv/Lost - {tvdb-73739}/Season 04/S04E05 - The Constant - (2008-02-28) - [Bluray-1080p h265 (TrueHD 5.1)].mkv

Do you have Intro Video Markers running as a Scheduled Task?

Plex analyzes the audio track to determine the Intro location.

Check the XML Info for the episode and see if intro markers are present. In Plex Web, mouse over the episode, click on the three dots in lower right corner, choose Get Info, then View XML.

Example: <Marker id="7647" type="intro" startTimeOffset="214174" endTimeOffset="293991">

The problem is that the beginning of the analysis has rolled out of the log files, so it is not possible to say what is causing the problem.

To increase the number of log files, edit Preferences.xml in the Plex Data Folder (stop PMS before editing).

Try this to manually initiate intro analysis:

  1. Stop & restart Plex Media Server. This bumps the log files.
  2. Wait 3 - 5 minutes for Plex to fully start and log the startup sequence.
  3. Open Plex Web to the Plex Console (Settings → Console)
  4. In a separate Plex Web window, manually analyze Lost s04e05 (three dots in lower right corner of episode → Analyze)
  5. If errors start filling the console, quickly pull the log files (Settings → Troubleshooting).
  6. If you do not see the huge amount of errors, let the analysis finish (it should take just a few seconds), then pull the log files.
  7. Post the log files to the thread.

I do not know if Intro Analysis is kicking off the error messages. Even if it is not, the above will show what happens when PMS starts and when it analyzes the tv episode.

Here, @FordGuy61
Plex Media Server Logs_2025-06-09_10-49-49.zip (1.5 MB), i don’t think it will do any good though… the errors immediately flood all 5 log files, however, I have analysis from the console below.

For the intro markers, in the file in questions (Lost, S04, E05,) there is no instance of “intro” or “endTimeOffset” in the XML for that episode.

What is the attribute in the Preferences.xml file to set the number of log files? The only one related to logs that I can find is “logDebug”.

Here is what happens immediately when I click analyze on that file (Lost S04 E05):

The errors in red eventually change to the “no space left on device” errors:

Those continue ad nauseum.

EDIT/Solution: I replaced that one episode, and the errors have disappeared.

EDIT 2: 6 hours later, log file holding steady at ~16 kilobytes total.

EDIT 3: The next day there’s a huge number of errors again. I’m sure the answer is to delete/replace the offending media, but I can’t see what the offending media is due to log overflow. Following up in new reply to this thread..

@FordGuy61 @BigWheel

Found this value. For anyone stumbling onto this thread, it’s “LogNumFiles”. I set it to 20, because whatever is happening is really filling up the logs REALLY fast.

So apparently there’s more than one file causing this issue, because it was back this morning. I just need to find the other files. No easy matter. This error is absolutely FLOODING the logs. Will report back. If either of you have a way to figure out the files with errors, that would be great.

@FordGuy61 @BigWheel

Overnight, I left the logs at 20, and it filled all 20 almost immediately, still not capturing what it’s processing that’s causing the error(s). Should I increase that to like… 100 or 200 overnight to see if I can get that?

EDIT: I ended up increasing it to 500. Hopefully in the morning there will only be like… 400 or something. So I can get to the bottom of this. Is there a way to suppress the excessive repeated messages I’m getting in the log files?

Not that I am aware of.

Realized I never asked. How much space is there?

On QTS, /share/CACHEDEV4 does not exist.

The correct path to use is /share/CACHEDEV4_DATA.

/share is a 16MB partition which is part of the root from the flash

Share your docker compose or current config please

If you are using /transcode on CACHEDEV4_DATA (DataVol4), Please confirm the shared folder settings and confirm there is no quota limit.

Your config spec should:

  1. map /share/CACHEDEV4_DATA/transcode to /transcode
  2. in the container PMS, your transcoder temp should be /transcode
  3. You must ensure permissions (control panel - shared folder) allow the PUID/PGID to write to it.

@ChuckPa
Yeah, that’s what it is, sorry, I manually typed that incorrect path into the post. I’m no slouch in Docker/QNAP/Container Station, but sometimes my typing leaves something to be desired. :slight_smile:

@BigWheel

A lot. Almost a Terabyte of free space (the entire drive is 1TB, and there’s 824GB free)

Good news, though, looks like 30 was the magic number for Logs, and it looks like (in my opinion) my TV show “Hunter” is the issue. I can’t put the logs here because it’s .9 MB too big, but here is a link to the Zipped log files.

I get this error for almost every episode of the show I have:

EDIT: Upon further investigation, the error is related to a bad rclone mapped show. It still exists in my “Stream TV” library, but not in the rclone location. I deleted it from my “Stream TV” library. I will clear the logs, then watch them over the next overnight to see what happens and if the logs are clearer.

EDIT 2: I’ve attached the relevant plex media server log file.
Plex Media Server.30 log.zip (229.3 KB)
It would make sense to get the “no space” errors, as Plex and/or really any process would have no write permissions to the rclone mapped directory at all. I’m pretty sure I found my issue. 24 hours will tell.

@BigWheel So, many of the errors have gone, however, there’s still a LOT of them. This is absolutely happening overnight during scheduled processing. This time, however, I know the answers are in the logs because there are SIGNIFICANTLY fewer. Would you be able to help me pinpoint what is going on and teach me how to research the logs so that I can pinpoint where I should be looking in the first place (or maybe there’s a white paper/existing instructional I could read about this?)? Does Plex have some kind of log disseminator that links events across a log file bundle? In any case here’s my overnight logs:
Plex Media Server Logs_2025-06-13_10-32-28.zip (7.1 MB)

Hmm. Seem like it may have started in log Plex Media Server.30.log There are a bunch of other types of errors I was not expecting to see. i am going to need to ask some of the server devs if they have an idea. Unfortunately the ones that would know have taken off for the weekend already.

I wanted to ask I see it looks like it is trying to scan multiple directories for the same show. I see multiple errors like this.

Jun 12, 2025 11:35:19.976 [139721312987960] INFO - Library section 2 (TV Shows) will be updated because of a change in "/tv/All in the Family - {tvdb-72741}/Season 03/S03E01 - Archie and the Editorial - (1972-09-16) - [DVD x265 (AAC 2.0)].en.hi.srt"
Jun 12, 2025 11:35:20.076 [139721384332088] WARN - Error scanning directory, we'll skip and continue: boost::filesystem::last_write_time: No such file or directory [system:2]: "/cartoons/All in the Family - {tvdb-72741}"
Jun 12, 2025 11:35:20.119 [139721384332088] WARN - Error scanning directory, we'll skip and continue: boost::filesystem::last_write_time: No such file or directory [system:2]: "/db_shows/All in the Family - {tvdb-72741}"
Jun 12, 2025 11:35:20.607 [139721384332088] WARN - Error scanning directory, we'll skip and continue: boost::filesystem::last_write_time: No such file or directory [system:2]: "/stream/default/All in the Family - {tvdb-72741}"
Jun 12, 2025 11:35:20.851 [139721384332088] WARN - Error scanning directory, we'll skip and continue: boost::filesystem::last_write_time: No such file or directory [system:2]: "/stream/default/All in the Family - {tvdb-72741}"

Something is wonky here. Were these recent moves of files from those directories?

I agree, but no, not recently, it’s possible sometimes I add shows to the wrong area, then move it later when I wonder why it’s not showing up in the correct library, however, yesterday I was doing maintenance with Sonarr and updating file names. I did go through show titles starting with A-D doing renames, so there’s a good number of file renames yesterday which were expected.

As far as the missing file names, db_shows designates an rclone debrid volume, and /stream/default is a library mapping to that db_shows directory. There’s nothing in those directories currently other than placeholder files so the library doesn’t end up empty. I also have nothing currently in my db account, so it’s not trying to map something online and failing.

That said, it’s possible “All in the Family” WAS in /db_shows, and then /cartoons before ending up in it’s correct directory, but those moves were done long ago.

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