+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Server crash when transcoding high resolution (/t-solved-server-crash-when-transcoding-high-resolution)
Server crash when transcoding high resolution - MaSe214 - 2025-02-05
Hi,
Jellyfin Version 10.10.5, earliest version I tried was 10.10.3
I have a new mini home server, one of those amazon mini firewall computers. I bought it barebone with an Intel N100 and put 16GB RAM and a 1TB SSD (Kingston NV3) into it. I run Proxmox on it and Jellyfin as an priviliged container on it that I set up according to the documentation. The container has 16GB storage, 4GB RAM, access to all 4 cores, the GPU is passed through. After setting up the container I installed Jellyfin using the generic linux auto repository method and set everything up within Jellyfin. Transcoding works great in terms of hardware utilisation, it 4K causes little CPU usage, RAM usage stays low. I also set up transcoding following strictly the documentation.
After 2 days I finally opened a media file on my TV (4K HDR, Jellyfin Android TV App, Nvidia Shield) that needed transcoding and the video abruptly stopped. I noticed that nothing from my server was responsive. Neither Jellyfin, nor Home Assistant, or other containers or even Proxmox. I had to restart the serer using the power button. I tried the same file again, and again a crash occured, at a different time stamp that time. In total, I now had more than 20 crashes with several different media files, the crash usually occuring between 10-120 seconds after playback started. When no transcoding is neecessary, there is no crash. It just works. I tried streaming to my PC (which always required transcoding, Firefox, Windows 11, WQHD) and often the server did not crash, once it did but much later compared to the TV. The source files are often 1080p without HDR.
I checked the Jellyfin logs but whenever the crash happens it will only log many of those:
Code:
����������������������So I also checked Proxmox: The container summary shows no problem with CPU, RAM, storage (see screenshots that I made when a crash occured). There is also no temp problem. All temps stay below 50°C (ssd, cpu).
Even the journalctl does not show any error! There is only a Reboot line but no error before. The only thing I noticed is high IO Wait (>30%) when transcoding to my TV. Transcoding to my Browser is much more chill, going to 10%, then decreasing again.
I have the feeling that the issue might be hardware related. But I have no idea how I could really check that despite trying a different ssd/ram that I do not have and before I try that, maybe someone else got an idea. But would proxmox crash as well if it was not hardware related? I think a general problem might also be that I gave Jellyfin only 16 Gigs storage and transcoding cache is on that disk. But I don't see the storage consumption rise in Proxmox when I run a stream.
See attached also my transcoding config as well as a part of the debug log when the crash occured.
Thanks for any help!
PS: Also attached a screen to the server. At crash the screen simply turns black...
RE: Server crash when transcoding high resolution - TheDreadPirate - 2025-02-05
Is the container running out of disk space? Transcodes are written to disk and you mentioned that the container has 16GB of storage.
RE: Server crash when transcoding high resolution - MaSe214 - 2025-02-15
Did lots of testing, including giving it more disk storage, including several reinstalls, using other drivers, but nothing helped. Then I suddenly could not even use a screen anymore that was attached to the device as the screen would turn black after around 10 seconds after bootup. I switched the RAM and now it works fine, so looks like I got a faulty unit. I just wonder why there are no system errors at all, at least on Windows I can remember getting a bluescreen back in the time indicating problems with the RAM.
RE: Server crash when transcoding high resolution - rendous - 2025-03-16
I'm also getting this same behavior.
Was on 10.10.5: twice my friend tried streaming a 4K file via the browser that triggered transcoding, and my proxmox server crashed / shutoff immediately after.
Haven't been able to see anything in logs that would indicate a crash/error of some sort.
RE: Server crash when transcoding high resolution - TheDreadPirate - 2025-03-16
(2025-03-16, 06:12 AM)rendous Wrote: I'm also getting this same behavior.
Was on 10.10.5: twice my friend tried streaming a 4K file via the browser that triggered transcoding, and my proxmox server crashed / shutoff immediately after.
Haven't been able to see anything in logs that would indicate a crash/error of some sort.
How much free space do you have on the disk that Jellyfin runs off of? Transcodes/remuxes are written to disk and transcodes of 4K files can consume as much, and often more, than the original file. So, for example, an 80GB 4K HDR file will consume 100+GB of disk space for the transcode.
You can try enabling "Delete segments" and "Throttle transcodes" in Dashboard > Playback > Transcoding to reduce the disk space usage from transcodes/remuxes. Assuming that is the problem you are having.
RE: Server crash when transcoding high resolution - rendous - 2025-05-09
Jellyfin has 160gb, but I think the file was 100gb, so its entirely plausible that something like that was happening.
There's also the caveat that the server is underpowered to transcode 4K - CPU is an i7-7700, but I was just curious that the entire node / server shutoff instead of just Jellyfin crashing.