Dynamix - V6 Plugins


Recommended Posts

Also, if you're browsing your server with Windows and have the preview pane open in Explorer (or similar), that will spin drives up as it analyses what you're looking at.  Wouldn't spin all drives up in one hit, but a few minutes of browsing could trigger them all.  You may be aware of that (or it may be outdated, since I've turned all such views off), but just in case.

Link to comment
23 hours ago, nuhll said:

No, i dont mean that cache plugin is the problem, i just mean it should prevent that (because it caches directorys) but sometime its not good enaught (i dont know).

 

I had spinning up drives just from visiting and browser around on my client where links to the server were visisible - that was my hint. Like i had "Server" in my start menu (a link to //192.168..../some/thing/) which spun different drives up

 

At the end you can spot this issues with the open files plugins avaible (try different) (i saw acccesses to the directorys, so i knew it was the links)

Thanks @nuhll Actually I just uninstalled Dynamix Cache Directories just to see if that was the problem. It wasn't. So I guess I'll go back to the other thread. 

 

 

22 hours ago, emmcee said:

The Open Files plugin will show you which processes have open files. I found this very useful to track down why my disks were spinning up. 

 

 

Hi @emmcee, tried that many times, almost nothing open that's sitting directly on a disk, usually maybe 2 files on 2 disks but nothing on the rest. Most files are being read/written of the cache. 

 

22 hours ago, Cessquill said:

Also, if you're browsing your server with Windows and have the preview pane open in Explorer (or similar), that will spin drives up as it analyses what you're looking at.  Wouldn't spin all drives up in one hit, but a few minutes of browsing could trigger them all.  You may be aware of that (or it may be outdated, since I've turned all such views off), but just in case.

Hi @Cessquill, I have a Mac which I have an automouter on, I'll try disabling that and unmounting the server for a while.

Link to comment

I have tried Open Files, and I personal find that does not show me what files are being access when my Disk 2 and Disk 4 are spinning up.

I think I have tracked this down, and it is PLEX. I think it is when it does it automatic library scan.

 

also was on the topic. my Open Files plugin, is no shown on the Main page, and I have to go into the plugins tab and click on the application which gives me the following information.

 

Capture.thumb.JPG.00d645e74e53c9218be4da87a9935f5f.JPG

 

this is normal

 

Link to comment
9 hours ago, chris_netsmart said:

I have tried Open Files, and I personal find that does not show me what files are being access when my Disk 2 and Disk 4 are spinning up.

I think I have tracked this down, and it is PLEX. I think it is when it does it automatic library scan.

 

also was on the topic. my Open Files plugin, is no shown on the Main page, and I have to go into the plugins tab and click on the application which gives me the following information.

 

Capture.thumb.JPG.00d645e74e53c9218be4da87a9935f5f.JPG

 

this is normal

 

For me, it's not plex. I know that because if I start file activity spin down the array, clear stats, wait a minute I get this:

2019-04-28_09-28-10.thumb.png.77d2968207c9d7b6c45b92c9d40883c0.png

The one read of disk4 is a VM, yet all the disks are spun up for no reads or writes (aside form the vm).

Link to comment

hmm :(

 

I have same problem like last time, but even worser.

 

auto fan control cant find any PWM controller, i upgraded my server to the following board:

Z170 PRO GAMING Version 

 

Any idea?

 

root@Unraid-Server:~# pwmconfig
# pwmconfig revision $Revision$ ($Date$)
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 by nuhll
Link to comment

After upgrading my cache drive from 1.6tb Intel NVME to 3.8tb HGST NVME, fan auto control plugin is no longer ignoring NVME drive when calculating drive temp.

 

The new cache drive model is HGST N150 3800GB, and shows in Unraid dashboard as model UCSC-F-H38001.  Fans used to idle at 800rpm, now with min cache drive temp at 40C, a much louder 2000+rpm.

 

The new drive does run hot - 40C is after I switched pcie slots so open space next to drive heat sink, and also have 2000 rpm 12cm fan blowing directly down onto pcie slots.

 

I had a similar problem with plugin a couple of years ago, when NVME drives were newer, but something about this drive seems to be different, resulting in its temp not being ignored as configured.

 

Pics showing systemp temp/fan auto control settings, as well as drive status and log file.  Diagnostics attached.

 

Any help or suggestions appreciated, as this server used to be whisper-quiet except for parity checks!

 

 

drive status and log file.jpg

fan auto control.jpg

system temp.jpg

unraid-one-diagnostics-20190430-1146.zip

Link to comment

Dear all,

 

im realy stuck in the Fan Speed Plugin.

 

PWM controller is not found and at the same time i dont find temps of the Harddrives that are connected to the Mainbaord.

 

 

The Most weird thing is that i can access the Temps over the Main:

image.png.b12b67143cedf2b8db317991eae28a2f.png

 

I did run sensors-detect but it found a sensor on "ID 0x8686"

 

 


root@ben-server:/boot/config/plugins# sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Gigabyte Technology Co., Ltd. Z270P-D3 [Default string]
# Board: Gigabyte Technology Co., Ltd. Z270P-D3-CF
# Kernel: 4.18.20-unRAID x86_64
# Processor: Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz (6/158/9)

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 15h power sensors...                             No
AMD Family 16h power 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):
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 0x8686
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):
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):
Found unknown SMBus adapter 8086:a2a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at f040 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
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)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): no
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading i2c-dev... OK

 

The command:

 

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

 

or:

 

modprobe it87 force_id=0x8686

Did also not work...

 

Im not a linux pro so i hope for help.

 

The only thing that i got to work in System Temps is the CPU Core :

image.png.e12f6e3588caf8736e94c312b50b89b5.png

 

 

Hope for help

mfg Bengele

 


 

 

Link to comment

Can anyone respond as to status of Fan Auto Control?  Not sure if the "owner" is busy with other projects, or if plugin is no longer being supported/developed.  I consider it integral to the function of UnRaid - just as important as UPS, parity check, mover, etc.  Would be happy to help test any changes or donate funds to support current issues being addressed.

Link to comment

I am trying to troubleshoot an issue and need to remove all of my plugins to finish my diagnostics.  I have uninstalled the Dynamics System Info and Active Streams, but they have left behind two folders; dynamix and dynamix.kvm.manager.  No matter what I try to do I cannot delete these folders or any of their contents.

 

Does anyone know of a way to COMPLETELY remove these plugins from my system?  I am not very good with linux, so the easier the solution the better.

 

Thanks for your help.

Link to comment

Dynamix Stats seems to be pretty bugged on 6.7.0, for me it gives me error which makes duplicati hangs and I cannot shutdown my unraidserver but doing a power reset...

May 12 12:59:54 Tower nginx: 2019/05/12 12:59:54 [error] 8100#8100: *121517 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.5, server: , request: "POST /plugins/dynamix.system.stats/include/HardwareStats.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower:88", referrer: "http://tower:88/Stats""

 

Link to comment
3 hours ago, bonienl said:

This is not a plugin issue but a system issue.

First check your DNS settings. Next disable any adblockers and/or antivirus.

This is strange, I did not have this problem before I updated to 6.7.0... My DNS settings looks right and adblocker have never been an issue before. But I guess it's duplicati that mess up everything, trying to get borg working now instead...

Link to comment
6 hours ago, truckerCLOCK said:

Just updated to 6.7.0. Not able to monitor array temps. Mb and CPU show up fine. Using the coretemp nct6775 drivers. Revert back to 6.6.7 everything works fine.

Did you try going to the Settings for System Temps and make sure the sensors were still selected?

Link to comment
Just updated to 6.7.0. Not able to monitor array temps. Mb and CPU show up fine. Using the coretemp nct6775 drivers. Revert back to 6.6.7 everything works fine.


I’ve had the same problem with the nct6775 driver since upgrading to 6.7.0.


Sent from my iPhone using Tapatalk
Link to comment
On 5/4/2019 at 5:44 PM, bengele said:

Dear all,

 

im realy stuck in the Fan Speed Plugin.

 

PWM controller is not found and at the same time i dont find temps of the Harddrives that are connected to the Mainbaord.

 

 

The Most weird thing is that i can access the Temps over the Main:

image.png.b12b67143cedf2b8db317991eae28a2f.png

 

I did run sensors-detect but it found a sensor on "ID 0x8686"

 

 



root@ben-server:/boot/config/plugins# sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Gigabyte Technology Co., Ltd. Z270P-D3 [Default string]
# Board: Gigabyte Technology Co., Ltd. Z270P-D3-CF
# Kernel: 4.18.20-unRAID x86_64
# Processor: Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz (6/158/9)

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 15h power sensors...                             No
AMD Family 16h power 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):
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 0x8686
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):
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):
Found unknown SMBus adapter 8086:a2a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at f040 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
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)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): no
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading i2c-dev... OK

 

The command:

 


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

 

or:

 


modprobe it87 force_id=0x8686

Did also not work...

 

Im not a linux pro so i hope for help.

 

The only thing that i got to work in System Temps is the CPU Core :

image.png.e12f6e3588caf8736e94c312b50b89b5.png

 

 

Hope for help

mfg Bengele

 


 

 

 

Did this happen after you updated to 6.7.0? 

Link to comment
On 5/14/2019 at 4:39 AM, trurl said:

Did you try going to the Settings for System Temps and make sure the sensors were still selected?

Yup. How could they change? Update to 6.7.0. nothing changes, settings still the same. No array temps. Shows "not used". Revert back to 6.6.7. temps show back up. Works fine. Update again to 6.7.0. No array temps. Shows "not used".  Checked Nerd pack for updates. I'd say it's a problem with the plug in and makes fan auto control not work. 

Edited by truckerCLOCK
meowther
Link to comment

Just checking in to keep hope alive on update to AutoFan Speed plugin.  Ongoing issue with NVME drive temps not being ignored, even if checking in setup dialog.  Results in fan speeds (and noise levels) much higher than needed, and WAF being much lower than desired ;)

 

Details here:  

 

 

I realize that the plugins are supported in the free time of talented and generous community members, and they are very much appreciated.  In that same spirit of generosity, some communication regarding future direction of plugin would be helpful.

 

If this is the wrong channel to reach the right people, please redirect as needed.

Link to comment

upgraded from 6.5.3 to 6.7.0, using S3_Sleep_Plugin  version 3.0.6.1

 

The server goes to sleep just fine, but will not respond to WOL requests anymore.

WOL flag is set to "g" only (realtek NIC)...actually can't remember if there was something different in it for unraid 6.5.3...it just used to work for "ages"...last downtime was 300+days ago ;-)

 

Edit: just checked and the NIC seems to be powered down completely upon sleep...no lights visible from the outside at the connector

Edited by Ford Prefect
Link to comment
On 5/19/2019 at 1:26 AM, poto2 said:

Just checking in to keep hope alive on update to AutoFan Speed plugin.  Ongoing issue with NVME drive temps not being ignored, even if checking in setup dialog.  Results in fan speeds (and noise levels) much higher than needed, and WAF being much lower than desired ;)

 

Details here:  

 

 

I realize that the plugins are supported in the free time of talented and generous community members, and they are very much appreciated.  In that same spirit of generosity, some communication regarding future direction of plugin would be helpful.

 

If this is the wrong channel to reach the right people, please redirect as needed.

same boat.

older versions didn't have nvme support, so i guess it would solve the problem.

any way to downgrade to the older version of the plug-in?

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.