In your first post, the screenshot shows /dev/shm being only 7.7 GB, guessing that’s a ramdisk?
Then you set Plex to use that directory for transcoding, that’s not a lot for a 4k transcode?
It depends, in your first post you seemed to want to be using that mnt/Enterprise_Storage drive for transcoding, if that is the case, you’d want to put that in the Plex settings for transcoder directory instead of dev/shm.
If you have a lot of ram, then yes you use fstab entry to increase dev/shm.
For example, my servers have 128 GB of memory so I provision 96 to dev/shm.
I’m pretty sure the size of the transcoded file ends up determining how much space is used in the transcoded directory. The motion picture 4k is a directors cut that’s pretty long. And if you transcode to 1080p versus 720 or 480 or something, I think you’d end up with a smaller file, so maybe that’s why it’s not come up before?
The thing is that other films I have which are of similar size (~83 Gigabytes) and 4K HDR have played fine in their original quality before with the same limitations on /dev/shm.
I can play e.g. “Oppenheimer” (2023) fine and that one is about 85 Gigabytes 4K HDR.
I don’t get why it’s acting up now. I rarely make big system config changes.
Usually when I open a movie for playback I pause it ASAP and then select the playback quality in the playback settings. The other films I’ve mentioned are also using the HEVC codec like ST:TMP.
Dec 29, 2023 18:39:37.257 [140170546592568] DEBUG - [Req#21c/Transcode] Using session GUID 44D48934-B754-4CDD-98AA-FBE843861EF4 for new transcode session.
Dec 29, 2023 18:39:37.257 [140170546592568] DEBUG - [Req#21c/Transcode] Using existing transcode session.
Dec 29, 2023 18:39:37.258 [140170628107064] DEBUG - Completed: [192.168.0.142:50249] 206 GET /video/:/transcode/universal/start.m3u8?audioBoost=100&autoAdjustQuality=0&directPlay=1&directStream=1&directStreamAudio=1&fastSeek=1&includeCodecs=1&location=lan&mediaBufferSize=40000&partIndex=0&path=%2Flibrary%2Fmetadata%2F3216&protocol=hls&session=44D48934-B754-4CDD-98AA-FBE843861EF4&subtitleSize=100&useDoviCodecs=1&videoResolution=4096x2160 (8 live) #21c TLS 17ms 463 bytes (range: bytes=0-)
Dec 29, 2023 18:39:37.329 [140170578180920] DEBUG - Request: [192.168.0.142:50250 (Subnet)] GET /video/:/transcode/universal/session/44D48934-B754-4CDD-98AA-FBE843861EF4/base/index.m3u8 (9 live) #22f TLS Signed-in (range: bytes=0-)
Dec 29, 2023 18:39:37.329 [140170578180920] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Starting a transcode session 44D48934-B754-4CDD-98AA-FBE843861EF4 at offset -1.0 (state=3)
Dec 29, 2023 18:39:37.329 [140170578180920] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] TPU: hardware transcoding: enabled, but no hardware decode accelerator found
Dec 29, 2023 18:39:37.330 [140170578180920] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] [Universal] Using local file path instead of URL: /mnt/Enterprise_Storage/Star_Trek_Films/Star Trek - The Motion Picture (1979) {edition-Director's Edition}/Star Trek - The Motion Picture (1979) {edition-Director's Edition}.mkv
Dec 29, 2023 18:39:37.330 [140170578180920] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] TPU: hardware transcoding: final decoder: , final encoder:
Dec 29, 2023 18:39:37.330 [140170578180920] WARN - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Low disk space: 8.5GB source file, 7.67GB capacity, 7.67GB available on "/dev/shm/Transcode/Sessions"
Dec 29, 2023 18:39:37.330 [140170578180920] WARN - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] TranscodeSession: inadequate disk space for transcode
Dec 29, 2023 18:39:37.330 [140170578180920] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Streaming Resource: Terminated session 0x7f7c03d34e48:62D77409-2F6F-416C-9FDF-A22F7FC67485 with reason Not enough disk space to convert this item.
Dec 29, 2023 18:39:37.331 [140170578180920] ERROR - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Failed to start session.
Dec 29, 2023 18:39:37.331 [140170544483128] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Killing job.
Dec 29, 2023 18:39:37.331 [140170544483128] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Job was already killed, not killing again.
Dec 29, 2023 18:39:37.331 [140170544483128] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Stopping transcode session 44D48934-B754-4CDD-98AA-FBE843861EF4
Dec 29, 2023 18:39:37.331 [140170510183224] DEBUG - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Cleaning directory for session 44D48934-B754-4CDD-98AA-FBE843861EF4 (/dev/shm/Transcode/Sessions/plex-transcode-44D48934-B754-4CDD-98AA-FBE843861EF4-672fbd1b-4763-4772-83e2-c7a1fb8111da)
Dec 29, 2023 18:39:37.330 [140170578180920] WARN - [Req#22f/Transcode/44D48934-B754-4CDD-98AA-FBE843861EF4] Low disk space: 8.5GB source file, 7.67GB capacity, 7.67GB available on “/dev/shm/Transcode/Sessions”
Can’t use /dev/shm as your transcoder temp with only 8GB.
HDDs are MORE than fast enough – or is this a purely SSD system?
( FYI – Samsung 970 Pro 1TB has a 1.2 PB TBW which would last quite a while )
My system drive as you can proably see is a 120 GB NVMe SSD which I would like to spare as much as possible from repetetive R/W activity. As said above Oppenheimer play right away and is way longer and larger in file size.
EDIT: And I don’t want to use any HDD for transcoding even if technically feasible.