Plex DRV has become a nightmare lately. I am trying to record all NCAA College softball and more than half of them are failing with the error “There was not enough disk space to start the recording.” False error as I have 2.4TB of free space. To Add to the frustration, many of the scheduled recordings are starting extremely late. McGyver last week recorded the last 5 minutes of the program, for no discernible reason. To add insult to injury, a recording scheduled for tomorrow at 6:30AM is already marked with the error “There was not enough disk space to start the recording.” Anyone have any ideas? Server is running on an Nvidia Shield, NAS is disk source, Live TV source is an HD Homerun Prime-3.
Where is the temp folder for the DVR recording located?
And how much space does it have available.
Good question. I do not know the answer. Where can I find this setting on the PMS?
I think it uses the transcoder temp directory,
One thing I’ve heard is that it checks to make sure it has enough space for the full show/movie before it begins.
I do not transcode so the directory entry is empty.
If you don’t specify one, It uses a default location… not sure where that is in your configuration…
I would guess then it is local storage in the Shield device then. When I moused-over the field it showed a path to the old attached storage. I’ll create a directory in the NAS and see if I can point to that.
Looks like that may have done it. The PMS created new folders in the NAS share and a recording kicked off that had previously failed and there a bunch of .ts files being generated in one of the session folders. This really should be documented better…
Well keep and eye on it and hopefully it’s the fix you needed.
Why plex doesn’t force you to set this directory, or hide the location automagically per library like .grab directory is beyond me.
I had random recording failures and it seems like it all came down to not having the transcoder directory set, because I never use a transcoder. What Plex doesn’t tell you is they use the transcoder as a segmenter so it is always running. SMFH.
Yup. Now that I am watching the directory, that is exactly what it is doing. Add the fact that the directory entry is free-form makes it all the more frustrating and shows me the issues I had with previous installs that could have been fixed with a simple entry…
Yeh, right…library location selection is a nice path chooser ui, but transcoder directory is just all plop a random string here 
That detail didn’t affect me, but I’m sure it throws n00bs for a loop.
actually I think they should populate the field with the default folder location so everyone knows where it is and if you change it then that’s what it shows.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
