42 minutes ago, trivi said:

 

Thank you. I did run modprobe:

 

modprobe: FATAL: Module NCT6775 not found in directory /lib/modules/6.6.68-Unraid

 

Is this a driver problem?

 

And there is no fan controller detected in the system temp app:

 

 

EDIT:

 

If I run modprobe ftsteutates, then there are the pwm sensors listed, if I run sensors:

 

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +36.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:       +33.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:       +32.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:       +32.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:       +37.0°C  (high = +80.0°C, crit = +100.0°C)

pch_cannonlake-virtual-0
Adapter: Virtual device
MB Temp:      +34.0°C  

ftsteutates-i2c-0-73
Adapter: SMBus I801 adapter at efa0
in0:           3.00 V  
in1:           3.04 V  
in2:           3.09 V  
in3:           2.73 V  
fan1:         600 RPM
fan2:         840 RPM
fan3:         840 RPM
fan4:           FAULT
fan5:           FAULT
fan6:           FAULT
fan7:           FAULT
fan8:           FAULT
temp1:        +34.0°C  
temp2:        +25.0°C  
temp3:        +28.0°C  
temp4:        +25.0°C  
temp5:        +25.0°C  
temp6:        +33.0°C  
temp7:          FAULT  
temp8:          FAULT  
temp9:          FAULT  
temp10:         FAULT  
temp11:         FAULT  
temp12:         FAULT  
temp13:         FAULT  
temp14:         FAULT  
temp15:         FAULT  
temp16:         FAULT  

nvme-pci-0300
Adapter: PCI adapter
Composite:    +30.9°C  (low  =  -0.1°C, high = +71.8°C)
                       (crit = +89.8°C)

 

Then system temp detects the pwm controller, but fan control still does not.

Post the entire output of sensors-detect 

1 hour ago, trivi said:

 

Thank you. I did run modprobe:

 

modprobe: FATAL: Module NCT6775 not found in directory /lib/modules/6.6.68-Unraid

modprobe nct6775 not modprobe NCT6775

8 hours ago, spl147 said:

Post the entire output of sensors-detect 

Can't post it as code, so I attached a file.

 

 

modprobe nct6775

 

modprobe: ERROR: could not insert 'nct6775': No such device

 

sensors-detect.txt

Edited February 6, 20251 yr by trivi

9 hours ago, trivi said:

Can't post it as code, so I attached a file.

 

 

modprobe nct6775

 

modprobe: ERROR: could not insert 'nct6775': No such device

 

sensors-detect.txt 9.92 kB · 2 downloads

Search is your friend!

 

 

modprobe ftsteutates

Hi, regarding autofan, It's working great, but I've noticed that the temperature of my cache NVMEs is not taken into account for  fan control. Apparently theres a fix thats not in the plugin yet. Did anyone make this work and can share how, maybe?

Hello,

I've been using the S3 Sleep plugin for ages without issues. But for a while now I've run into problems:

 

Sometimes when I put the system to sleep using the button on the main page instead of going to sleep the server does a clean shutdown.

 

More often the system does a clean shutdown immediately after waking up from sleep. This happens regardless of it waking up by manual button press or by using WOL. I've attached the diagnostics after this just happened. I couldn't find a reason for the shutdown in the previous syslog. It just states "shutdown[19899]: shutting down for system halt".

 

Feb  9 11:08:43 Starhost kernel: sd 6:0:0:0: [sdd] Starting disk
Feb  9 11:08:43 Starhost kernel: OOM killer enabled.
Feb  9 11:08:43 Starhost kernel: Restarting tasks ... 
Feb  9 11:08:43 Starhost kernel: sd 7:0:0:0: [sdg] Starting disk
Feb  9 11:08:43 Starhost kernel: done.
Feb  9 11:08:43 Starhost kernel: random: crng reseeded on system resumption
Feb  9 11:08:43 Starhost kernel: PM: suspend exit
Feb  9 11:08:43 Starhost emhttpd: spinning down /dev/sdl
Feb  9 11:08:43 Starhost shutdown[19899]: shutting down for system halt
Feb  9 11:08:43 Starhost dhcpcd[2207]: br0: deleting route to 192.168.10.0/24
Feb  9 11:08:43 Starhost dhcpcd[2207]: br0: deleting default route via 192.168.10.1
Feb  9 11:08:43 Starhost dnsmasq[18427]: no servers found in /etc/resolv.conf, will retry
Feb  9 11:08:43 Starhost dhcpcd[2207]: br0: carrier acquired
Feb  9 11:08:43 Starhost kernel: sd 8:0:2:0: Power-on or device reset occurred
Feb  9 11:08:43 Starhost kernel: sd 8:0:0:0: Power-on or device reset occurred
Feb  9 11:08:43 Starhost kernel: sd 8:0:1:0: Power-on or device reset occurred
Feb  9 11:08:43 Starhost kernel: sd 8:0:5:0: Power-on or device reset occurred
Feb  9 11:08:43 Starhost kernel: sd 8:0:3:0: Power-on or device reset occurred
Feb  9 11:08:43 Starhost kernel: sd 8:0:4:0: Power-on or device reset occurred
Feb  9 11:08:43 Starhost dhcpcd[2207]: br0: soliciting a DHCP lease
Feb  9 11:08:43 Starhost dhcpcd[2207]: br0: offered 192.168.10.10 from 192.168.10.1
Feb  9 11:08:43 Starhost dhcpcd[2207]: br0: probing address 192.168.10.10/24
Feb  9 11:08:44 Starhost init: Switching to runlevel: 0
Feb  9 11:08:44 Starhost s3_sleep: Wake-up from sleep mode
Feb  9 11:08:44 Starhost rc.0: Running shutdown script /etc/rc.d/rc.0:
Feb  9 11:08:44 Starhost init: Trying to re-exec init
Feb  9 11:08:44 Starhost rc.0: Saving system time to the hardware clock (UTC).
Feb  9 11:08:44 Starhost rc.0: Creating system time correction file /etc/adjtime.
Feb  9 11:08:44 Starhost rc.0: /sbin/hwclock --utc --systohc

 

diagnostics-20250209-1118.zip

On 2/9/2025 at 6:08 AM, cryon said:

Hi, regarding autofan, It's working great, but I've noticed that the temperature of my cache NVMEs is not taken into account for  fan control. Apparently theres a fix thats not in the plugin yet. Did anyone make this work and can share how, maybe?

 

@Phoenix Down has posted a solution to this a while back, but it has not been incorporated into the autofan plugin. See link below for details. If you know what you’re doing you can mod your install of autofan plugin to not ignore the NVME temps.

 

I assume this will not be incorporated unless someone elects to fork and continue developing an alternative version of autofan, as it appears @bonienl is no longer actively supporting this plugin.

 

 

 

On 1/18/2025 at 8:08 PM, MothyTim said:

I have the same problem, fans are all spinning at full speed since updating to 7.0 and hoping for a fix soon?

 

Same here - after the update to 7.0 the fans spin up to 100% every other day - no matter what the temperature is. 

Only a reboot brings it back to normal

 

Edited February 16, 20251 yr by Jabberwocky

On 1/31/2025 at 1:40 PM, spl147 said:

stop fan control, delete dynamix.system.autofan2.cfg rename dynamix.system.autofan1.cfg to dynamix.system.autofan.cfg, remove the line from the go script. then reboot, then start fan control

Thanks for this has resolved my fan issues massively, really appreciate it.

13 minutes ago, archieboy72 said:

Thanks for this has resolved my fan issues massively, really appreciate it.

Glad to help

New to Unraid  so learning . Have set up a second serrver as backup and I want it to sleep when not in use. Installed S3 sleep plugin . Server will go to sleep but wont wake via a WOL . Board supports all sleep states . Reinstalled plugin and now see the SLEEP button doesn't show on main page.

Diagnosics attached.

Help please.

box-diagnostics-20250218-0924.zip

@dOM152 I'm affraid nobody official is maintaining these addons at the moment.

 

About WOL: did you set "g" as WOL options before sleep in the config-gui of S3? If so, it might not work from there. Another option would be to set it in the go file or create a user script running at startup. (ethtool -s eth0 wol g)

 

About the icon: maybe a reboot inbetween uninstall and reinstall could help?

Edited February 18, 20251 yr by NoRaid99

13 hours ago, NoRaid99 said:

@dOM152 I'm affraid nobody official is maintaining these addons at the moment.

 

About WOL: did you set "g" as WOL options before sleep in the config-gui of S3? If so, it might not work from there. Another option would be to set it in the go file or create a user script running at startup. (ethtool -s eth0 wol g)

 

About the icon: maybe a reboot inbetween uninstall and reinstall could help?

Thanks for the reply. I hadn't set "g" but have done now and it works!

 

On 3/3/2021 at 9:12 PM, Zonediver said:

 

 

Its not broken, just "vice versa" 😉

You can fix this.

If the sleep plug-in is active, you can enter all drives (which you want to monitor) under "Monitor disks outside array:"

There is something "the other way around" - but it is working 😉👍

It seems the plugin does not recognise the array correctly (last update from 6.2020)

 

 

 

I recently tried S3 sleep plugin, i face the same issue, though all the drive in array are active, i get the below message.

All monitored HDDs are spun down

and after the inactivity timer, the server goes into sleep. I tried adding theh devices to monitor disks outside array to address this for now.

Shouldn't there be a permament fix for this ?

I am currently on UNRAID 6.12.10 with 

s3_sleep version: 3.0.11

 

(S3 sleep plugin version).

Is there anything I am missing here. ?

Edited February 21, 20251 yr by makesh86
s3 sleep plg version update

Does anyone know if these plugins are under active development? I see that @bonienl hasn't posted since May of last year. Is he/she ok?

Can System AutoFan be used to achieve plain constant fan speeds by just setting each PWM Controller's Minimum PWM value field and emptying all the rest of the fields? Or could there still be some interactions with the drives' temperatures?

 

(As I only have two PWM headers being shared by five case fans, the drives and cards having very diverse temp. ranges and cooling needs that don't lend themselves to depend on drives' temps. only, and the case is in a storage room where noise isn't too much of a concern, I rather set fixed speeds that work for all situations)

2 hours ago, MetricTonto said:

Can System AutoFan be used to achieve plain constant fan speeds by just setting each PWM Controller's Minimum PWM value field and emptying all the rest of the fields? Or could there still be some interactions with the drives' temperatures?

 

(As I only have two PWM headers being shared by five case fans, the drives and cards having very diverse temp. ranges and cooling needs that don't lend themselves to depend on drives' temps. only, and the case is in a storage room where noise isn't too much of a concern, I rather set fixed speeds that work for all situations)

The plugin is to control fan speeds based on hdd temps.

use your bios to set fan speeds

Sadly, I can't do that in an effective manner: the old motherboard's BIOS only allows for modes that either regulate fan speeds depending on temperature reads (which wouldn't deal correctly with my diverse storage units' types and situations: very different thermal ranges and airflow situations) or just let the fans go 100% uncontrolled. No fixed percentage settings available.

 

I think I've managed to work it out, though. The solution for setting a constant RPM seems to be:

1. Set the Maximum RPM Value to the desired speed.
2. Set the min/max storage temperature range to something that will never be reached, say, 80º to 90º C.

i am using unraid 7.0.0, tried to reset my unraid server with the Dynamix Factory Reset plugin.

i selected yes for"Keep Array and Pool assignments". while after i clicked FACTORY RESET and reboot my server, nothing changed.

is there any other way to reset my sever with data and array preserved?

22 minutes ago, allenchou1994 said:

is there any other way to reset my sever with data and array preserved?

You can do this:

 

backup the current one first and then recreate it using the USB tool and just restore the key, super.dat and the pools folder for the assignments.

4 hours ago, JorgeB said:

You can do this:

 

backup the current one first and then recreate it using the USB tool and just restore the key, super.dat and the pools folder for the assignments.

could you tell me where is the super.dat? and i checked my pool folder, there is only cachs assignment no array info

23 minutes ago, allenchou1994 said:

ould you tell me where is the super.dat?

/config/super.dat

16 hours ago, JorgeB said:

/config/super.dat

what about the pool folder,  i only saw cache.cfg, no array assignment

The pool folder is for pools as its name says, array config is in the super.dat.

Hi,

 

I would like to make a suggestion for a new feature in the upcomming releases of "Dynamix Auto Fan Control":

- Add a new field in the configuration to set a fan name. 

- Display the fan name in the bottom bar of UnRAID.

 

Instead of the "flag" icon, the fan name could be displayed.

 

Thanks for your amazing work making these amazing plugins available to all of us!

 

Regards,

Edited March 4, 20251 yr by PetabyteLDA
plugin name missing