seifer Posted February 22 Share Posted February 22 Hi, I would like some help on my setup, it's been some time now that my system freezes randomly, and I cannot figure out why. I just cannot access Unraid dashboard, I have to perform an unclean reboot using power button to have access back on. I think it may occur while a parity check is running but I do not know the way to confirm it. Could you please help me to discover what is wrong? And if it is parity check related, how should I get rid of that kind of problems? I join the diagnostics files if needed. The system runs since february 2022, no problems so far until I added the parity disk. The setup informations in my sign are up to date. seifernas-diagnostics-20240222-1756.zip Quote Link to comment
JorgeB Posted February 22 Share Posted February 22 Enable the syslog server and post that after a crash. Quote Link to comment
itimpi Posted February 22 Share Posted February 22 It is possible you are running into a power issue as the parity check is one time the PSU is likely to be under maximum load. Quote Link to comment
seifer Posted February 22 Author Share Posted February 22 1 hour ago, JorgeB said: Enable the syslog server and post that after a crash. I have already enabled the syslog server, I took a look at it but I did not find anything on there. I joined the file if you want to have a look. 35 minutes ago, itimpi said: It is possible you are running into a power issue as the parity check is one time the PSU is likely to be under maximum load. Is that possible? I have a 450W PSU, a T1000 8Gb which consume 40w max and a i5 which consume 65W max. syslog-192.168.1.106.log Quote Link to comment
JorgeB Posted February 22 Share Posted February 22 Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. Quote Link to comment
seifer Posted February 22 Author Share Posted February 22 I have for now disabled the parity check, I will check if there is any improvement without this enabled. And if there is no freezes, I would have found my problem. Is that a possibility? I have read that it could come from the SATA plugs on the motherboard, wouldn't be pointed out by the logs? I will try your solution as well and I will come back to you if anything happens or not. Thanks for the help! Quote Link to comment
JorgeB Posted February 22 Share Posted February 22 If the freezes are mostly during a parity check it suggest some hardware issue, like a bad power supply. Quote Link to comment
seifer Posted February 22 Author Share Posted February 22 A bad or insufficient? Quote Link to comment
itimpi Posted February 22 Share Posted February 22 3 hours ago, seifer said: A bad or insufficient? Either. Quote Link to comment
seifer Posted March 8 Author Share Posted March 8 (edited) Hi, I am still waiting for an issue, I had one some days ago and I realised that the diagnostics file does not include the defaults after a reboot, so I have enabled SSH to be able to save the diagnostics file before rebooting with the "diagnostics" command as my user interface freezes. Will SSH eventually give me the possibility to perform a clean reboot with the "reboot" command in terminal? Edited March 8 by seifer Quote Link to comment
itimpi Posted March 8 Share Posted March 8 1 minute ago, seifer said: Will SSH eventually give me the possibility to perform a clean reboot with the "reboot" command in terminal? Not if the system really freezes/crashes. It has to be at least working at a basic level for ssh to continue working. Quote Link to comment
seifer Posted March 17 Author Share Posted March 17 (edited) Hi, I recently got an error in Fix Common Problems plugin : As my server do not stop working, but I ask anyway, could this lead to a freeze of Unraid? As the processes were killed off, I do not think it could be the case, but who knows... I can't figure out why I did not get a freeze already since I asked for help, maybe a container was faulty and an upgrade fixed the problem... I join a new diagnostics file. seifernas-diagnostics-20240317-1231.zip Edited March 17 by seifer Quote Link to comment
JorgeB Posted March 17 Share Posted March 17 Killed process 24507 (ffmpeg) ffmpeg was killed twice, meaning it was using a lot of RAM, go to container that is using this and limit its RAM usage. Quote Link to comment
seifer Posted March 17 Author Share Posted March 17 Thanks, I just have added "--memory=4G" to frigate extra parameters, is that enough or should I increase amount of RAM? Quote Link to comment
JorgeB Posted March 17 Share Posted March 17 6 hours ago, seifer said: is that enough or should I increase amount of RAM? I don't know, retest, you can also ask in the container support thread. Quote Link to comment
Recommended Posts
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.