Still seeing the out o space messages in the logs which doesn’t make sense since we moved the transcoder folder to your G:\ drive.
Jul 08, 2018 17:42:00.037 [18756] ERROR - [Transcoder] av_interleaved_write_frame(): No space left on device
Jul 08, 2018 17:42:00.038 [16064] ERROR - [Transcoder] Error writing trailer of G:\TV\.grab\24d4deef2c94a6c71cb326b4af7d1eaf493c1eec\TMZ (2007) - S11E264 - Episode 264.ts: No space left on device
I have posted a message on our Internal Slack room to see if any one else has any other ideas.
Thanks for the screenshot. The file system gives the reason for the error. FAT32 is limited to 2GB file size. A one hour recording at 1080 will be around double that size so around 4GB. Will probably need to move any files off that external drive and format as NTFS to be able to record anything more than 30 minute shows.
We have a successful recording!
The show completed without issue last night and I hope that we can now say the issue is resolved. Thank you SO MUCH for all your help–I really appreciate it!!
By chance is there a note about hard drive format documented anywhere for other folks who may run into this issue?
Awesome, good to hear it is now working. We are discussing where to put the File System information in the Support Guides. Don’t recall ever hearing of any other forum threads in which a drive formatted as FAT32 was causing the problem. Almost all drives I have seen recently except for some flash drives have all been NTFS. Even my new external WD HD is formatted as NTFS.
I have been having similar problems, but on a different platform:
FreeNAS 11.1U5
Plex Version 1.13.5.5291
DVR has been working perfectly on my older Windows machine. Now I’m attempting to graduate to a full NAS environment. There are 19TB of free space on the disk, so I am sure that it is not a file space issue.
The error occurs at 18:17 and change, the show is “KTLA 5 News at 6”
I am getting this issue when attempting to record Jeopardy, which is a half hour program. I am using the Nvidia Shield Pro as my DVR and all other media is stored on a different hard drive so I have more than 300GB of free space. My husband will not be pleased if the new episodes don’t record…and there is no on demand version of the show.
Had the same “transcoder error” tonight with the new back-to-back “Chicago …” TV shows here in Austin TX. During the recording of the 2nd show (Fire), about 21 minutes past the show start, recording failed with transcoder error. I have a WinTV quad card in my Kubuntu linux desktop with over 2T bytes of free space on my drive. Scanning the Plex logs for ERROR:
> tim1@vega:~$ grep ERROR /var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Logs/Plex\ Media\ Server.*log
> /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/Plex Media Server.4.log:Sep 26, 2018 19:57:00.192 [0x7fecd6bfc700] ERROR - Unable to find title for item of type 5
> /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/Plex Media Server.4.log:Sep 26, 2018 19:57:00.193 [0x7fecd6bfc700] ERROR - Unable to find title for item of type 5
> /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/Plex Media Server.log:Sep 26, 2018 20:21:51.653 [0x7fecda3ff700] ERROR - [Transcoder] av_interleaved_write_frame(): No space left on device
> /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/Plex Media Server.log:Sep 26, 2018 20:21:51.654 [0x7fecfafff700] ERROR - [Transcoder] [stream_segment,ssegment @ 0x25b6240] Failure occurred when ending segment 'media-05089.ts'
> /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/Plex Media Server.log:Sep 26, 2018 20:21:51.670 [0x7fecdd3fd700] ERROR - [Transcoder] Error writing trailer of media-%05d.ts: No space left on device
> tim1@vega:~$ df
> Filesystem Size Used Avail Use% Mounted on
> udev 7.8G 0 7.8G 0% /dev
> tmpfs 1.6G 1.7M 1.6G 1% /run
> /dev/nvme1n1p2 228G 39G 178G 18% /
> tmpfs 7.8G 29M 7.8G 1% /dev/shm
> tmpfs 5.0M 8.0K 5.0M 1% /run/lock
> tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
> /dev/nvme0n1p1 434G 34G 378G 9% /mnt/work
> /dev/nvme1n1p1 511M 4.7M 507M 1% /boot/efi
> /dev/sda1 2.7T 363G 2.2T 14% /mnt/PLEX
> tmpfs 1.6G 12K 1.6G 1% /run/user/1000
> tim1@vega:~$
I had Skip Commercials enabled, but have turned that off for now. Also Transcode While Recording was (and is) off. I hope the skip commercials feature doesn't rely on having idle time between recordings! BTW, my wksta has a Ryzen 5 1600 with 16G 3200 MHz DDR4 RAM -- I wouldn't call it a slow machine. Besides, cutting commercials from previous experience takes about 6-7 minutes, and this failure happened 20 mins after recording stopped. So I'm not clear that is the culprit.
I am saving my plex logs, in case they are needed.
Thanks for any help,
Tim
Ooops, my bad… turns out the low disk space was due to my use of /dev/shm (shared memory/ramdisk, ~ 8GB) for transcoding temp space. I found this in the logs:
Sep 26, 2018 20:21:51.223 [0x7fecdd3fd700] WARN - Low disk space: 0B source file, 7.77GB capacity, 684kB available on "/dev/shm/Transcode/Sessions/plex-transcode-b3f90548-df77-4a82-a633-fd58a65c6913"
I’ve changed the Transcoder temporary directory setting. I thought transcoding didn’t happen until after the .ts was complete/saved to disk, but that is obviously wrong.
Hi All,
Im experiencing the same recording errors for every show I attempt to record, regardless of channel.
my transcoder drive is NTFS, the drive with the temp transcoder has 400+GB free space.
ive tried all of the above suggestions with no success.
any assistance would be greatly appreciated
thanks
Thanks for your reply, would you mind looking at them for me? if so what ones should I send as I see their are quite a few different log names each day.
I have as a further test also removed the temp transcoder directory back to the default leaving the window blank without any success so have reassigned it back.
Please ensure Debug logging is enabled, Verbose is disabled, and Allow Plex Tokens in logs is also disabled. If you had to change any of these options please reboot the server or stop the Plex Media Server and restart it. When the next recording fails go to Settings/Server/Help and click the Download Logs link. Then drag/drop the zip file created into a new post here.
Thanks,
please see logs for today attached. the shows referenced are ‘NBC today’ and ‘the morning show’
I attempted NBC today numerous times as the same transcoder error occured, then swapped to the morning show and recived the same error. plex logs october 5th morning show and NBC today.zip (204.3 KB)
I have just shifted the G back one character and tried again, i also get the same error when this field is left as the blank default. prior to trying the next recording I saved pathway change, restarted the server, downloaded the guide updates and then tried to record Ellen with the fault occuring in a matter of seconds.
The same transcoder error occured trying to record ‘ellen’ as a test. plex logs ellen recording.zip (80.2 KB)
This error is not the same as your previous errors. The folder on your G drive was now created successfully for the transcoder to use. The transcoder is not seeing any video or audio in the stream coming from the tuner.
Oct 05, 2018 12:40:34.907 [12660] ERROR - DVR:Recorder: Part didn't have an audio or a video stream.
Oct 05, 2018 12:40:34.907 [12660] ERROR - DVR:Recorder: Error 12 (There was a transcoder error) starting the record, shutting things down.
Oct 05, 2018 12:40:34.910 [3504] DEBUG - Cleaning directory for session a6ec22aa-6573-4b3a-b2a5-4ac34a139689 (G:\Plex\Transcoder\Transcode\Sessions\plex-transcode-a6ec22aa-6573-4b3a-b2a5-4ac34a139689)
You can see from the last log line above that it is cleaning up the G drive directory created due to the failed recording attempt.
I would like to see if you can capture a short 30 second clip using the same channel. To do this you can use PowerShell and enter the following command:
Sorry I haven’t used power shell before, can you please tell me where I start the command line from as I keep getting errors? my power shell opens with the following PS C:\Users\me>
my tuners are onboard PCI tuners.
