jpslv

Well, I removed all my docker containers and reinstalled some of them while also setting up a new VM (2 CPU and 4 GB of RAM) with Home Assistant OS using my previous vDisk. So far, so good. I didn't do any memory test but it was probably some docker containers running tasks and maybe maxing my server CPU and memory. Not only did my Home Assistant OS VM used to crash but sometimes I couldn't also access unRAID's GUI. I will report back if anything happens.

Hello. I'm a bit of an amateur, so apologies if I'm not clear enough! I'm running Home Assistant OS through a VM on unRAID. I've been doing this for almost 4 years. Home Assistant has been recently crashing almost every night. I've set 2 logical CPU to the VM and increased memory to 4 GB (from 2 GB). The problem (crashing) still persists. On the unRAID GUI the memory is always maxed: However, on Home Assistant GUI memory use seems fine: Overall, my unRAID server doesn't require much power: I don't really know what to do. Maybe the diagnostics file could be useful? I'm running unRAID v7.0.0-rc.2. I'd appreciate help from the experts of this community! Thank you for your time! core-diagnostics-20250104-1300.zip

Same with me.

Would love to use my YubiKey on unRAID's GUI.

Thanks for your comment. Had no idea about this. Found more information on Samsung's forum: https://us.community.samsung.com/t5/Monitors-and-Memory/SSD-980-heat-spikes-to-84-C-183-F/m-p/2161229.

Hey guys. Sometimes I get an unRAID warning about one of my two cache ssds reaching high temperatures (84ºC) [see first two images]. However, on the disk attributes page, temperature is normal (35ºC) [see image 3]. Scrutiny also doesn't show any high temperature for the disk [see image 4]. Is it "bad temperature reporting" by unRAID? Is my disk really reaching that temperature of 84ºC? And why?! Both SSDs are the same exact model (Samsung 980 M2 SSD), except the size (one is 250gb and the other one is 500gb). Only the 250gb SSD reaches >80ºC temperatures. I've attached a report. Thank you guys for your inputs and thoughts. image 1: image 2: image 3: image 4: core-diagnostics-20220813-2226.zip

Thank you. I'll post on git and report back here if there is a solution. https://github.com/jellyfin/jellyfin/issues/8030

Yes, 10.8.1 has been released. They fixed the problem but my unRAID server doesn't seem to have the OpenCL drivers. How can I install them?

I've installed both containers (yours and the official one) and I repeat every step on both of them. I can't play these DoVi profile 5 files and according to the logs, the problem is OpenCL related. I think I have all AMD drivers configured properly (for example, in Plex, I can hardware transcode with no problem). Thank you for replying!

Hello @ich777. First of all, thank you for all the hard work! I'm trying to play some DoVi (profile 5) content with jellyfin. The 10.8.1 version supposedly fixed DoVi to SDR tone-mapping. However, I can't get it working. A jellyfin dev wrote that "AMD OpenCL runtime must be installed before using DV tonemapping". Can you try to help me? Error message: "Playback Error. This client isn't compatible with the media and the server isn't sending a compatible media format." ffmpeg log: "[AVHWDeviceContext @ 0x5623ffee0340] Failed to get number of OpenCL platforms: -1001. Device creation failed: -19. Failed to set value 'opencl=ocl:.0,device_vendor=Advanced Micro Devices' for option 'init_hw_device': No such device Error parsing global options: No such device."

Thank you so much!

Thank you very much for this guide!