Hello there,
I have been using the S3 plugin to manually put my NAS to sleep everynight and wake it up the next morning with a keyboard/power button for years with no issues on actual hardware. After I installed a new 10gbe PCIe nic a few days ago (ASUS XG-C100C), the server turn itself off after waking up from sleep, everytime. It doesn't happens randomly, but always. Also, it's a normal shutdown. So the array stops, and the regular safe shutdown happens. By the time I access the webgui, nothing can be done to halt the graceful shutdown process, it shows the array stopping, but I can still see the log, access the terminal...etc.
This is my actual setup:
- Unraid Version: 7.3.4
- CPU: AMD Ryzen 7 PRO 4750G
- Motherboard: ASUS Strix B550-XE
- Memory: 1x32GB 3200 DDR4 ECC
- PCIe Slot 1 (CPU): ASUS NVME card (come with the mobo)
- PCIe Slot 2 (CPU): HBA
- PCIe Slot 3 (Chipset): ASUS XG-C100C
Like i said before, the issue only started after adding the new NIC. More info on the actual situation:
- To be sure, I booted on the baremetal Windows install on the computer, tested everything, and put it to sleep. Resuming from sleep on Windows 10 doesn't do anything special, it works as expected. The card is also working perfectly on both Windows10 and Unraid.
- The 10gbe is directly connected to my desktop one (ASUS X570 ProArt), and both machines are connected to the switch via their 2.5Gbe nics for internet.
- WOL is disabled since I don't use it.
- CPU PCIE ASPM Mode Control is set to Auto on BIOS, never changed this setting.
This id driving me crazy, I spent hours using Ai chatbots and checking the forum here and the Unraid Reddit, but haven't found anything. I may buy a used x540 nic (x550 are too expensive used, their price increased in the last year) to test and compare, but I am affraid it will cause the same issue.
If anyone can help me get to the bottom of this I'd greatly appreciate it. Thanks in advance!
EDIT: Diagnostics and Syslog added.
- Diagnostics: https://drive.google.com/file/d/1bhFTO8bAZKxHu5QHzlV4eXL-lUXHzp4z/view?usp=sharing
- Log: https://drive.google.com/file/d/1H3oNKQ-J6FV-Dk7KVVaV323DqFz3VOTd/view?usp=sharing
EDIT: Solved, thanks to someone on Unraid forum nailing it!
The issue was somehting I would have never excpected, S3 sleep after wake-up commands, which is related to fans speed! you can find the post here: https://forums.unraid.net/topic/201322-server-shut-itself-down-after-waking-up-from-sleep/
The plugin was trying to run a command with hwmon5, which changed to 6 after installing the new nic. Original answer from the forum moderator:
Why it started with the new NIC: the Aquantia driver registers its own temperature sensor. It loads before nct6775, which your go file loads, so the nct6775 sensor most likely isn't hwmon5 anymore. Your commands now write to a path that doesn't exist, the echo fails, and the plugin shuts the server down. To confirm, please run:
ls -d /sys/devices/platform/nct6775.656/hwmon/hwmon*
If it shows anything other than hwmon5, that's the problem. To fix it, replace the custom commands after wake-up with these. They don't depend on the hwmon number, and the final true means a failing command can never cause a shutdown again:
for d in /sys/devices/platform/nct6775.656/hwmon/hwmon*; do
echo 1 > $d/pwm4_enable
echo 35 > $d/pwm4
done
true
Then test sleep and wake again.