Dynamix - V6 Plugins


bonienl

Recommended Posts

That's the acpitz - temp 3.   If nothing is listed in the Fan section, then sensors detect isn't picking up any valid sensors for it.  Not an uncommon problem, and unfortunately outside of bonienl's control.

Link to comment
On 6/6/2021 at 4:36 PM, spl147 said:

currently it only works if you have a single config file and a single controller! it's a known issue.

So if I understand correctly it will only work with one motherboard pwm header?? Since the nvme temps and the hdd temps are so different, I was planning to set one pwm header for hdd array temps and another one for nvme temps, so this mean I would not be able to do it?   

Link to comment
6 hours ago, Squid said:

That's the acpitz - temp 3.   If nothing is listed in the Fan section, then sensors detect isn't picking up any valid sensors for it.  Not an uncommon problem, and unfortunately outside of bonienl's control.

 

Got it. No big deal on the fans. CPU is most important which looks to work, so all good.

Do you mean acpitz - temp 3 is the motherboard temp?

Link to comment

In terms of the PWM detection and subsequently using auto fan app, I assume there's no driver available for the ITE chip that controls my fans? I'm using a relatively new motherboard (Gigabyte Aorus Pro B560M AX). Do you know if there is any workaround? From sensors-detect below..

 

Trying family `ITE'...                                      

Found unknown chip with ID 0x8689

Link to comment
In terms of the PWM detection and subsequently using auto fan app, I assume there's no driver available for the ITE chip that controls my fans? I'm using a relatively new motherboard (Gigabyte Aorus Pro B560M AX). Do you know if there is any workaround? From sensors-detect below..
 
Trying family `ITE'...                                      
Found unknown chip with ID 0x8689

Post the full output
Link to comment
1 hour ago, spl147 said:


Post the full output

 

Here is the full output, thanks for any help.

 

# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. B560M AORUS PRO AX [-CF]
# Kernel: 5.10.28-Unraid x86_64
# Processor: 11th Gen Intel(R) Core(TM) i5-11400 @ 2.60GHz (6/167/1)

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): YES
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...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
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): YES
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'...                                      No

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): YES
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): YES
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): YES
Found unknown SMBus adapter 8086:43a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x28
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM96080'...             No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Nuvoton NCT7802Y'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No


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

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

 

 

image.png.c0169aa92e5de176ec83bdd9217fb32d.png

 

image.thumb.png.19e99bb7b3d489b12e41c30759688288.png

Link to comment

Last time a saw this Error in my Syslog:

 

Sep  4 19:11:10 Unraid-1 nginx: 2021/09/04 19:11:10 [error] 27998#27998: *4810699 open() "/usr/local/emhttp/plugins/dynamix.system.stats/images/sys.png" failed (2: No such file or directory) while sending to client, client: 192.168.0.6, server: , request: "GET /plugins/dynamix.system.stats/images/sys.png HTTP/1.1", host: "192.168.0.50", referrer: "http://192.168.0.50/Stats"

 

This Error appears every time, i open the System Stats Tab.

Diagnostic attached.

 

unraid-1-diagnostics-20210904-1913.zip

Link to comment

hi i have a question regards plugin auto fan control, sorry if this has been asked before please feel free to ping me the link if it has, how do bios fan curves and the plugin interact?, does the auto fan control plugin take control or is there some sort of internal fight (assuming its set in the bios) between fan curves in the bios and auto fan control plugin?, is it good practise to disable any automatic ramp up/down fan settings in the bios?

  • Like 1
Link to comment
On 8/29/2021 at 7:57 PM, jayephx said:

In terms of the PWM detection and subsequently using auto fan app, I assume there's no driver available for the ITE chip that controls my fans? I'm using a relatively new motherboard (Gigabyte Aorus Pro B560M AX). Do you know if there is any workaround? From sensors-detect below..

 

Trying family `ITE'...                                      

Found unknown chip with ID 0x8689

worth a shot at these instructions, works for me and im on a fairly newish board (Asus ROG Strix x470-f Gaming):-

https://forums.unraid.net/topic/34889-dynamix-v6-plugins/page/102/?tab=comments#comment-789606

 

 

  • Thanks 1
Link to comment

Hi, I installed the system stats plugin a few days ago and the real time function works fine, but if I select last day or any other selection in the drop down I don't get anything displayed.

 

Do I need to carry out some additional work to get this historical data to show ?

 

Thanks!!

 

edit: I don't have a /var/log/sa folder, do I need to manually create that ?

Edited by fireplex
Link to comment
9 hours ago, IMTheNachoMan said:

Thank you for these plugins. Very helpful!

 

What is the "Users Names" tab for in "Active Streams"?

 

 

The plugin normally displays the smb user streaming, but the username is used to override based upon the IP name.

 

So, instead of something like "tammy" displaying, you can put in and have it display "My freeloading sister-in-law who thinks paying rent is beneath her"

 

Link to comment
10 hours ago, Squid said:

The plugin normally displays the smb user streaming, but the username is used to override based upon the IP name.

 

So, instead of something like "tammy" displaying, you can put in and have it display "My freeloading sister-in-law who thinks paying rent is beneath her"

 

 

Got it. Thank you!

Link to comment
On 9/6/2021 at 1:02 PM, binhex said:

hi i have a question regards plugin auto fan control, sorry if this has been asked before please feel free to ping me the link if it has, how do bios fan curves and the plugin interact?, does the auto fan control plugin take control or is there some sort of internal fight (assuming its set in the bios) between fan curves in the bios and auto fan control plugin?, is it good practise to disable any automatic ramp up/down fan settings in the bios?

 

Hello - I, too, wondered about this as well..  I also had a question about some of the settings.  

 

Should I just use all of the autodetected settings? I really shouldn't make any changes to it or...can I??

Link to comment

Hi,

I updated to S3 Sleep version 2021.03.13 and since then the server (unRAID 6.9.2) is no longer going to sleep automatically. I just enabled debug mode and hope to find something. Since the update is from March this year, I wonder if this is a known bug? It was working fine with the previous version without any issues and of course I did not changed anything in the plugins settings.

 

The "Sleep" button in the main tab is working and so far as I know the wakeup is also working.

 

Debug mode "Console" is bullshit - I figured out xD Hope I find something within the syslog these days.

Edited by cap089
Link to comment

Unraid crashed/became unresponsive when doing a Detect with the System Temp plugin - what do I do? I was in the middle of some Preclears with new disks, should I assume I have to start those over and force reboot the system or is there another way?

 

Edit: Ehh... rebooted and now a full parity check in process - not fun

Edited by Econaut
Link to comment
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. TUF GAMING B550M-PLUS (WI-FI)
# Kernel: 5.10.28-Unraid x86_64
# Processor: AMD Ryzen 7 5800X 8-Core Processor (25/33/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'...               Yes
Found `Nuvoton NCT6798D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
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'...                                      No

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): 

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: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively): 

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (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)

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9)

hi,there

it could not read the fan speed now,how should i do

Link to comment

Update: Found out that for whatever reason from now on at "Wait for array inactivity" the option "Yes, exclude cache" drive must be chosen otherwise the server is not going to sleep anymore. Before the update this option was not necessary as the cache drive is not permanently busy. Could not figured out which plugin/ docker instance is responsible for that.

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.