December 23, 20232 yr I've had my unraid setup running for quite some time now, but recently started experiencing some lockups where the GUI and shares are not accessible through the network. I have run parity check at least 5 times now and have not been able to complete because the system locks up every time before completion. Since I can't access through the network, I try to login directly on the server itself but it hangs after I input root as the user. I have tried replacing both RAM sticks since I had spares lying around, but the server is still crashing. Originally I was running 6.12.6 when I ran into this problem, but i downgraded back to 6.12.4 because I thought it was the problem, but I'm still experiencing the same issues. I noticed that very rarely, the server will actually recover itself and becomes accessible again. Most of the time when I press the power button to initiate shutdown, it will pass the graceful shutdown period and hang on the force shutdown, and I usually have to hard shutdown. As i was writing this post, I finally got some information on the error because previously, I couldn't find any sort of information related to the issue, but my server actually recovered itself just now, and the Fix Common Issues plugin threw me a useful error. I have 32GB of RAM total so some process must be memory leaking. One change I made recently was adding a VM for Home Assistant, but I have that capped at 4GB of RAM. Not sure if the attached diagnostics logs would be able to help identify which process is causing the problem. daniel-nas-diagnostics-20231223-0924.zip
December 23, 20232 yr Author Was looking up some things on google about Home Assistant memory leaks and one post came up about frigate and using vaapi, which I switched to recently because people said it was recommended for encoding. Will try to change it back and see if it stops the hanging.
December 23, 20232 yr Author Solution I caught frigate in the act with docker stats...now to figure out how to fix it CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 5f97175ae55c frigate 673.73% 20.16GiB / 31.11GiB 64.80% 980MB / 58.8MB 149MB / 602kB 1238
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.