Goobaroo

@JonathanM, your opinion here would be appreciated. Right before the latest shutdown I got the error "Array has 7 disks with read errors", all my disks. I was rebuilding a drive at the time, but other searches seem to point to a power issue.

Thanks @JonathanM, I did hit the base of the CPU with a laser thermometer, but you're right. Not a very accurate measurement. Usually on reboot the BIOS has the CPU in the 40-50 C range. It would help if Unraid could detect the thermal sensors like it did on my old setup, but loading the nct6775 driver doesn't return anything. Despite that being the recommendation from sensors-detect. But the uptimes are all over the place. Week, day, hours. I'm willing to swap the Power Supply to see if it fixes it.

I'm going to replace the power supply and see if that clears it finally. Heat seems fine now with the new case, there is a Nuctua NH-D9L on the CPU and it is cool to the touch. Power is the next most likely issue.

4 hours online, and reboot. So no dice. This is really making me regret this purchase, not Unraid, but moving to AMD

I'm going to throttle the scaling_governor to conservative. I only stayed up 7 hours last night and it was trying to recreate a drive, which is CPU intensive. That was after replacing the CPU cooler and putting it all in a much larger case with better air flow. cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Of course I say that and it rebooted again today. I'm hoping it is something with the flakey SAS cable at this point, and the replacement coming today will fix the stability.

I think I have it down two issues, heat and a bad SAS breakout cable. It ran for over a week with the case open and a small desk fan blowing into the case. I have a new case on order a Phanteks Enthoo 719 to get a bigger case with better airflow. The SAS cable because I've had the same drive location marked bad by Unraid twice now, once with the original drive and again with a brand new drive. It can't actually be the drive it has to be the cable. Biggest issue I have is that there are no OS level temperature sensors that work to confirm that things are overheating.

I recently replaced my motherboard and CPU from a i5 to a Ryzen 5700G and ROG Strix X570-E and it ran great for over a week. In the past few days I have not made it past 24 hours, sometimes as low as 30 minutes. What I've checked: Ran a memtest, and it passed with 4 pases Enabled syslog to disk, but there is no indication that I spot of why it is shutting down. Updated my BIOS, which reset all my settings, so I'm not 100% sure I've got everything the way it should be. Disabled c-state Enabled virtualiztion Plugged in the additional 4 pin CPU power. Running a 750W power supply. Temperature seems okay, but I don't know for sure since the sensors don't load. It finds Nuvoton NCT6798D, but modprobe doesn't load the driver Any help would be greatly appreciated. Prior to upgrading to Ryzen, the server was running great for over a year. lucifer-diagnostics-20210916-1327.zip Solved: TLDR: Heat and power. Replaced case with one with better airflow & replaced 750 W PSU with 1,000W one. Update: 16 days up, no issues. Definitely heat and power.

This isn't the most elegant solution but it works for me. I wanted to run a script when my VM started up to switch the scaling_governor from ondemand to performance when my gaming VM was running. I took @JonathanMs suggestion to use virsh list. Then setup a User Script to run every 5 minutes. If all the settings are already right, it does nothing, otherwise it will update the system. You can see the script here: https://github.com/Goobaroo/unraid-setCPUgovernor

I've got some sonoff devices that are configured on my old homebridge setup. The docker container doesn't seem to be able to resolve their .local names. Any ideas as to how to fix that? Edit: Looks like I need the avahi-daemon added to the docker container and started. Though I'm not sure how to do that exactly.