snowspeeder Posted August 21, 2022 Share Posted August 21, 2022 My Unraid box has been running well for the past few months, as of last night, the machine constantly panics after being on for a short while (15 minutes?). I tried several post repeating to the Docker direct IP being an issue, upgraded to 6.10.RC3 and switch to ipvlan with no avail. Removed all dockers except for Plex. I tried just disabling Docker, but I still get hardware errors. I ran a meatiest and everything passed. Any ideas? I have attached my syslog. syslog Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 Attach Diagnostics to your NEXT post in this thread Quote Link to comment
snowspeeder Posted August 21, 2022 Author Share Posted August 21, 2022 Diagnostics attached xnas-diagnostics-20220821-1209.zip Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 Uninstall NerdPack. It is deprecated and incompatible with 6.11 Reboot, start the array and post new diagnostics. Setup syslog server. Quote Link to comment
snowspeeder Posted August 21, 2022 Author Share Posted August 21, 2022 Nerdpack uninstalled. New Panic. New Syslog and Diagnostics attached. xnas-diagnostics-20220821-1325.zip syslog Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 How long did you let memtest run? Quote Link to comment
snowspeeder Posted August 21, 2022 Author Share Posted August 21, 2022 It ran overnight, but about 13 hours Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 Does it still happen if you disable dockers/VMs? Quote Link to comment
snowspeeder Posted August 21, 2022 Author Share Posted August 21, 2022 @trurl Yes, it does. It won't if I don't start the array, but even if I disable Docker, once I start the array it will barf after a few minutes. I started running the Memtest again, but this time with Hyperthreading enabled (option 2) and stated getting these errors after about 30 min, which I did not get with option one. So, I went to the BIOS and reset to defaults and am running again. Quote Link to comment
snowspeeder Posted August 21, 2022 Author Share Posted August 21, 2022 Yes, there are errors with he Bios settings defaulted. Is it typical for a long running machines memory to fail like this? Quote Link to comment
itimpi Posted August 21, 2022 Share Posted August 21, 2022 15 minutes ago, snowspeeder said: Yes, there are errors with he Bios settings defaulted. Is it typical for a long running machines memory to fail like this? You should never get errors on a memory test if you want the system to be stable. Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 You shouldn't attempt to run any computer if memory isn't perfect. Everything goes through RAM, the OS and other executable code, your data, everything. The CPU can't do anything with anything until it is loaded into RAM. Quote Link to comment
snowspeeder Posted August 24, 2022 Author Share Posted August 24, 2022 Just updating here. The issue seemed to be the motherboard had its TPU switch enabled. Once I switched it off, the system stabilized and has been running for 2 days without fault. Quote Link to comment
snowspeeder Posted October 10, 2022 Author Share Posted October 10, 2022 Following up here, the only thing I needed to do was switch off TPU, since then its been running steady for months. 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.