Dynamix - V6 Plugins

PeterB · December 15, 2015

Uninstall/re-install seems to have fixed it.

... but after another reboot (powercut), it has gone wrong again!

I cannot understand why this has suddenly started happening.

Looking at the contents of my flash drive, the only thing I can see which might be a little bit odd is that the Extra directory contains both dynamix.system.autofan.txz and dynamix.system.autofan2.txz - should those archives be present?

Also in the Extra directory I have a dynamix.hot.fix-2015.12.02.txz and a dynamix.smart.update-2015.12.03.txz. I don't recall placing any of those files there, so I guess that it has been done automatically.

While looking at this, I notice that I still have:

# modprobe for each sensor
modprobe ipmi-si
modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s

in my go file. Are these still required, or should they be removed?

Medwynd · December 15, 2015

Using a X10SL7-F with 4 PWM fans I wanted to spin down to reasonable speeds.

Installed the autofan plugin and it fails to detect any pwm controllers.

If I set the plugin to enabled and click apply I get this error:

awk: fatal: cannot open file '/boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.cfg' for readin (No such file or directory)

I'm assuming this file would be created after I set some settings so may not be as fatal as it sounds. But what I can't figure out is why it's not seeing my motherboard fan controllers.

EDIT:

This is what IPMI is reporting:

Name Status Reading

CPU Temp Normal 29 degrees C

System Temp Normal 31 degrees C

Peripheral Temp Normal 32 degrees C

PCH Temp Normal 39 degrees C

VRM Temp Normal 33 degrees C

DIMMA1 Temp N/A Not Present!

DIMMA2 Temp Normal 27 degrees C

DIMMB1 Temp N/A Not Present!

DIMMB2 Temp Normal 27 degrees C

FAN1 Lower Critical 400 R.P.M

FAN2 Normal 1700 R.P.M

FAN3 Normal 1900 R.P.M

FAN4 Normal 1600 R.P.M

FANA Normal 2800 R.P.M

According to the motherboard manual there should be a H/W (Hardware) Monitor option in the bios but there does not appear to be. I do not know if it is just for display or for setting configurations.

Via IPMI I have the fan mode set to "Standard Speed"

I may have stumbled onto the problem:

I noticed a post that stated that BMC has a threshold limit for the fans at 600rpm. If the fans go below 600rpm, it considers that there's a fault and will spin them back at full speed. Now I just need to verify this but it does match my conditions, then figure out how to solve it.

bonienl · December 15, 2015

Uninstall/re-install seems to have fixed it.

... but after another reboot (powercut), it has gone wrong again!

I cannot understand why this has suddenly started happening.

Looking at the contents of my flash drive, the only thing I can see which might be a little bit odd is that the Extra directory contains both dynamix.system.autofan.txz and dynamix.system.autofan2.txz - should those archives be present?

Also in the Extra directory I have a dynamix.hot.fix-2015.12.02.txz and a dynamix.smart.update-2015.12.03.txz. I don't recall placing any of those files there, so I guess that it has been done automatically.

While looking at this, I notice that I still have:
# modprobe for each sensor
modprobe ipmi-si
modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s
in my go file. Are these still required, or should they be removed?

Ideally there are NO packages in the extra folder. You need to delete any autofan packages in there (the plugin never installs in that folder).

The hotfix and smartupdate packages are a temporary measure until the next unRAID version is released, keep in mind that these need to be deleted in the future as well.

You can keep the entries in your go file, these load the necessary drivers for your motherboard. Though the last line /usr/bin/sensors -s isn't really needed.

bonienl · December 15, 2015

Using a X10SL7-F with 4 PWM fans I wanted to spin down to reasonable speeds.

Installed the autofan plugin and it fails to detect any pwm controllers.

If I set the plugin to enabled and click apply I get this error:

awk: fatal: cannot open file '/boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.cfg' for readin (No such file or directory)

I'm assuming this file would be created after I set some settings so may not be as fatal as it sounds. But what I can't figure out is why it's not seeing my motherboard fan controllers.

EDIT:

This is what IPMI is reporting:

Name Status Reading

CPU Temp Normal 29 degrees C

System Temp Normal 31 degrees C

Peripheral Temp Normal 32 degrees C

PCH Temp Normal 39 degrees C

VRM Temp Normal 33 degrees C

DIMMA1 Temp N/A Not Present!

DIMMA2 Temp Normal 27 degrees C

DIMMB1 Temp N/A Not Present!

DIMMB2 Temp Normal 27 degrees C

FAN1 Lower Critical 400 R.P.M

FAN2 Normal 1700 R.P.M

FAN3 Normal 1900 R.P.M

FAN4 Normal 1600 R.P.M

FANA Normal 2800 R.P.M

According to the motherboard manual there should be a H/W (Hardware) Monitor option in the bios but there does not appear to be. I do not know if it is just for display or for setting configurations.

Via IPMI I have the fan mode set to "Standard Speed"

You probably need to install additional drivers to support your motherboard. Perhaps the easiest way is to use the system temp plugin, this will do a scan and allows installation of additional drivers, it has found. You need to install the 'perl' package separately to use system temp's detection function though.

Medwynd · December 15, 2015

You probably need to install additional drivers to support your motherboard. Perhaps the easiest way is to use the system temp plugin, this will do a scan and allows installation of additional drivers, it has found. You need to install the 'perl' package separately to use system temp's detection function though.

I was just looking into that. Now to figure out how to install the perl package

bonienl · December 15, 2015

You probably need to install additional drivers to support your motherboard. Perhaps the easiest way is to use the system temp plugin, this will do a scan and allows installation of additional drivers, it has found. You need to install the 'perl' package separately to use system temp's detection function though.

I was just looking into that. Now to figure out how to install the perl package

You can download the perl package from a slackware repository, this link is a direct download

Put the .txz file in the folder /extra on your flash device and it will be automatically installed upon each system start.

To do a manual installation, type:

installpkg /boot/extra/perl-5.18.1-x86_64-1.txz

SpaceInvaderOne · December 15, 2015

yes. And after you have installed the perl and detected which driver for the sensors for your motherboad, you can delete the perl package from unraid as it is only needed to detect which driver is used not to run the sys temp plugin etc.

itimpi · December 15, 2015

I was just looking into that. Now to figure out how to install the perl package

The easiest way is to install the Nerd Tools plugin (Perl was recently added). Also added recently is an option under Settings to select which of the tools in the Nerd Tools plugin should be installed on each boot.

bonienl · December 15, 2015

True, you can delete the perl package afterwards as it isn't needed to run the system temp plugin, but I find it handy to keep it. Ultimately anyone can choose what fits best

PeterB · December 15, 2015

Ideally there are NO packages in the extra folder. You need to delete any autofan packages in there (the plugin never installs in that folder).

Strange! I can't think that I would have put them there. I was using fanspeed control for some years, long before you adopted it as a dynamix plugin, and I could well have put original packages in Extra - but those are both named 'dynamix...'. The last access dates on the files are February 5, 2015. They haven't been interfering with the operation of autofan until last weekend.

The hotfix and smartupdate packages are a temporary measure until the next unRAID version is released, keep in mind that these need to be deleted in the future as well.

You can keep the entries in your go file, these load the necessary drivers for your motherboard. Though the last line /usr/bin/sensors -s isn't really needed.

Thanks for the advice.

trurl · December 15, 2015

You probably need to install additional drivers to support your motherboard. Perhaps the easiest way is to use the system temp plugin, this will do a scan and allows installation of additional drivers, it has found. You need to install the 'perl' package separately to use system temp's detection function though.

I was just looking into that. Now to figure out how to install the perl package

perl is now included in NerdPack (though not currently mentioned in the first post of that thread)

Msan · December 17, 2015

Would it be possible to show mounted drives that are not part of the array in the stats plugin?

bonienl · December 17, 2015

Would it be possible to show mounted drives that are not part of the array in the stats plugin?

The disk I/O activity under system stats includes all disks present in the system. The Disk stats only show the disks known to unRAID (=are part of the array).

dlandon · December 17, 2015

There is a new version of Dynamix Cache Dirs with a V6 only cache_dirs script. There was some left over code from the V5 days that is no longer applicable to V6. The two parameters that have been removed are:

'w' - wait for array to come on line. This does not apply to V6 because of the 'disks_mounted' event that starts cache_dirs. This guarantees that the array is started and online.
'b' or 'B' - force disks busy. This does not apply to V6 because of the 'stopping_svcs' event that stops cache_dirs. This guarantees that cache_dirs stops its 'find' processes and does not try to access the disks further to allow the array to stop.

When cache_dirs was installed in the 'go' file, it managed these events itself by using the code that has been removed. Now that these events are managed by the plugin, they are no longer needed.

The setting of these two parameters has been removed from the gui.

There were no code changes other than removing the code for the above two parameters. The cache_dirs script was modified for readability.

wirenut · December 18, 2015

trying to update cache directories I get this:

plugin: updating: dynamix.cache.dirs.plg

cache_dirs not running!

plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.cache.dirs.txz ... done

plugin: bad file MD5: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs.txz

bonienl · December 18, 2015

trying to update cache directories I get this:

plugin: updating: dynamix.cache.dirs.plg

cache_dirs not running!

plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.cache.dirs.txz ... done

plugin: bad file MD5: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs.txz

Your download is corrupted. You need to redownload. To be on the safe side, delete the existing .txz file on your flash disk under config/plugins/dynamix.cache.dirs.

dlandon · December 19, 2015

Stats not working after update to 2015.12.19. I get the following on the console:

Cannot find the data collector (sadc)

exec: No such file or directory

Invalid data format

and the "System Stats" are not working.

bonienl · December 19, 2015

Stats not working after update to 2015.12.19. I get the following on the console:

Cannot find the data collector (sadc)

exec: No such file or directory

Invalid data format

and the "System Stats" are not working.

Boy, you are fast

I think you downloaded an "intermediate" version which I needed to correct afterwards. You need to uninstall the existing version and re-install using the URL.

https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg

dlandon · December 19, 2015

Stats not working after update to 2015.12.19. I get the following on the console:

Cannot find the data collector (sadc)

exec: No such file or directory

Invalid data format

and the "System Stats" are not working.

Boy, you are fast

I think you downloaded an "intermediate" version which I needed to correct afterwards. You need to uninstall the existing version and re-install using the URL.
https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg

I was just there updating ca and did a quick check and caught it. Sorry to be so fast.

dlandon · December 19, 2015

Stats not working after update to 2015.12.19. I get the following on the console:

Cannot find the data collector (sadc)

exec: No such file or directory

Invalid data format

and the "System Stats" are not working.

Boy, you are fast

I think you downloaded an "intermediate" version which I needed to correct afterwards. You need to uninstall the existing version and re-install using the URL.
https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg

Still no go.

bonienl · December 19, 2015

What is the output of the command below on your system:

# ls -l /usr/local/emhttp/plugins/dynamix.system.stats/scripts
total 4
-rwxrwxrwx 1 root root 1895 Dec 19 03:09 sa1

dlandon · December 19, 2015

What is the output of the command below on your system:
# ls -l /usr/local/emhttp/plugins/dynamix.system.stats/scripts
total 4
-rwxrwxrwx 1 root root 1895 Dec 19 03:09 sa1

total 4

-rwxrwxrwx 1 root root 1895 Dec 18 21:09 sa1*

bonienl · December 19, 2015

I just uninstalled mine and did a fresh install from the URL, and all is happily working, so I am not sure what went wrong at your side.

Do you still see some console messages which may give a clue?

Log files should now be stored in /var/sa, you may want to check that folder.

dlandon · December 19, 2015

What is the output of the command below on your system:
# ls -l /usr/local/emhttp/plugins/dynamix.system.stats/scripts
total 4
-rwxrwxrwx 1 root root 1895 Dec 19 03:09 sa1
total 4

-rwxrwxrwx 1 root root 1895 Dec 18 21:09 sa1*

Should the sa1 script be dated the 19th?

dlandon · December 19, 2015

I just uninstalled mine and did a fresh install from the URL, and all is happily working, so I am not sure what went wrong at your side.

Do you still see some console messages which may give a clue?

Log files should now be stored in /var/sa, you may want to check that folder.

Log files are stored in /var/sa. No /var/logs/sa files.

Uninstall:

plugin: removing: dynamix.system.stats.plg

Removing package /var/log/packages/dynamix.system.stats...
Removing files:
--> Deleting /usr/bin/sadf
--> Deleting /usr/bin/sar
--> Deleting /usr/lib64/sa/sadc
--> Deleting /usr/lib64/sa/sysstat
--> Deleting /usr/lib64/sa/sysstat.ioconf
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/README.md
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/StatSettings.page
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/Stats.page
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/SystemDisks.page
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/SystemStats.page
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/default.cfg
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/icons/diskstats.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/icons/statssettings.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/icons/systemstats.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/array.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/arrow.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/com.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/cpu.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/dynamix.system.stats.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/hdd.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/ram.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/images/sys.png
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/include/HardwareStats.php
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/javascript/jquery.highcharts.js
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1
--> Deleting /usr/local/emhttp/plugins/dynamix.system.stats/styles/disk.stats.css
--> Deleting empty directory /usr/local/emhttp/plugins/dynamix.system.stats/styles/
--> Deleting empty directory /usr/local/emhttp/plugins/dynamix.system.stats/scripts/
--> Deleting empty directory /usr/local/emhttp/plugins/dynamix.system.stats/javascript/
--> Deleting empty directory /usr/local/emhttp/plugins/dynamix.system.stats/include/
--> Deleting empty directory /usr/local/emhttp/plugins/dynamix.system.stats/images/
--> Deleting empty directory /usr/local/emhttp/plugins/dynamix.system.stats/icons/
--> Deleting empty directory /usr/local/emhttp/plugins/dynamix.system.stats/
--> Deleting empty directory /usr/lib64/sa/
plugin: removed

Reinstall:

plugin: installing: https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg
plugin: downloading https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg
plugin: downloading: https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg ... done
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.stats.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz
+==============================================================================

Verifying package dynamix.system.stats.txz.
Installing package dynamix.system.stats.txz:
PACKAGE DESCRIPTION:
Package dynamix.system.stats.txz installed.



-----------------------------------------------------------
Plugin dynamix.system.stats is installed.
This plugin requires Dynamix webGui to operate
Copyright 2015, Bergware International
Version: 2015.12.19a
-----------------------------------------------------------

plugin: installed

Dynamix - V6 Plugins

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

bonienl

bonienl

bonienl

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation