I have a minimum set but that doesn't solve the underlying issue that the cache drive temperature isn't being monitored by the plugin even though it's listed as a drive that can be "excluded"

If you have a min set then the fans will not turn off, if they turn off the you min is too low for the fans.

Works fine here with a nvme cache drive

@PicPoc ah ya seems like it  probably why no more updates  to the fan support  or issue i having as i trying to figure how to script it...  might have to ask in general

you guys dont happen to know how i can run say pwm4  the apply option from the command line do ya?  i looked into the emhttp folder and looked at some of the code but i dont even know how to run it from the command line  to force the fans to stop on reboot.. since it not reading the plugin in and say if its below 35 degrees not to run..  as i exclude my nvme drive...  so each time i reboot  or boot up  i gotta adjust the pwm4  then reset back  and then press apply just to get the fans to stop

Just now, comet424 said:

so each time i reboot  or boot up  i gotta adjust the pwm4  then reset back  and then press apply just to get the fans to stop

may just read a little upper in the Thread, its may just the autostart function which is not properly working and i posted a cmd howto

@alturismo ok ill scroll up and look  and let you know if it fix's it.. i apprecaite the speedy reply too 🙂

@alturismo thanks it fixed it...    is the autostart a problem with the plugin or how unraid works now...

i tested it on my one server...    ill add it to my other servers...  thank you

 

 

10 minutes ago, comet424 said:

is the autostart a problem with the plugin or how unraid works now...

actually i dont know, i just figured autostart stopped working ... so i looked how to solve it

@alturismo  oh lol .. well least you figured it out or i be still hitting the apply..  since no one in general chat replied which they probably dont know  or too soon for a reply lol...  as i wasnt sure to ask help in here or there...    

 

least my main server isnt running fans at 5000 rpms now they off or at 1000 lol

Hello,

I'm having trouble understanding the Auto Fan Setup and was hoping somebody can clarify.

 

The setup menu shows me three PWM controler.

Are these my fans header on the mainboard that were detected by the plugin?

 

But when I switch between the three entries, the path to the PWM fan stays exactly the same for each contoller.

/sys/devices/platform/nct6775.656/hwmon/hwmon3/fan1_input

/sys/devices/platform/nct6775.656/hwmon/hwmon3/fan1_input

/sys/devices/platform/nct6775.656/hwmon/hwmon3/fan1_input

 

The hwmon3 directory contains other fan*_input files though.

I have an issue with the sleep function. 

 

I disabled the S3 sleep function. 

 

But now my server seems to randomly go into standby / sleep mode. 

 

Not sure what is going here. 

8 hours ago, bobalot said:

I have an issue with the sleep function. 

 

I disabled the S3 sleep function. 

 

But now my server seems to randomly go into standby / sleep mode. 

 

Not sure what is going here. 

Have you actually gone as far as uninstalling the plugin?

10 hours ago, itimpi said:

Have you actually gone as far as uninstalling the plugin?

Now I feel like a dingus. 

 

That seemed to have worked. 

On 7/16/2023 at 12:20 PM, pille said:

I have som issues with the Auto Fan Plugin. I can not find any PWM Controllers. Drop down only says "none". System Temp Plugin works fine. Anyone has an idea how to fix the Fan error?

I do use PWM Fans all attached directly to the mainboard.

Did you get a response or a solution to this?
Having the same problem,, have not tried the temp-plugin, but I'm using glances+hddtemp to show HD-temps in HA - could that be an issue?

Two pwm-fans directly to new motherboard; Gibabyte Z690

I have a dell "0NK70N" mobo.  Using Autofan floods my system logs with pointless info like "...autofan: Highest disk temp is 32C, adjusting fan speed from: 128 (50% @ 888rpm) to: 196 (76% @ 4967rpm)" every few mins (or every few seconds if the server is putting in work).   The movie quote, "frankly my dear, i don't give a dam" comes to mind.  

Its useless (my dashboard tells me fan speeds, if im curious), and bury's important information that i might want to see in the logs, from earlier in the day.


HOW DO I SHUT THIS UP???  I don't need to know what the plugin is doing every time it changes fan speeds!  I not sure why it even does this by default!  Please tell me someone has a way to fix this?!?!?!

---

 

A separate question:  Autofan only sees 3 out of the 8 fans/headers (incl CPU fans).  Additionally, one of the 3 fans that it does see, it doesn't seem to be able to control at all! 
For now, ive resorted to using a powered fan splitter and jerry rigged jumpers (yay dell non-standard fan headers...companies should be sued for this kinda nonsense; but i digress) to one of the headers that is controlled by autofan, and force most of the fans to run on that sensor bank...but its not ideal.  

---

Lastly: is there a way to make Autofan control fans based on CPU/MOBO/Video/etc temps, instead of just HDD's?  This might not be possible without a full re-work, but thought i would ask!

 

+++

Normally my Google-fu hits hard, but i can't seem to knock this one out!  So I gave up, and am asking ya'll!  

Edited July 27, 20233 yr by miicar

5 hours ago, miicar said:

I don't need to know what the plugin is doing every time it changes fan speeds!  I not sure why it even does this by default!  Please tell me someone has a way to fix this?!?!?!

there is nothing to "fix" as its by design ... if you dont want to see those syslog messages ... and if you would have searched ... you would have found as sample the "enhanced syslog setting" plugin ... where  you can filter events to not show ...

 

 

5 hours ago, miicar said:

Lastly: is there a way to make Autofan control fans based on CPU/MOBO/Video/etc temps, instead of just HDD's?  This might not be possible without a full re-work, but thought i would ask!

same here, asked already many times in this thread ... lets make it short, no ... only hdd temps are used as base by design, not wanted ... for CPU fans, this should be done in your BIOS and set your curve there.

 

also imagine how many log entries there would be if your CPU is controlled ...

12 hours ago, alturismo said:

there is nothing to "fix" as its by design ... if you dont want to see those syslog messages ... and if you would have searched ... you would have found as sample the "enhanced syslog setting" plugin ... where  you can filter events to not show ...

 

 

same here, asked already many times in this thread ... lets make it short, no ... only hdd temps are used as base by design, not wanted ... for CPU fans, this should be done in your BIOS and set your curve there.

 

also imagine how many log entries there would be if your CPU is controlled ...

imagine if they made a setting to quiet the pointless logs, like most other programmers do...

Since pool discs temperature is not reported while disks are spinned down and I have System AutoFan tied to discs temperature, the fans are stopping. I need them to be in min rpm while discs are down. Would you consider adding this as a feature (checkbox or something) ?

10 hours ago, KrisMin said:

Since pool discs temperature is not reported while disks are spinned down and I have System AutoFan tied to discs temperature, the fans are stopping. I need them to be in min rpm while discs are down. Would you consider adding this as a feature (checkbox or something) ?

You need to set the "Minimum PWM Value" to something high enough to keep them spinning.  That's how I fixed mine, you might have to play with the value to find what works. 255 is "Max" - 65 works well for my system.

Edited August 1, 20233 yr by WackyWRZ

or may exlude the cache devices ... like here, i want the fans to turn off and dont need the nvme ssd drives as measure points ...

 

or like @WackyWRZ already mentioned, set a min value ...

 

Somewhere along the lines I lost the percentage next to the RPM in the footer for System Temp.  In the syslog I can see:

 

autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 2492rpm) to: 114 (44% @ 1354rpm)

 

But in the Unraid footer I see the fan RPM and a 0% next to it all the time.  Any suggestions on what to check for this?  It looks like the system temperature plugin is supposed to pull the percentage from autofan, but it's getting a 0.

Edited August 1, 20233 yr by WackyWRZ

On 8/1/2023 at 9:01 PM, WackyWRZ said:

You need to set the "Minimum PWM Value" to something high enough to keep them spinning.  That's how I fixed mine, you might have to play with the value to find what works. 255 is "Max" - 65 works well for my system.

This method is not working for me. When discs spin down, their temperature is not reported and fans stop no matter what min pwm value is set to. This is why I asked for additional "check box" feature.

Edited August 2, 20233 yr by KrisMin

9 hours ago, KrisMin said:

This method is not working for me. When discs spin down, their temperature is not reported and fans stop no matter what min pwm value is set to. This is why I asked for additional "check box" feature.

working fine here ...

 

sample, forced now even disks are down

 

normally off while disks are down

 

 

alturismo, I have some kind of anomaly then. Likely hardware related. I guess I'll make a work around to keep a couple of fans on 24/7.

Edited August 3, 20233 yr by KrisMin

On 3/2/2015 at 8:25 PM, gfjardim said:

 

Please post the result of this command:

 

 

find -L /sys/class/hwmon/ -maxdepth 5 -iname "pwm[0-9]" 2>/dev/null

 

 

I know the autofan plugin is still a work in progress and won't detect everything. Can someone confirm if my system should be detectable or not?  I've seen many other posts with people asking pretty much the same thing. I found this quoted post from many years ago, and tried running that find command. It returned nothing.

I have a Gigabyte Z390 UD motherboard. It has 3 system fans and 1 CPU fan. I'm running unraid 6.12.3.

 

 

I also just found out about the pwmconfig command, so I ran it and here are the results:

# pwmconfig version 3.6.0
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed

Edited August 4, 20233 yr by Lonewolf147

So I just found another post that actually solved my issue!  unraid isn't recognizing the pwm sensor module, and I needed to change the ID of it to trick it into recognizing it.