I have the same problem as @Somberland.
I have not ignored my cache drive but when the disks in the array go into spindown, the fan speed goes to 0.
Is it possible to set a minimum speed even when the disks are in spindown?

22 minutes ago, Patty92 said:

Is it possible to set a minimum speed even when the disks are in spindown?

usually the min pwm value should be hold, may try raising it higher and test how low you can go in terms it works then.

7 hours ago, alturismo said:

usually the min pwm value should be hold, may try raising it higher and test how low you can go in terms it works then.

thanks that helped for me, Min PWM of 70 is around 15% (400rpm)

System Statistics seems to be broken with the v7.0.0 beta.  I just get an empty page when I navigate to the 'Stats' tab.  This is on a system with only a ZFS Pool where the UnRaid Array has been removed.  Possibly the plugin currently needs an UnRaid Array to operate?

 

Not sure if this can be done, but is there a way to add support for dGPU fan control?

 

I have an Intel Arc a310 and while idle, the GPU fan spins up and down every few seconds and its quite annoying!

16 minutes ago, ranova said:

Not sure if this can be done, but is there a way to add support for dGPU fan control?

 

short, nope .... GPU fans are by default controlled by their BIOS, software could only control with access to ... which is not given like this on this linux platform, if there would be a cli tool from intel to control the fan, then you could write something together ...

 

sample now with intel tools https://www.oldcai.com/ai/intel-gpu-tools/

 

may write to intel to give some tool to read more, control, ...

Feature request for Fan Auto Control:

Please implement a setting to always autostart. My PMW controller is number 4 in the list, and Fan Auto Control did not start on reboot. Apparently, this is because it only tests the first pmw?

 

Quote

The plugin has an issue where it will only check to see if the first PWM controller is enabled before auto-starting.

So if it’s not enabled then it won’t auto-start, even if others are enabled, which I’m guessing is the issue you’re running into.

The solution I use is to add this to the go file, which will start the plugin regardless:

# Start “Dynamix Auto Fan Control” plugin

/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan ‘start’ &>/dev/null

Link

This did not start autofan when rebooting the server. Does anyone have a better solution I can use? My PMW controller is 4

 

FIXED: 

I changed to using a userscript:

#!/bin/bash
/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan start

 

At first start array only

Edited July 21, 20241 yr by Soulplayer

Sorry if it has been asked. I'm also new to unraid. Actually I want to use dynamix stop shell plugin. (already installed) because my unraid won't reboot and the GUI crash (done powerdown -r and it's not work). All I could do is shh. I don't understand how to use this plugin and I couldn't find the tutorial anywhere.  Call me stupid but I've tried for many days. helped would be appreciated

(sorry for my english)

5 hours ago, brutalmethod said:

don't understand how to use this plugin

There is nothing for you to do. The explanation of the plugin is on your Plugins page.

Quote

The Dynamix Stop Shell plugin adds a script which gets invoked when the array is stopped. This script looks for any open shells in /mnt/... and terminate them. This ensures the array can be stopped.

Be aware that automatic terminating of open shells may lead to data loss if an active process is writing to the array.

 

This happens automatically when you stop the array.

13 hours ago, brutalmethod said:

Sorry if it has been asked. I'm also new to unraid. Actually I want to use dynamix stop shell plugin. (already installed) because my unraid won't reboot and the GUI crash (done powerdown -r and it's not work). All I could do is shh. I don't understand how to use this plugin and I couldn't find the tutorial anywhere.  Call me stupid but I've tried for many days. helped would be appreciated

(sorry for my english)

How long have you waited for the reboot attempt to finish?  Lots of things that can take a while to shut down before it reboots compared to a more typical computer.

Can you please assist with this issue to do with this driver?,

Or could you advise on another way to get around it, be it a new fan controller?

My current setup
Asus Pro WS WRX90E-SAGE SE

AMD Ryzen Threadripper PRO 7965WX
Noctua NH-D9 TR5-SP6 4U CPU Cooler

Edited July 27, 20241 yr by Aedankerr
Didnt list computer parts

hi y'all so i have set up my unraid server to go to sleep, that part goes well.

when i wake it up by wol or with the power button on the tower it start up and just shutdown right after.

I have attached the syslog of the whole wake up shutdown process.

If anyone can help me with that I thank you

best regards

syslog.txt

is the share floor plugin still working with the newest 6.12.11?  I have been running this plugin for almost 2 years and just noticed it is no longer updating the minimum share sizes.  When i run manually the plugin, it immediately reports: "No Shares or Pools updated".  Anyone else seen this before?

 

Thanks,

JD

 

I just installed the Auto Fan Control plugin in unraid 6.12.11 on a QNAP TVS-h874.  After installation, I configure the minimum PWM value and it increases the fan speed as expected.  Upon reboot, the fans run at minimum speed despite the plugin showing the previously configured PWM value.  If I re-apply the same value, the fan speed increases once again.

 

Why is the PWM value not applied during bootup?

The plugin has an issue where it will only check to see if the first PWM controller is enabled before auto-starting.

 

 I fixed it by using a userscript:

#!/bin/bash /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan start

 

At first start array only

Soulplayer, this seems to have resolved my issue, thanks for the tip!

 

Anyone know if it's possible to run two instance of Auto Fan Control to control two different PWMs?

So I believe I spoke too soon...  this problem is persisting.  I'm only able to fix it by selecting 'DETECT' under the PWM fan setting and then choosing apply.  The value in the settings doesn't change when I re-detect it, but it seems to update the setting in the running app.

 

 

What I noticed, is that the value in the settings doesn't match what's in the config file.  Settings shows 'hwmon4' while the config file shows 'hwmon2'.  It's as if the settings are not being pushed to the startup config file, although the settings page shows the correct values after a reboot.

 

 

I tried to modify the config to match what's in the settings page, but then it returns a permissions denied error when starting.

 

Any ideas?

1 hour ago, ritti said:

So I believe I spoke too soon...  this problem is persisting.  I'm only able to fix it by selecting 'DETECT' under the PWM fan setting and then choosing apply.  The value in the settings doesn't change when I re-detect it, but it seems to update the setting in the running app.

 

 

What I noticed, is that the value in the settings doesn't match what's in the config file.  Settings shows 'hwmon4' while the config file shows 'hwmon2'.  It's as if the settings are not being pushed to the startup config file, although the settings page shows the correct values after a reboot.

 

 

I tried to modify the config to match what's in the settings page, but then it returns a permissions denied error when starting.

 

Any ideas?

that is not the place to edit!

 

that is the actual plugin, not the config file.

 

config file is at /flash/config/plugins/ plugin name folder. delete all config files and start over

 

Any idea why Dynamix System Temp is now blacklisted?

7 minutes ago, Panja said:

Any idea why Dynamix System Temp is now blacklisted?

Came for the same question, I think it updated to a new version built for v7

 

(changelog shows

2024.07.10

bugfix for Unraid version 7.0.0)

 

and isn't meant for pre-v7 but I could be wrong 

I think I asked somewhere else, I would like to add the feature of using any temp sensor not just a drive to Auto Fan. Using a temp probe from my corsair commander pro I have embedded in the LSI heatsink. I would like to drive a fan mounted to it. 

OR

using the LSI temp sensor if it has one?

here you can see my Corsair output. 
corsaircpro-hid-3-2
Adapter: HID adapter
in0:          11.99 V  
in1:           4.99 V  
in2:           3.40 V  
fan1 4pin:    485 RPM
fan2 4pin:   1670 RPM
fan3 4pin:    467 RPM
fan4 3pin:   2359 RPM
temp1:        +33.5°C  


/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:1B1C:0C10.0002/hwmon/hwmon3/fan1_input
/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:1B1C:0C10.0002/hwmon/hwmon3/fan2_input
/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:1B1C:0C10.0002/hwmon/hwmon3/fan3_input

/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:1B1C:0C10.0002/hwmon/hwmon3/fan4_input

@Cosmo:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:1B1C:0C10.0002/hwmon/hwmon3# ls -l

lrwxrwxrwx 1 root root    0 Aug 17 10:49 device -> ../../../0003:1B1C:0C10.0002/
-r--r--r-- 1 root root 4096 Aug 17 10:49 fan1_input
-r--r--r-- 1 root root 4096 Aug 16 06:29 fan1_label
-rw-r--r-- 1 root root 4096 Aug 17 10:58 fan1_target
-r--r--r-- 1 root root 4096 Aug 17 10:49 fan2_input
-r--r--r-- 1 root root 4096 Aug 16 06:29 fan2_label
-rw-r--r-- 1 root root 4096 Aug 17 10:58 fan2_target
-r--r--r-- 1 root root 4096 Aug 17 10:49 fan3_input
-r--r--r-- 1 root root 4096 Aug 16 06:29 fan3_label
-rw-r--r-- 1 root root 4096 Aug 17 10:58 fan3_target
-r--r--r-- 1 root root 4096 Aug 17 10:49 fan4_input
-r--r--r-- 1 root root 4096 Aug 16 06:29 fan4_label
-rw-r--r-- 1 root root 4096 Aug 17 10:58 fan4_target
-r--r--r-- 1 root root 4096 Aug 17 10:49 in0_input
-r--r--r-- 1 root root 4096 Aug 17 10:49 in1_input
-r--r--r-- 1 root root 4096 Aug 17 10:49 in2_input
-r--r--r-- 1 root root 4096 Aug 17 10:49 name
drwxr-xr-x 2 root root    0 Aug 17 10:58 power/
-rw-r--r-- 1 root root 4096 Aug 17 10:58 pwm1
-rw-r--r-- 1 root root 4096 Aug 17 10:47 pwm2
-rw-r--r-- 1 root root 4096 Aug 17 10:58 pwm3
-rw-r--r-- 1 root root 4096 Aug 17 10:47 pwm4
lrwxrwxrwx 1 root root    0 Aug 17 10:58 subsystem -> ../../../../../../../../../class/hwmon/
-r--r--r-- 1 root root 4096 Aug 17 10:49 temp1_input
-rw-r--r-- 1 root root 4096 Aug 17 10:58 uevent

Edited August 17, 20241 yr by TheDirtyR

Auto Fan Control is flaky for me.

 

Controller: nct6797 on an MSI b450 board

 

It appears to work just fine but at some point gets stuck and won't modify fan temperatures anymore. When trying to restart via CLI i get errors saying device or resource busy...

Hi there, after updating to 6.12.12 using the Dynamix Fan Control, its stopped detecting "highest disk temp" value and is reporting 0º causing the fans to run at 0 rpm. 

Aug 21 19:31:40 unraid autofan: Highest disk temp is 0C, adjusting fan speed from: FULL (100% @ 0rpm) to: OFF (0% @ 0rpm)

This was fine with 6.12.11. 

Version 2023.02.05a was included in the update and theres no errors in the logs during the installation or afterwards. 

In the GUI management settings I could detect the PWM and min fan setting. 

I've disabled the plugin and resumed fan speeds.  

Just discovered the Dynamix Safe Mode plugin.    Not yet tested how effective it is but I am hopeful.    However one feature that I think it would be very simple to add and could help with debugging issues is to write a syslog entry every time this plugin turns Safe mode on or off.   That would make it easier to see what changes there are to Unraid behaviour depending on whether Safe Mode is turned on or off dynamically.