TheEyeTGuy

Thanks for your response. Sorry if I offended you with some of my wording, did not mean any offense. Docker can't control memory either now though, which regardless of swap, I think is something that could be considered a bug. Cgroup stuff is also above my head. I appreciate your quick responses. On an unrelated note, is your source code published anywhere? I'd just like to poke around, for my own curiosity. Thanks!

If it does work, its not working for my docker containers, I can also confirm the docker container is not respecting its memory limit configuration (limited to 8 gigs, but uses more than that). Bug in 6.12.x?

Has anyone had success with swap working in 6.12? I've got a docker container that I use it for and I get the following when updating the container: WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.

*Bump*

Hello, I've very recently started getting out-of-memory errors on my Unraid server. And this morning I woke up to my HomeAssistant VM showing as 'Started' but inaccessible and throwing errors in VNC console (screenshot attached). Recent changes: Upgraded from 16GB RAM to 48GB Added Frigate as Docker Added a Coral Mini PCIe card. Added 2 new 8TB HDDs My assumption, is that Frigate is trying to use up all the RAM. I do have a Dell Optiplex 7010 with a 4th gen? i5 and 24GB of RAM that is currently unused. Would it be better to offload frigate to that? My diagnostics are attached. Thanks in advance! dxsunraid-diagnostics-20230531-0904.zip

I'm getting the same error. Just updated from 6.9.3 to 6.11.5 Everything else seems to be working ok.

I agree with the 3 of the above opinions: Search should be on the right hand side, Close should also be on the right and side of pop-ups Pop-ups should not cover the banner.

Hi @Trurl My bios did not have the CState control or the Power Supply Idle Control. I ended up downgrading it to 5.80 and it had the options for 'Global Cstate Control' , which In set to 'Disabled'. I also found an option labeled 'PSI' and no clear indication of what this was. I assumed this was the Power Supply Idle Control but instead of 'Typical' I only had 'Auto' and 'Disabled', so I went ahead and disabled this. Additionally, as I previously stated, I am not overclocking the RAM, not even using an XMP profile. Server is back on and running again, so we'll see in a few hours.

Hello, My unraid system seems to be crashing after roughly 12-20 hours every day. The system completely hard locks and needs to be hard powered off by the power switch, and switched back on to become responsive again. After 2 days of this same thing after approx the same amount of time passing, I took the time to setup syslog and had it log to my desktop. I can generate the diagnostics if needed, but not sure how helpful that will be since the system has to be restarted to be accessed at all. Its completely unreachable via network or even when I attach a keyboard and display. Specs: CPU: Ryzen 7 1700X - Stock clocks RAM: 16GB - Stock clocks Motherboard: ASRock AB350 Pro 4 BIOS: P6.40 (Latest) Unraid Version: 6.8.3 Relevant portion of syslog attached. Unraid_Syslog.txt