Dynamix - V6 Plugins

[nearcatch]

22 hours ago, David Bott said:

Thanks...Ok, did that...Bummer, even after a restart and a rescan, no changes,  Still can not see the fans.  System temp readings seems to the be the same and the only items I can see.  

 

 

Don't know what else to do. After I installed the IT87 plugin (and maybe after unloading drivers and re-detecting/re-saving, I don't remember), my plugin looks like this, and I haven't had to do anything else since then, even after reboots:

[Ecsport108]

Hello all,

 

I am having similar issues to Hasown above with a Gigabyte W480 Vision W motherboard with three system fans installed (not including CPU cooler). When the IT87 plugin is not installed, I get three fans listed in both the System Temp and Fan Auto Control plugins appearing as it8792. If I install the IT87 plugin multiple new it8688 entries, including those for fan headers not currently populated, appear just as in the screenshot above. Even with the IT87 plugin installed, System Temp seems to only list speeds next to the it8792 entries anyways so I have uninstalled the IT87 plugin for now. My CPU fan only appears with the IT87 plugin installed, but I don't want to control it with the Fan Auto Control plugin regardless. I have enabled fan control on all three it8792 PWM controllers and the Fan Auto Control plugin is able to detect a fan on each controller, albeit intermittently. However, when I go to detect the minimum PWM value, I hear the fans physically changing speeds but a value never populates the box and the speed control doesn't appear to be working correctly. I have tried putting multiple random numbers in the "Minimum PWM Value" box but it does not seem to affect anything. Here are some lines from my log that show the plugin appearing to adjust the PWM value but the RPMs stay constant. Does anyone have any ideas on how to fix this, I am going deaf from these 80mm server fans and the motherboard's BIOS fan controls only allow me to bring them down to 70% speed.

 

Oct 13 16:25:53 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm)
Oct 13 16:25:53 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3229rpm) to: 88 (34% @ 3229rpm)
Oct 13 16:26:09 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3040rpm) to: 88 (34% @ 3040rpm)
Oct 13 16:26:59 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm)
Oct 13 16:26:59 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3245rpm) to: 88 (34% @ 3229rpm)
Oct 13 16:28:05 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm)
Oct 13 16:28:05 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3245rpm) to: 88 (34% @ 3229rpm)
Oct 13 16:29:11 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3125rpm)
Oct 13 16:29:11 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3245rpm) to: 88 (34% @ 3229rpm)
Oct 13 16:30:17 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3110rpm) to: 88 (34% @ 3110rpm)
Oct 13 16:30:17 NASNAME autofan: Highest disk temp is 36C, adjusting fan speed from: 112 (43% @ 3214rpm) to: 88 (34% @ 3229rpm)

 

[Bob_C]

Dynamix S3 Plugin - Activity Monitor not working for ports other than 22

 

I recently changed the unraid default SSH port from 22 to a higher port for security reasons.  Since doing that, if I am logged in to unraid via SSH, the S3 plugin does not find any active connection and executes a shutdown.  Changing default port back to 22 and it works again.

[Bob_C]

On 6/14/2021 at 2:03 PM, SimoneM1988 said:

I installed dynamix S3 sleep and it worked without problems for a few days, suddenly both the programming and the home button stopped working. If I click on the button on the home page, the confirmation menu no longer appears,

"System in sleep mode" appears at the bottom next to the array status,

but after a few seconds the page reloads and everything remains as before.

I tried to put it to sleep from the command line with

echo -n mem> / sys / power / state

but the result is

bash: echo: write error: Device or resource busy

If I do

cat / sys / power / state

the result is

freeze mem

as if the sleep had disappeared

 Since the upgrade to 6.11.1 I am experiencing the exact same issue.  Was there a solution to this?

[BreakfastPurrito]

Is there a way to label these fans anything other than Fan X? I want to label them something like Case Fan, CPU Fan, etc.

 

[alturismo]

16 hours ago, BreakfastPurrito said:

Is there a way to label these fans anything other than Fan X? I want to label them something like Case Fan, CPU Fan, etc.

 

custom theme, rewrite through CSS

 

sample (sadly i couldnt find anything due +10 fans, fan10 == fan1, etc ...)

 

[BreakfastPurrito]

4 hours ago, alturismo said:

custom theme, rewrite through CSS

 

sample (sadly i couldnt find anything due +10 fans, fan10 == fan1, etc ...)

 

I have no idea how to do that. Is there a tutorial somewhere?

[alturismo]

8 hours ago, BreakfastPurrito said:

I have no idea how to do that. Is there a tutorial somewhere?

 

 

</style>

<script type="text/javascript">
document.addEventListener("DOMContentLoaded", function() {
    $( ".fan_view td:contains('FAN 0')" ).text("PUMP AC Eisbaer HPE");
    $( ".fan_view td:contains('FAN 1')" ).text("VRM (1x 35)");
    $( ".fan_view td:contains('FAN 2')" ).text("HDD Case (4x 80)");
    $( ".fan_view td:contains('FAN 3')" ).text("PUMP AC Eiswolf II");
    $( ".fan_view td:contains('FAN 4')" ).text("UNUSED");
    $( ".fan_view td:contains('FAN 5')" ).text("Eisbaer HPE (3x 120)");
    $( ".fan_view td:contains('FAN 6')" ).text("Eiswolf II (3x 120)");
    $( ".fan_view td:contains('FAN 7')" ).text("UNUSED");
    $( ".fan_view td:contains('FAN 8')" ).text("Front Case (3x 120)");
    $( ".fan_view td:contains('FAN 9')" ).text("MOS (1x 35)");
    $( ".fan_view td:contains('FAN 10')" ).text("VRM (1x 35)");
});
</script>

<style>

 

little trial & error

 

sadly i didnt manage to get FAN1 as unused (as its then also recognized in FAN10) as my java script knowledge's are not existent

 

[BreakfastPurrito]

4 hours ago, alturismo said:

 

 

</style>

<script type="text/javascript">
document.addEventListener("DOMContentLoaded", function() {
    $( ".fan_view td:contains('FAN 0')" ).text("PUMP AC Eisbaer HPE");
    $( ".fan_view td:contains('FAN 1')" ).text("VRM (1x 35)");
    $( ".fan_view td:contains('FAN 2')" ).text("HDD Case (4x 80)");
    $( ".fan_view td:contains('FAN 3')" ).text("PUMP AC Eiswolf II");
    $( ".fan_view td:contains('FAN 4')" ).text("UNUSED");
    $( ".fan_view td:contains('FAN 5')" ).text("Eisbaer HPE (3x 120)");
    $( ".fan_view td:contains('FAN 6')" ).text("Eiswolf II (3x 120)");
    $( ".fan_view td:contains('FAN 7')" ).text("UNUSED");
    $( ".fan_view td:contains('FAN 8')" ).text("Front Case (3x 120)");
    $( ".fan_view td:contains('FAN 9')" ).text("MOS (1x 35)");
    $( ".fan_view td:contains('FAN 10')" ).text("VRM (1x 35)");
});
</script>

<style>

 

little trial & error

 

sadly i didnt manage to get FAN1 as unused (as its then also recognized in FAN10) as my java script knowledge's are not existent

 

Omg it works! Thanks so much!

[nearcatch]

On 10/21/2022 at 12:17 PM, alturismo said:

little trial & error

 

sadly i didnt manage to get FAN1 as unused (as its then also recognized in FAN10) as my java script knowledge's are not existent

 

something like this should work even when you want FAN1 to be different from FAN10. I don't have 10 fans so I can't test it and confirm. @BreakfastPurrito

 

EDIT: go to this post for the code

Edited October 25, 2022 by hasown

[alturismo]

7 minutes ago, hasown said:

something like this might work even for FAN1 being different from FAN10. I don't have 10 fans so I can't confirm.

thanks for the hint, but nope, doesnt work

 

[nearcatch]

18 minutes ago, alturismo said:

thanks for the hint, but nope, doesnt work

 

This works for me. You need the style tags to trick Theme Engine into inserting custom javascript this way. Probably a security hole, tbh. You could also use a browser extension like Violentmonkey or Tampermonkey to load it as a userscript.

 

 

</style>
<script type="text/javascript">
  document.addEventListener("DOMContentLoaded", () => {
    let fansTds = document.querySelectorAll(".fan_view td");
    let fansTdsArray = Array.from(fansTds);
    for (const td of fansTdsArray) {
      switch (td.innerText) {
        case "FAN 0":
          td.innerText = "fan0name";
          break;
        case "FAN 1":
          td.innerText = "fan1name";
          break;
        case "FAN 2":
          td.innerText = "fan2name";
          break;
        case "FAN 3":
          td.innerText = "fan3name";
          break;
        case "FAN 4":
          td.innerText = "fan4name";
          break;
        case "FAN 5":
          td.innerText = "fan5name";
          break;
        case "FAN 6":
          td.innerText = "fan6name";
          break;
        case "FAN 7":
          td.innerText = "fan7name";
          break;
        case "FAN 8":
          td.innerText = "fan8name";
          break;
        case "FAN 9":
          td.innerText = "fan9name";
          break;
        case "FAN 10":
          td.innerText = "fan10name";
          break;
        default:
          break;
      }
    }
  });
</script>
<style>

Edited October 22, 2022 by hasown

[alturismo]

there we go now  thanks alot 

 

[JBCn1]

Help: Auto fan pluign and driver for Asus PRIME B450M-A

 

I can't find a PWM controller, and I can't figure out why. System temp plugin uses k10temp driver and it finds my temp, but only for CPU and MB - I dont have any more.

I guess that its becaurse off incorrect driver, but I can't figure out how to find the right ones. Anyone can help?

 

 

 

[hispeedsurfer]

On 9/7/2018 at 6:17 PM, Squid said:

@bonienl  Can you add in to autofan an option to disable logging (preferably disabled by default).  Don't think it's really necessary to have it spam logs every 5 minutes with this

 

+1

[jojo345]

Dynamics S3 sleep

 

Hi, since update to 6.11.1 my system shuts down while parity check. Didn`t change anything on the settings, system update only.

 

Somebody knows if this is a known problem?

[Squid]

2 hours ago, jojo345 said:

Hi, since update to 6.11.1 my system shuts down while parity check. Didn`t change anything on the settings, system update only.

 

When you turn the system back on does it do a parity check due to an unclean shutdown? 

[jojo345]

Hi, thanks for answering.

 

No, it does not continue with the parity check. It only says "parity check canceled". There is a propper shutdown. No errors in the log.

It looks like the addon does not recognise the array working anymore.

 

Tested now with other settings: included all the discs on "Monitor discs outside array"

and it seems to work like this.

 

After the array check I will do some more testings.

 

-----------------------------------------------------------------------------

edit:

-------

@Squid

when I uncheck the discs on "Monitor discs outside array"

syslog shows:

Spoiler

Oct 27 15:00:10 UnRaidNAS1 s3_sleep: included disks=
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: ----------------------------------------------
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: s3_sleep process ID 2887 started, To terminate it, type: s3_sleep -q
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: All monitored HDDs are spun down
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: Extra delay period running: 60 minute(s)
Oct 27 15:01:10 UnRaidNAS1 s3_sleep: All monitored HDDs are spun down
Oct 27 15:01:10 UnRaidNAS1 s3_sleep: Extra delay period running: 59 minute(s)

with included discs:

Spoiler

Oct 27 15:01:14 UnRaidNAS1 s3_sleep: included disks=sdb sdc sdd sde sdf sdg
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: excluded disks=sda
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: ----------------------------------------------
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: s3_sleep process ID 4169 started, To terminate it, type: s3_sleep -q
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: Disk activity on going: sdb
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: Disk activity detected. Reset timers.
Oct 27 15:02:14 UnRaidNAS1 s3_sleep: Disk activity on going: sdb

So there seems to be no active discs detected while parity check.

Edited October 27, 2022 by jojo345

[ProphetSe7en]

Trying to figure out if anything has changed since last time I tried to get system temp and fan auto control to work.

I have a MSI Z590 Torpedo motherboard. 

 

From my understanding I need to use these drivers, but not sure how to get it done. Do I need to edit any files? Do I install something manually etc?

 

modprobe nct6683 force_id=0xd592

[jojo345]

On 10/27/2022 at 2:37 PM, jojo345 said:

Hi, thanks for answering.

 

No, it does not continue with the parity check. It only says "parity check canceled". There is a propper shutdown. No errors in the log.

It looks like the addon does not recognise the array working anymore.

 

Tested now with other settings: included all the discs on "Monitor discs outside array"

and it seems to work like this.

 

After the array check I will do some more testings.

 

-----------------------------------------------------------------------------

edit:

-------

@Squid

when I uncheck the discs on "Monitor discs outside array"

syslog shows:

  Reveal hidden contents

Oct 27 15:00:10 UnRaidNAS1 s3_sleep: included disks=
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: ----------------------------------------------
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: s3_sleep process ID 2887 started, To terminate it, type: s3_sleep -q
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: All monitored HDDs are spun down
Oct 27 15:00:10 UnRaidNAS1 s3_sleep: Extra delay period running: 60 minute(s)
Oct 27 15:01:10 UnRaidNAS1 s3_sleep: All monitored HDDs are spun down
Oct 27 15:01:10 UnRaidNAS1 s3_sleep: Extra delay period running: 59 minute(s)

with included discs:

  Reveal hidden contents

Oct 27 15:01:14 UnRaidNAS1 s3_sleep: included disks=sdb sdc sdd sde sdf sdg
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: excluded disks=sda
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: ----------------------------------------------
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: s3_sleep process ID 4169 started, To terminate it, type: s3_sleep -q
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: Disk activity on going: sdb
Oct 27 15:01:14 UnRaidNAS1 s3_sleep: Disk activity detected. Reset timers.
Oct 27 15:02:14 UnRaidNAS1 s3_sleep: Disk activity on going: sdb

So there seems to be no active discs detected while parity check.

So this is really the solution? 🙄

 

[Zonediver]

17 hours ago, jojo345 said:

So this is really the solution? 🙄

 

Have you tried it?

Here is the last screen...

And yes, it is still vice versa - the developer did not correct this... Last Update: 13.03.2021

It seems, the development of this plugin is dead...

 

Edited October 29, 2022 by Zonediver

[jojo345]

2 hours ago, Zonediver said:

It seems, the development of this plugin is dead...

Don`t hope so...

[LMD]

I moved my system from an Intel platform (Z170 Chip) to AMD X570S, but with that my fan's ain't visible anymore.

I tried the ITE IT87 Driver plugin, but without luck.

 

The motherboard i moved to is the Gigabyte X570S AERO G

 

Sensors and sensors-detect:

root@Mindfix4:~# sensors
nvme-pci-0400
Adapter: PCI adapter
Composite:    +48.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +48.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +56.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
MB Temp:      +16.8°C  (crit = +20.8°C)

nvme-pci-0100
Adapter: PCI adapter
Composite:    +38.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +38.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +42.9°C  (low  = -273.1°C, high = +65261.8°C)

k10temp-pci-00c3
Adapter: PCI adapter
CPU Temp:     +45.6°C
Tccd1:        +36.5°C
Tccd2:        +35.0°C

root@Mindfix4:~# sensors-detect
# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. X570S AERO G [-CF]
# Kernel: 5.19.14-Unraid x86_64
# Processor: AMD Ryzen 9 3900X 12-Core Processor (23/113/0)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8695

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.

Next adapter: NVIDIA i2c adapter 4 at b:00.0 (i2c-0)
Do you want to scan it? (yes/NO/selectively):

Next adapter: NVIDIA i2c adapter 6 at b:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively):

Next adapter: NVIDIA i2c adapter 7 at b:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively):


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

 

Seems the following chip ID's are in the need of a driver;

Found unknown chip with ID 0x8689

Found unknown chip with ID 0x8695

 

Google didn't give a good direction on which "Super IO Sensors" it are and I have no idea if there is a plugin that would help with Unraid for this.

 

So is there anybody that could help me out with this?

 

 

[Jammy B]

Dynamix S3 Sleep

 

running latest stable unraid.

 

Can someone help me please?

 

i've setup S3 Sleep and so far was working fine.

 

but now it seems to ignore its own rules and turns itself off.

 

by that, i have it set to switch off from midnight onwards. typically it might stay on till around 1am then switch off due to activity on the server.

 

now it switches off bang on 12:10am every night [as the 10 minutes is the "extra delay" set on the plugin]

 

it aborted my parity check to switch itself off last night.

 

if people are watching Plex, it switches itself off.

 

it didn't do this before.

 

i attach a screenshot of my settings in hope that someone tells me i've ticked something!

Edited November 2, 2022 by Jammy B

[jojo345]

Since some time it`s not 100% working anymore. It does not detect array. You can add all your array discs to " monitor discs outside array" and it will work.