On 3/16/2019 at 9:04 AM, DanielCoffey said:

It supports one fan channel, yes. Splitters are fine as long as they only return one PWM signal back to the motherboard.

 

Some of the cheap ones are simply 4-pin connectors chained one after another and they all share the same PWM signal line. It is usually advised that you find the PWM line and break it on the splitter upstream from the first fan so that only the first fan returns the PWM signal to the board. If yo udon't, the board can get confused as the tach signal looks noisy and it cannot read the correct speed.

I just installed this Akasa three-way splitter: http://www.akasa.com.tw/search.php?seed=AK-CB002

Worked very nicely and the pwm line is connected only to one of the fan headers.

 

I excluded my two M.2 cache drives from the monitor since they run much hotter than the front mounted HDDs. However autofan does not seem to work properly. It is logging the following:

Mar 21 22:49:33 TMS-740 ool www[7904]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start'
Mar 21 22:49:33 TMS-740 autofan: autofan process ID 23144 started, To terminate it, type: autofan -q 
Mar 21 22:49:33 TMS-740 autofan: autofan excluding drives nvme0n1,nvme1n1 from max temp calculations 
Mar 21 22:49:38 TMS-740 autofan: Highest disk temp is 45C, adjusting fan speed from: FULL (100% @ 2436rpm) to: 190 (74% @ 1904rpm)

At the same time all HDD's are below 38 and only the M.2 NVMEs are over 40. Even the NVMEs do no match that 45 when viewed through Unraid dashboard which is reporting 42. Is this a common issue or what could be the problem?

Do you have any unassigned drives? It looks like they are monitored but there is no way to exclude them. I had this issue and disconnecting an unassigned drive fixed it. 

This was a good guess; I had my old 2.5" cache SSD still connected. It did not show temperature in the dashboard so I did not even think about it. I disconnected it but still the same problem. Autofan is reporting way higher highest temperature what is shown for any hdd in the system (37 vs 45) and still also the nvme cache drives are not matching it (42 vs 45). But I think it could be the nvme cache drives, the Unraid dashboard must have some polling interval so the 42 vs 45 difference could be explained by that. I'll let it run for a bit longer and see if these values eventually become the same.

 

I guess using M.2 NVMEs are still pretty rare which could explain why no one else has ran into this. It would make debugging easier If the autofan logged the disk with the highest temperature.

 

Edit 23.3.2019 11:06 (GMT+2): I'm quite certain that the max temp is read from the cache nvme drives. The temps are now stabilised and the only drive with ~1C range from the one reported by autofan is my cache 1 nvme. So the nvme exclusion does not work correctly in autofan. I have now as workaround adjusted the high limit accordingly and hoping that there is sufficient correlation from the cache drive temp to the hdd drive temps.

Edited March 23, 20197 yr by henris

Are those of us on the stable release of unRaid missing any important updates with Dynamix System Statistics? You have it restrict to a release candidates atm.

Hi.

I'm on 6.6.7, latest plug-in.

Auto Fan doesn't exclude my cache drive.

It used to work, anyone else has this issue? Now my fan speed is always based on my "hot" nvme ssd.

tried restart, disable reanable, tick untick, etc. still. My highest temp (in the log) is always my nvme ssd temp

any ides?

 

thanks!

 

edit: I see other people have the same exact problem. On my previous server build, I did not have nvme cache, and it did work as advertised. It excluded my sata ssd cache drive.

I guess the nvme support is not great atm.

(I also have an unassigned drive, but it's 2,5", always spun down and its cooler then my array hdd's, so I don't think this is the issue)

Hopefully it will be fixed later.

Edited April 3, 20197 yr by LSL1337

Installing older version of the System Stats plugin which supports unRAID 6.6.x

I've got a really old version of system stats running and I'm unable to update it to the latest because the latest supports only 6.7.0rc. The following is relevant only if you are currently running a version older than 29.8.2018 and would like to update to latest 6.6.x compatible which is 29.8.2018 release.

 

There are several posts about this but no definitive answer yet. I dig around and found this post from Squid which says that simply copying the old versions of the plugins plg and txz files to correct folders on flash and then rebooting should work. Simply installing it with "plugin install ..." will not work since though pointing to an older version of the plg it will still try to download the latest txz.

 

Browsing the Bergmans Github for Dynamix V6 I found out that for each latest file version there are also all the previous versions available. Comparing history to System.Stats release notes, the last version supporting 6.6 is from 29.8.2018. So the links below are to that release.

 

So here it goes:

1. Download 29.8.2018 version plg file from here.
2. Copy the plg file to flash into folder /config/plugins
3. Download 29.8.2018 version txz file from here
4. Copy the txz file to flash into folder /config/plugins/dynamix.system.stats
5. Restart the server (no way around this)

 

Hope this helps.

Edited April 6, 20197 yr by henris

Just installed 6.7.0-rc7...  It has a blank button right next to the power button on the webui...  When pressed, this adds a "flyout" effect with nothing in it...  Removing the System Buttons plugin removes the button...

 

For the Fans plugin, is it limited to only PWM fans? No 3 pin?

@henris

Thanks for that post. Got me thinking about it and the last step - reboot the server?

I absolutely recommend rebooting your server instead of doing this but...

If you really can't reboot now and are willing to accept some possible weirdness (because we aren't going to install this quite like the script wants):

1. login to your server via bash shell

2. # cd /

3. # tar xf /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz

 

commands are after the # and don't blame me if you do this wrong - if/when you do - reboot.

1 hour ago, DazNick said:

Even though I always run/update the latest version of Unraid, I can never update the Dynamix System Statistics plugin.
My Unraid is Version: 6.6.7 Stable

Everytime I do it says:-

plugin: updating: dynamix.system.stats.plg
plugin: installed Unraid version is too low, require at least version 6.7.0-rc1

You have the latest version for the Stable  release Branch--- 6.6.7.  The updated version is only for the Next (Read, 'Beta') release Branch--- now 6.7.0-rc7.  I have the same issue on my Media server.  You will be able to update under two conditions.  (1) you change to the Next Branch or (2) 6.7.0 is released as the Stable Branch version. 

On 3/16/2019 at 3:04 AM, DanielCoffey said:

It supports one fan channel, yes. Splitters are fine as long as they only return one PWM signal back to the motherboard.

 

Some of the cheap ones are simply 4-pin connectors chained one after another and they all share the same PWM signal line. It is usually advised that you find the PWM line and break it on the splitter upstream from the first fan so that only the first fan returns the PWM signal to the board. If yo udon't, the board can get confused as the tach signal looks noisy and it cannot read the correct speed.

Hello ... As many here have said thanks for all your work ... i have been using you fan control from day on and loved it .. My server has gone down and forced to upgrad ( long story ) I  am running a Supermicro x9qr7-tf+ mother board now and i am having all kinds of probllems with the plugin sometimes it finds every thing and other times nothing. Nothing means hot cpu!

 

Dont need that ?;->> on and on i just removed it and seted it again and this is what i go .. Any thoughs ... 

 

Thanks John G.

 

errors are ( 

 

<br /><b>Warning</b>:  file_put_contents(): Only 0 of 1 bytes written, possibly out of free disk space 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(): Only 0 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>41</b><br /><br /><b>Warning</b>:  file_put_contents(): Only 0 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>44</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />

 

 

4 hours ago, John Graham said:

possibly out of free disk space in

These suggests you may have other problems.

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

4 hours ago, trurl said:

These suggests you may have other problems.

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

i played around some more and it looks like it is using a bad path

 

"/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002e/hwmon/hwmon5/fan1_input"

 

I search the system and this is all that i could find with fan1_inout >> i input this file and saved it but still not good

 

Thanks for your help

 

tower-diagnostics-20190415-1648.zip

Looks like you rebooted between this post and your last. What I was looking for in your diagnostics would have gone away with the reboot until it happened again. Specifically, I was looking to see if something had filled up rootfs. I don't know if there was anything to the idea or not.

When I removed the buttons it does not restore the placeholder at the top right back to before it was there.  The placeholder is still there for a button that was removed...

 

FYI

 

On 6/3/2018 at 3:18 AM, Auxilium said:

I and at least one more person have problem with System Temp,

sensors output:

root@SERVER:~# sensors
Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 12: Undeclared bus id referenced
sensors_init: Can't parse bus name

/etc/sensors.d/sensors.conf content:

# sensors
chip "nct7904-i2c-0-2d"
ignore "fan2"
chip "nct7904-i2c-0-2d"
ignore "fan4"
chip "nct7904-i2c-0-2d"
ignore "fan5"
chip "coretemp-isa-0000"
label "temp1" "CPU Temp"
chip "i350bb-pci-0500"
label "temp1" "MB Temp"
chip "nct7904-i2c-0-2d"
label "fan8" "Array Fan"

It is with SuperMicro X9DA7 motherboard, and also X9DRi-LN4F+ (the other person on DataHoarding Discord)

BLKMGK here have same problem: https://lime-technology.com/forums/topic/29533-dynamix-system-temp/?do=findComment&amp;comment=657577

 

According to https://linux.die.net/man/5/sensors3.conf

what is missing is bus statement,

in my case it's

bus "i2c-0" "SMBus I801 adapter at 9000"

 

 

After that everything works.

 

This literally saved me! Thanks!

 

Do you know if the CPU temp is combining CPU 1 and CPU 2 temps or is it something different?

Edited April 17, 20197 yr by Tech4KStudios

Is it Possible to install a previous version of AutoFan, before it had 'nvme support'? It just broke the functionality basicly for every nvme user

Edited April 19, 20197 yr by LSL1337

I dont know ,,, i would but up to try it ,,, i just tryed Dynamix System Temp with about the same outcome ,,, furst timw it worked but ever time after that it dose not work..?? i am lost. Might be my new setup but i dont thing so. the only thing i see is a comment about somthing call

"Dynamix webGui" searched for it but cant find it? I will send a screen dump of my screen. i have tryed un instaling and reinstalling still nothing

 

Thanls and dont get me wrong i am not bitching just trying out all the buttons ?;-{

 

Model: N/A
M/B: Micro-Star International Co., Ltd. - X470 GAMING PRO CARBON (MS-7B78)
CPU: AMD Ryzen 7 2700 Eight-Core @ 3200
HVM: Enabled
IOMMU: Enabled
Cache: 768 kB, 4096 kB, 16384 kB
Memory: 32 GB (max. installable capacity 256 GB)
Network: bond0: fault-tolerance (active-backup), mtu 1500 
 eth0: 1000 Mb/s, full duplex, mtu 1500
Kernel: Linux 4.18.20-unRAID x86_64
OpenSSL: 1.1.1a
Uptime: 3 days, 01:52:06

After installing and clicking on Detect, it does nothing. Is this still working on v6.6.7 or on amd chips?

Hello, I've been having a problem with all my disks spinning up for no apparent reason. I posted about it in the link below where it was suggested I try open files, active streams and file activity which lead to a dead end, nothing seemed to be opening. Then @nuhll suggested it was a possibly a problem with the Dynamix Cache Directories plugin. So I went to the settings of that, turned on help, and tried setting 'cache pressure of directories' to 1 as per the help (it was 10 by default), that still resulted in the same problem. So then I tried turning on /mnt/user/ caching (yes I saw the cpu warning), and that doesn't seem to have solved the problem either. What to try next? I've uploaded a diagnostics file.

 

zeus-diagnostics-20190426-1404.zip

@dgwharrison

I think to really test it, you should disable cache dirs completely. If the disks stop spinning up, it was the culprit, if not you will have to look further. Media serves like plex could also spinup disks, disable dockers and vms one by one, to test further. Also make sure you have not turned on turbo write mode in Settings -> Disk Settings, and look for Tunable (md_write_method). This would spinup all disks on every write if activated.

Edited April 26, 20197 yr by SlrG
typo

I have the same issues that out of my raid 2 out of 5 spin up for no reason.

 

In the hope to help.  The dockers that i am running are.

 

Plex, deluge, jackett, sonnar, Radarr.

 

With my testing i am leaning towards plex.

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)

Edited April 26, 20197 yr by nuhll

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. 

 

 

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.