homiek33

I reverted to my old mobo cpu ram (3rd gen intel) and PSU and haven't had an unclean shutdown. I am pretty sure it was the new mobo but can't be 100% sure. In any case, this was such a big time suck and I appreciate the help.

Safe mode (with dockers enabled) hasn't worked. I will change my mobo CPU ram and chalk it up to hardware (likely mobo) issue. Thanks all for the input.

Removing GPU did not work. Unclean shutdown same day. As a final ditch effort, will run in safe mode.

Okay will try and revert. Thanks for the suggestion as always.

sigh. Just had another unclean shutdown randomly (a day after upgrading PSU). I am posting my diagnostics and logs from syslog server to check one last time if there are any other leads I should follow to further resolve. If still likely a hardware issue, then I will just have to move on and get a new mobo cpu ram setup. Can't spend more time diagnosing this further unfortunately - have a whole village depending on this server. Like I said, I had run memtest for 17 passes (more than 24 hrs) and Cinebench stress test (granted it was only 10sh minutes) with no issues and have now upgraded PSU to no avail. Many thanks syslog2.txt beast-diagnostics-20250407-0008.zip

@JorgeB Could the hardware problem be the flash drive running the OS?

okay. step 1 will remove my GPU and see if it stops. After that, will swap PSU. if that doesn't resolve, I am nuking the whole thing and getting some new hardware Thanks again for your your help.

I have now run a CPU test on cinebench, kept an eye on temp (sub 53c CPU) and ran memtest for 17 passes with no errors. Motherboard seems fine, no error lights or visible damage anywhere. Is there anything I can do to diagnose this further ? I’m not convinced power supply is an issue given system ran under stress with no issues. any tips would be helpful. Happy to repost for logs for this latest unclean shutdown if helpful. thanks!

Just happened again. Sigh... My PSU may not be beefy enough? (running i5-9600K using a 450w PSU, 4 HDDs, one NVME a few fans and GTX1660TI Super which is always idle). Based on all calculations I need close to 420W or thereabouts so I was confident I would be okay. Maybe Will update the PSU and see what happens.

I have updated to 7.0.1, disabled NUT (checking the logs, there was some incompatibility issue with it) and replaced my UPS. So far, it is been almost two days without issue. Will report if any issues but so far, looks to be stable. thanks

Yes indeed the uptime restarts after such unclean shutdowns. My UPS needed a battery change so just switched to a new one as per your response to my previous thread (although not sure that alone would cause this problem). Is there best practice on what/how to test the relevant hardware?

Hi all I am on 7.0.0 with critical updates patch installed. I have moved to new hardware (new Mobo, ram and CPU) a few weeks ago. I have been suffering form almost daily random unclean shutdowns with parity checks initiated after. Only started happening recently, after updating to 7.0.0. I don't think the PC actually shuts down. Just a notification that states unclean shutdown and then I notice a parity check running. Any help would be much appreciated. thank you beast-syslog-20250310-1414.zipbeast-diagnostics-20250310-1714.zip

Okay. Will do that and report. Thanks

Hi all, My Unraid 7.0.0 sometimes drops out of my network. Can't ping, cant SSH. I have had this happen in the past and switched to ipvlan under docker settings which resolved the issue at that time - I am still on ipvlan. I hate this as I am not always around the server to restart it and I am forced to do an unclean shutdown. I have an intel NIC on ipvlan (docker settings) had "Host access to custom networks" set to enabled (as per SapceInvader One instructions for unifi controller but then scrapped the whole idea and reverted back to disabled after today's issue of Unraid not being reachable today. Not sure if that is related to my issue) My UPS is flashing to replace battery (the logs appear to fill up with its warnings, not sure if that is relevant to Unraid being unreachable) If it matters, I have recently (few weeks ago) upgraded my hardware (mobo, CPU and ram) to ASRock Z390 Phantom Gaming 4 (intel NIC) on i5-9600k (did not play around with OC) with 4x 8g DDR4 ram. Uploaded diagnostics and syslog server logs for help. Many thanks in advance for your time. syslog-192.168.1.110.log beast-diagnostics-20250302-2106.zip

what I am about to say doesn't resolve the above stated issue but is an alternative to avoid the problem altogether. I found myself in the same situation where my nzbget docker was broken and understand that the previous maintainer for the nzbget docker has stopped maintaining it. After much fiddling and brute forcing, I just ended up going to the nzbget website and looked under the installation/docker tab then replaced the repository under the nzbget settings on unraid to the below and now no more issues with unpacking. Will do some more tests but looks like this resolved. I only got into this mess because the update link for nzbget on my docker page was broken (due to the previous maintainer stopping to maintain). My strong suggestion to you is, if nzbget is working without issue, don't play around with it just because the version link isn't available on the docker page. ghcr.io/nzbgetcom/nzbget:latest