Jump to content

Dynamix - V6 Plugins


Recommended Posts

On 4/13/2020 at 2:10 PM, henris said:

Auto Fan Control stopped working on Asus Z390M-PLUS (NCT6796D / NCT6798D) when upgrading to 6.8.x

I built my third UnRAID server last summer running with version 6.7.1. Out of the box most sensors were not detected (eg. the fan speeds), only temperatures were. After a quite a bit of reading in this thread and else where I managed to understand that I needed to manually load the correct driver module with command "modprobe nct6775" which I also put to my go file to make it persist over boot. Everything was fine from sensors perspective and Auto fan control was working pretty nicely (except for the nvme exclusion issue).

Just tried this again and the problem still persists. Did some more digging and found this kernel bug report from 2019:
"Bug 204807 - Hardware monitoring sensor nct6798d doesn't work unless acpi_enforce_resources=lax is enabled"

https://bugzilla.kernel.org/show_bug.cgi?id=204807

This fully explains why it stopped working and what is the workaround. Though I will not be using the workaround because it is not considered safe and I can live with the fixed fan speed.

 

There is a bug fix in kernel version 5.2.11 so I will wait for it to come through Unraid.

Link to comment

Ive started using the S3 Sleep plugin to shutdown my server at night. It works fine with WOL however every time the system restarts it commences a Parity-Check as a result of an unclean shutdown.

 

Ive seen a number of posts from users with similar issues however none have a solution. Anyone else have this issue and found a solution?

Link to comment
  • 2 weeks later...

Hi, since i updated to unraid Version 6.9.2, i have a Problem with the S3 Sleep Plugin.

It seemed to shut the system down instead of sleep and never came back up, i mirrored the syslog to flash and now finaly found the time to look into it but i don't really understand why its happening:

The Server was supposed to go sleep at 2:00 and wakeup the same day at 19:00.

To Achive this i set this custom command before sleep:

echo 0 > /sys/class/rtc/rtc0/wakealarm
echo `date '+%s' --date='19:00:00'` > /sys/class/rtc/rtc0/wakealarm

It was working fine for years.

 

In the syslog i now saw whats happening:

Its going to sleep at night as planned:

Oct  6 02:00:16 unRAID s3_sleep: Disk activity detected. Reset timers.
Oct  6 02:01:16 unRAID s3_sleep: All monitored HDDs are spun down
Oct  6 02:01:16 unRAID s3_sleep: Extra delay period running: 0 minute(s)
Oct  6 02:01:16 unRAID s3_sleep: Initialize TCP activity counter
Oct  6 02:02:16 unRAID s3_sleep: All monitored HDDs are spun down
Oct  6 02:02:16 unRAID s3_sleep: Check TCP/SSH/TTY/IP activity
Oct  6 02:02:38 unRAID s3_sleep: Communication state is idle
Oct  6 02:02:38 unRAID s3_sleep: Execute custom commands before sleep
Oct  6 02:02:38 unRAID s3_sleep: Enter sleep state now
Oct  6 02:02:38 unRAID kernel: PM: suspend entry (deep)
Oct  6 02:02:38 unRAID kernel: Filesystems sync: 0.003 seconds

But when it wakes up, it seems to do some stuff that was supposed to be done before sleep but i never looked into the syslog before the problem so it could be normal:

Oct  6 19:00:12 unRAID kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct  6 19:00:12 unRAID kernel: OOM killer disabled.
Oct  6 19:00:12 unRAID kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Oct  6 19:00:12 unRAID kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct  6 19:00:12 unRAID kernel: e1000e: EEE TX LPI TIMER: 00000011
Oct  6 19:00:12 unRAID kernel: sd 5:0:0:0: [sde] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 6:0:0:0: [sdf] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 6:0:0:0: [sdf] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 5:0:0:0: [sde] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 4:0:0:0: [sdd] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 2:0:0:0: [sdb] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 3:0:0:0: [sdc] Stopping disk
Oct  6 19:00:12 unRAID kernel: bond0: (slave eth0): link status definitely down, disabling slave
Oct  6 19:00:12 unRAID kernel: device eth0 left promiscuous mode
Oct  6 19:00:12 unRAID kernel: bond0: now running without any active interface!
Oct  6 19:00:12 unRAID kernel: br0: port 1(bond0) entered disabled state
Oct  6 19:00:12 unRAID kernel: ACPI: Preparing to enter system sleep state S3
Oct  6 19:00:12 unRAID kernel: PM: Saving platform NVS memory
Oct  6 19:00:12 unRAID kernel: Disabling non-boot CPUs ...

After that it seems to do normal wakeup stuff:

Oct  6 19:00:12 unRAID kernel: smpboot: CPU 1 is now offline
Oct  6 19:00:12 unRAID kernel: smpboot: CPU 2 is now offline
Oct  6 19:00:12 unRAID kernel: smpboot: CPU 3 is now offline
Oct  6 19:00:12 unRAID kernel: ACPI: Low-level resume complete
Oct  6 19:00:12 unRAID kernel: PM: Restoring platform NVS memory
Oct  6 19:00:12 unRAID kernel: smpboot: Scheduler frequency invariance went wobbly, disabling!
Oct  6 19:00:12 unRAID kernel: Enabling non-boot CPUs ...
Oct  6 19:00:12 unRAID kernel: x86: Booting SMP configuration:
Oct  6 19:00:12 unRAID kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct  6 19:00:12 unRAID kernel: CPU1 is up
Oct  6 19:00:12 unRAID kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Oct  6 19:00:12 unRAID kernel: CPU2 is up
Oct  6 19:00:12 unRAID kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct  6 19:00:12 unRAID kernel: CPU3 is up
Oct  6 19:00:12 unRAID kernel: ACPI: Waking up from system sleep state S3
Oct  6 19:00:12 unRAID kernel: sd 2:0:0:0: [sdb] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 5:0:0:0: [sde] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 3:0:0:0: [sdc] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 4:0:0:0: [sdd] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 6:0:0:0: [sdf] Starting disk

After that, there seems to be the problem, s3_sleep initiates a shutdown, which its not supposed to do and while at the same time still wakeup tasks are execudet like spinup:

Oct  6 19:00:12 unRAID s3_sleep: Shutdown system now
Oct  6 19:00:12 unRAID emhttpd: read SMART /dev/sdc
Oct  6 19:00:12 unRAID shutdown[27671]: shutting down for system halt
Oct  6 19:00:12 unRAID init: Switching to runlevel: 0
Oct  6 19:00:12 unRAID s3_sleep: System woken-up. Reset timers
Oct  6 19:00:12 unRAID init: Trying to re-exec init
Oct  6 19:00:14 unRAID kernel: mdcmd (46): nocheck cancel
Oct  6 19:00:15 unRAID emhttpd: Spinning up all drives...
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdd
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sde
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdb
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdf
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdc
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sda
Oct  6 19:00:15 unRAID emhttpd: Stopping services...
Oct  6 19:00:15 unRAID emhttpd: shcmd (74385): /etc/rc.d/rc.libvirt stop
Oct  6 19:00:15 unRAID root: Waiting on VMs to shutdown

Here are my Plugin-settings, its Version 3.0.8

image.thumb.png.82f14d30b85509932fcc9a5e899dd958.png

Full syslog is also attached. I hope you can help me with this problem, thanks in advance.

syslog

Link to comment

Hi

 

I think I have found a bug with the way sys temp handles HID devices for sensor output.

 

For more detail on the issue, I raised an issue on github here - https://github.com/lm-sensors/lm-sensors/issues/369

 

In summary - 

 

I have the Corsair Commander Pro connected to my UNRAID server. Sensors show the correct info:

 

# sensors
corsaircpro-hid-3-2
Adapter: HID adapter
in0:          12.11 V  
in1:           4.99 V  
in2:           3.35 V  
fan1 4pin:    681 RPM
fan2 4pin:    680 RPM
fan3 4pin:    679 RPM

 

The problem is when I choose one of the fans in sys temp plugin settings - I get this error...

 

# sensors
Error: File /etc/sensors.d/sensors.conf, line 5: Undeclared bus id referenced
sensors_init: Can't parse bus name

 

The sensors.conf file in the plugin dir looks like this -

 

chip "k10temp-pci-00c3"
label "temp2" "CPU Temp"
chip "corsaircpro-hid-3-2"
label "fan1" "Array Fan"

 

It is line 3 that is generated by sys temp plugin that then causes an issue with sensors.

 

What could be the problem here?

 

Link to comment

I'm hoping the developers of the Auto Fan Control plugin can weigh in on this question.  Is there a reason why the plug-in is hard coded to look for the pwmX_enable sysfs attribute?  We're working on developing a driver for a embedded controller chip used in many QNAP NAS devices so that Unraid and other Linux based OSes can read and control fan speeds, however, this embedded controller chip doesn't provide a enable/disable PWM function (PWM is always enabled) therefore according to the hwmon/sysfs standards (at least the way we currently understand them) our driver should not be creating a PWM enable sysfs attribute.  However, without that attribute we get the following error from the Auto Fan Control plugin:

 

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/qnap-ec/hwmon/hwmon2/pwm7_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/qnap-ec/hwmon/hwmon2/pwm7_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/qnap-ec/hwmon/hwmon2/pwm7_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 />

Is it possible to change the plug-in to check if this attribute exists before trying to open it and if it doesn't exist assume PWM is enabled?  Or is the concern that without this attribute the plug-in doesn't know if PWM is enabled and the developers don't feel comfortable assuming that it is enabled?

 

Thanks,

Harry

Link to comment

Also wanted to clarify, according to the Dynamix plugin GitHub page (https://github.com/bergware/dynamix) the Dynamix plugins are now part of Unraid 6.x, so does that mean that the Unraid development team is now responsible for any bug fixes in those plugins (I guess that are no longer plugins if they are part of Unraid 6.x).  Is there a GitHub page where we can submit issues and pull requests for what used to be the Dynamix plugins?  The original GitHub page seems to be abandoned from an issues and pull request aspect.

 

Thanks,

Harry

 

 

Link to comment
7 hours ago, HarryMuscle said:

Also wanted to clarify, according to the Dynamix plugin GitHub page (https://github.com/bergware/dynamix) the Dynamix plugins are now part of Unraid 6.x, so does that mean that the Unraid development team is now responsible for any bug fixes in those plugins (I guess that are no longer plugins if they are part of Unraid 6.x).  Is there a GitHub page where we can submit issues and pull requests for what used to be the Dynamix plugins?  The original GitHub page seems to be abandoned from an issues and pull request aspect.

 

Thanks,

Harry

 

 

That is incorrect, the dynamix UI is now integrated into unRAID, not the plugins

Link to comment

So I¬īve got kind of a hit and miss problem with System Auto fan plugin.¬†
Sometimes it works, somtimes it doesen¬īt, and right now its Not working, and I cant for the life of me get it to work.¬†

It detect fans, but thats it. 
About this > < close to just trow it out the door and set my fans static, although my fans will run hot at some times. 
Anyone got anything? 
I¬īve got¬†acpi_enforce_resources=lax i syslinux.cfg, otherwise my fans wouldnt show up.

 

What it says in log, but as you can se, it doesnt change the fanspeed.

Nov  2 16:15:44 BelK autofan: autofan process ID 25339 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2624/hwmon/hwmon4/pwm4 -f /sys/devices/platform/it87.2624/hwmon/hwmon4/fan4_input
Nov  2 16:15:44 BelK autofan: autofan excluding drives nvme0n1,nvme1n1 from max temp calculations
Nov  2 16:15:50 BelK autofan: Highest disk temp is 34C, adjusting fan speed from: 63 (24% @ 681rpm) to: 148 (58% @ 606rpm)

 

I¬īm kinda¬†suspicious that bios just overrides it for some reason. (Gigabyte z590m)

But I don¬īt have another board to test on atm.

Edited by BeardElk
Link to comment
So I¬īve got kind of a hit and miss problem with System Auto fan plugin.¬†
Sometimes it works, somtimes it doesen¬īt, and right now its Not working, and I cant for the life of me get it to work.¬†
It detect fans, but thats it. 
About this > Anyone got anything? 
I¬īve got¬†acpi_enforce_resources=lax i syslinux.cfg, otherwise my fans wouldnt show up.
 
What it says in log, but as you can se, it doesnt change the fanspeed.
Nov  2 16:15:44 BelK autofan: autofan process ID 25339 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2624/hwmon/hwmon4/pwm4 -f /sys/devices/platform/it87.2624/hwmon/hwmon4/fan4_inputNov  2 16:15:44 BelK autofan: autofan excluding drives nvme0n1,nvme1n1 from max temp calculationsNov  2 16:15:50 BelK autofan: Highest disk temp is 34C, adjusting fan speed from: 63 (24% @ 681rpm) to: 148 (58% @ 606rpm)

 
I¬īm kinda¬†suspicious that bios just overrides it for some reason. (Gigabyte z590m)
But I don¬īt have another board to test on atm.


In bios fans should be set to full speed, autofan is not your issue if sensors detect doesnt have drivers four your board.
Link to comment
2 hours ago, spl147 said:


In bios fans should be set to full speed, autofan is not your issue if sensors detect doesnt have drivers four your board.

If I set my fans to full speed, then turn on auto fan, it just shuts them off. 

How tf is that not a auto fan prob?

Sensors detect does detect all drivers.

Edited by BeardElk
Link to comment
11 hours ago, BeardElk said:

If I set my fans to full speed, then turn on auto fan, it just shuts them off. 

How tf is that not a auto fan prob?

Sensors detect does detect all drivers.

What is your min pwm setting? Min temp setting?

 

min temp should be you idle temp, min pwm should be highest value you can set before you hear your fans

Link to comment

Hi there, just trying to get the Auto Fan Control plugin up and running. For some reason the "Detect" button next to the "PWM fan" field is greyed out, and also for the same button next to "Minimum PWM value". The "PWM controller" drop down also has "None" the only option.

 

Am I missing something simple here by chance?


The mobo I am using is the ASRock B250M Pro4 with an i5-7600K. The board does have 4 pin PWM headers that are currently in use via a basic fan curve in the BIOS.

Link to comment
1 hour ago, nametaken_thisonetoo said:

Hi there, just trying to get the Auto Fan Control plugin up and running. For some reason the "Detect" button next to the "PWM fan" field is greyed out, and also for the same button next to "Minimum PWM value". The "PWM controller" drop down also has "None" the only option.

 

Am I missing something simple here by chance?


The mobo I am using is the ASRock B250M Pro4 with an i5-7600K. The board does have 4 pin PWM headers that are currently in use via a basic fan curve in the BIOS.

Did you install pearl from the nerd pack plugin? It is required

Link to comment
On 11/3/2021 at 12:29 PM, spl147 said:

What is your min pwm setting? Min temp setting?

 

min temp should be you idle temp, min pwm should be highest value you can set before you hear your fans

I¬īm gonna apologize for my previous¬†language, was frustrated as hell!¬†
Min temp value does not matter what I set it to, min pwm does not matter what I set it to. 
If I set my fans 100% in bios, as soon as I "detect fan", and it detects it, my selected fan turns of. 
Does not matter what I set min temp or min pwm to, can not get selected fan to turn on again. 

Link to comment

Hi all, I am new to using the Dynamix Auto Fan Control plugin, and I would like to ask - can this plugin control multiple PWM controllers at once? I have my fans plugged into different pins on my motherboard, so they are independently controllable. Can the plugin modify the fan speed of all of these fans, or only one controller?

Link to comment
Hi all, I am new to using the Dynamix Auto Fan Control plugin, and I would like to ask - can this plugin control multiple PWM controllers at once? I have my fans plugged into different pins on my motherboard, so they are independently controllable. Can the plugin modify the fan speed of all of these fans, or only one controller?

1 input
Link to comment
I¬īm gonna apologize for my previous¬†language, was frustrated as hell!¬†
Min temp value does not matter what I set it to, min pwm does not matter what I set it to. 
If I set my fans 100% in bios, as soon as I "detect fan", and it detects it, my selected fan turns of. 
Does not matter what I set min temp or min pwm to, can not get selected fan to turn on again. 

Post the full output of sensors-detect
Link to comment
18 hours ago, BeardElk said:

I¬īm gonna apologize for my previous¬†language, was frustrated as hell!¬†
Min temp value does not matter what I set it to, min pwm does not matter what I set it to. 
If I set my fans 100% in bios, as soon as I "detect fan", and it detects it, my selected fan turns of. 
Does not matter what I set min temp or min pwm to, can not get selected fan to turn on again. 

I've looked through the source code for the Auto Fan Control plug-in and for some reason they turn off PWM functionality in the main loop and then turn it back on (they also assume two optional sysfs fan/pwm attributes always exist which prevents it from working with lots of configurations).  According to the sysfs docs when PWM is turned off the fan should go full speed but it's technically dependant on the actual chip controlling the PWM, so I wouldn't be surprised that because they turn off PWM momentarily it turns your fans off.  Unfortunately the way the plug-in is designed it will only work with a fairly limited number of configurations.  I've put in a bug report on their GitHub repo but I think the developers are not maintaining the code at all at this time.  I've thought about rewriting it to be more universal but honestly it's just easier and faster to write a script to manually control my fans directly since my configuration too doesn't work with the Auto Fan Control plug-in.

 

Harry

Edited by HarryMuscle
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

√ó
√ó
  • Create New...