On 12/8/2022 at 11:38 AM, SonOfTux said:

 

Hi,

It seems to be being caused by the fan speed script not being able to cope with PWM outputs that don't have an associated enable output, hence the

file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm2_enable) failed to open stream: No such file or directory

This issue with the nct6687 driver has been an ongoing issue for at least the last 2 years if you look back through these messages and is still waiting to be addressed.

So the only solution is get a different motherboard or anything else i can do?  It's been ok temp wise because i am not pushing anything and the CPU is about 42 idle (5950X) 

Anyone has got an idea why there are not temp sensores listed? They disapeared once I added the MB temp sensor. Before that, the CPU sensor was just running fine.

 

Same for the Fan Auto Control. I have two PWM Fans plugged into the mainboard directly.

Edited December 19, 20223 yr by pille

Is there a way to call for the sleep function not via the gui, but with the command line?

On 12/24/2022 at 6:07 PM, lightshark85 said:

Is there a way to call for the sleep function not via the gui, but with the command line?

 

I was searching for this as well. I checked the source code a little bit on my own and it seems like you can use it via bash manually like this..

 

/usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep -h

 

But still not tested, only figured out a minute ago.. Let us know how you use it and if it has worked out, please

Edited December 29, 20223 yr by Skylinar

28 minutes ago, Skylinar said:

 

I was searching for this as well. I checked the source code a little bit on my own and it seems like you can use it via bash manually like this..

 

/usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep -V

 

But still not tested, only figured out a minute ago.. Let us know how you use it and if it has worked out, please

Thanks, this totally works!

If anyone wants to copy my setup:

I use Homeassistant on a Raspy with a wake on lan switch (see documentation for homeassistant wake on lan https://www.home-assistant.io/integrations/wake_on_lan/)

I use the turn_off feature of wake on lan to call the script.

 

Here is my script to sleep the server via ssh:

 

"ssh -i /config/ssh_keys/id_YOUR_PRIVTE_KEYFILE -o 'StrictHostKeyChecking=no' [email protected] /usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep -S"

 

bare in mind that you have to follow another guide to configure the ssh_key first, or HA can't connect to the server via ssh

Anyone get anywhere with the auto fan & Nct6687 driver bug?

 

The driver works for showing fan speed but if I use the autofan plugin it sets the fans to full speed or 0%.

 

For the moment just using bios settings based on CPU usage.

 

I would like to fans to turn off if selected drives (array which in future will be a ZFS cache pool) turn off for noise purposes.

 

NVMe ssds do not matter so much as on motherboard and both have heatsinks & CPU fan is very close.

Edited January 11, 20233 yr by dopeytree

Hello everyone,

 

I'm an Unraid beginner and for now I only wanted to know if it is possibile to exewcute an automatic shutdown depending on certain IPs active on the network. Ok, found the dynamix s3 sleep plugin which after being installed is working fine - till the next reboot, then it is stopped and I have to start it again. I cannot find any errors in the syslog and cannot understand why the plugin is not starting automatically after reboot.

My setup: some old pc tower fot testing, Unraid is running in trial mode, the is only the USB key used, no array or cache disks active.

 

Thank you for your help!

On 1/13/2023 at 12:17 PM, undee said:

Unraid is running in trial mode, the is only the USB key used, no array or cache disks active.

Most services on unraid only run after starting the array.

S3 sleep - can anyone help with a script to pause dockers? It's preventing the machine from sleeping sometimes.

 

Hello everybody, i have a problem with autofan. It recognizes my sensors and makes the fans go (they are pwm) but I haven't seen the % of use for a few days. I also don't know how to set the second fan which is the CPU one differently to follow the temperatures of the CPU and not the disks

 

 

 

15 hours ago, Lordbye said:

I also don't know how to set the second fan which is the CPU one differently to follow the temperatures of the CPU and not the disks

not possible (by plugin design) and also not recommended by the author, this is only meant to be used for hdd fans.

8 hours ago, alturismo said:

not possible (by plugin design) and also not recommended by the author, this is only meant to be used for hdd fans.

Cpu fan speed is set in the bios

thanks all.

I have already set bios config for cpufan. ok i'll use it only for hdd

 

 

On 12/3/2022 at 9:18 PM, Bluppylein said:

i have delete all information in sensors and it work

Been struggling with making sensors work after setting array fan speed and Reinstalling/loading/unloading did not do anything.. and from the gui i cant delete something which is not there ^^ so...from where did you delete all information?

 

edit: I`m still looking for the above answer for the future endeavors; however, somehow today after i rebooted the server Ive noticed that it automatically picked the array fan speed.. so i went to check and the error disappeared and somehow all works fine (had to attach the right temp sensors for cpu +mdb tho)   😂

Edited February 5, 20233 yr by obi-WAN-kenobi
added footnote

Recently upgraded my motherboard and now I get this when I try and use the Fan Control software...

 

 

 

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6687.2592/hwmon/hwmon2/fan1_input

 

 

After installing the ict6687 plugin I do have all the sensors and I can manually set the fan speed via the command line.

 

 

nct6687-isa-0a20
Adapter: ISA adapter
+12V:         12.02 V  (min = +12.00 V, max = +12.05 V)
+5V:           5.04 V  (min =  +5.03 V, max =  +5.05 V)
+3.3V:         3.35 V  (min =  +3.34 V, max =  +3.35 V)
CPU Soc:     616.00 mV (min =  +0.16 V, max =  +1.20 V)
CPU Vcore:   662.00 mV (min =  +0.66 V, max =  +0.66 V)
CPU 1P8:       0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU VDDP:      0.00 V  (min =  +0.00 V, max =  +0.00 V)
DRAM:          1.22 V  (min =  +0.23 V, max =  +2.40 V)
Chipset:     946.00 mV (min =  +0.92 V, max =  +0.95 V)
CPU SA:      898.00 mV (min =  +0.90 V, max =  +0.90 V)
Voltage #2:    1.54 V  (min =  +1.53 V, max =  +1.54 V)
AVCC3:         3.32 V  (min =  +3.32 V, max =  +3.34 V)
AVSB:          3.34 V  (min =  +3.34 V, max =  +3.36 V)
VBat:          1.06 V  (min =  +1.06 V, max =  +1.06 V)
Array Fan:    630 RPM  (min =  596 RPM, max = 3174 RPM)
Array Fan:   1532 RPM  (min =  580 RPM, max = 1540 RPM)
Array Fan:   1235 RPM  (min =    0 RPM, max = 1301 RPM)
CPU:          +30.5°C  (low  = +27.5°C, high = +87.0°C)
MB Temp:      +33.5°C  (low  = +33.0°C, high = +39.5°C)
VRM MOS:      +32.0°C  (low  = +32.0°C, high = +45.5°C)
PCH:          +46.0°C  (low  = +46.0°C, high = +53.0°C)
CPU Socket:   +31.0°C  (low  = +30.5°C, high = +56.0°C)
PCIe x1:      +29.0°C  (low  = +29.0°C, high = +30.5°C)
M2_1:         +32.0°C  (low  = +31.5°C, high = +32.0°C)

 

Searching this thread brings up the error but not the solution unless I'm being silly?

 

There is no pwm_enable, so maybe that is why it is falling over?

 

echo 255 > pwm1 for example, works.

 

 

-r--r--r-- 1 root root 4096 Feb  2 22:08 fan1_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan1_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan1_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan1_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan2_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan2_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan2_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan2_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan3_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan3_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan3_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan3_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan4_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan4_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan4_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan4_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan5_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan5_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan5_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan5_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan6_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan6_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan6_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan6_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan7_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan7_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan7_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan7_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan8_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan8_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan8_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan8_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 name
drwxr-xr-x 2 root root    0 Feb  2 22:22 power/
-rw-r--r-- 1 root root 4096 Feb  5 20:19 pwm1
-rw-r--r-- 1 root root 4096 Feb  5 20:14 pwm2
-rw-r--r-- 1 root root 4096 Feb  5 20:14 pwm3
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm4
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm5
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm6
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm7
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm8
lrwxrwxrwx 1 root root    0 Feb  2 22:08 subsystem -> ../../../../../class/hwmon/
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp2_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 temp2_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp2_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp2_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_min
-rw-r--r-- 1 root root 4096 Feb  2 22:08 uevent

 

Edited February 5, 20233 yr by Interstellar

After the update to v 2023.02.05a, i see this:

 

 

...not normal (i think).

 

Feb  6 11:18:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:19:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:20:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:21:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:22:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:23:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:24:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:25:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:26:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:27:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:28:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:29:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:30:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:31:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:32:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:33:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:34:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:35:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:36:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:37:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

 

The Stats-Plugin was working before this update...

 

Edited February 6, 20233 yr by Zonediver

2 hours ago, Zonediver said:

After the update to v 2023.02.05a, i see this:

 

The Stats-Plugin was working before this update...

 

 

Same here, running Unraid 6.11.5 on an QNAP TS-453Be, but I don't get any Syslog Errors after a reboot. System Stats are just blank. 

The latest version of System Stats uses the sa package which is provided with Unraid.

When the upgrade is performed the "old" sa package is removed and it requires a system reboot to restore it.

 

8 minutes ago, bonienl said:

The latest version of System Stats uses the sa package which is provided with Unraid.

When the upgrade is performed the "old" sa package is removed and it requires a system reboot to restore it.

 

 

Thanks for your help - working 👍

6 hours ago, bonienl said:

The latest version of System Stats uses the sa package which is provided with Unraid.

When the upgrade is performed the "old" sa package is removed and it requires a system reboot to restore it.

 

Unfortunately it doesn’t work for me like before: 

I updated the package and rebooted the system. No System Stats were available. 
So i uninstalled an reinstalled the plugin (with purging the old plugin files via „Apps“ -> „Previously installed“). After that i rebooted the system again to be safe. 

The System Stats are now working for the Real-Time view, but not for the static views.  

12 hours ago, superschlundi said:

The System Stats are now working for the Real-Time view, but not for the static views.  

 

It will take some time to fill the database.

 

Is there any plan to allow the fans detected by Auto Fan to be nameable - it would be great to be able to add a name so I can remember what is plugged in where, great to for an easy look when they speed up

Anyone else got 'pending' update for S3 sleep plugin? Its been like that for a few days also the forum link doesn't work anymore..?

On 2/6/2023 at 3:05 PM, superschlundi said:

Unfortunately it doesn’t work for me like before: 

I updated the package and rebooted the system. No System Stats were available. 
So i uninstalled an reinstalled the plugin (with purging the old plugin files via „Apps“ -> „Previously installed“). After that i rebooted the system again to be safe. 

The System Stats are now working for the Real-Time view, but not for the static views.  

Same issue here as well - reinstalled plugin and rebooted but historical views not working.

On 2/7/2023 at 9:53 AM, bonienl said:

 

It will take some time to fill the database.

 

After several days still no data and inconsistent representation of the graphs.