Dynamix - V6 Plugins

[eroz]

I'm still not sure what my sensors are?

 

eroz, try this for your sensors.conf file and save on your flash drive. Since you are returning results from sensors -u coretemp-isa-0000, I am pretty sure it will work.

 

/boot/config/sensors.conf

 

# sensor configuration

chip "coretemp-isa-0000"

label temp1 "MB Temp"
label temp2 "CPU Temp"

 

Don't forget to add modprobe coretemp in your go file.

 

Hope that helps,

 

Gary

Awesome!  Thank you, That worked.

[bonienl]

I think if you remove and then re-install the plugin it should work for you now. Did for me anyway.

 

That seems to have worked, thanks!

 

Both temps show 117; not sure if that's right.  I'd expect them to be at least a little different.

 

** I refreshed a few times, and now they are different.

 

Any way to know which is which?  There are no labels.

 

Hover your mouse over the temperature icons and labels are shown: left is processor, right is motherboard.

 

[bonienl]

bonienl,

 

is the powerdown package installed with dynamix?

 

i thought it was before.. just want to make sure....

 

Powerdown is available as a separate plugin and can be installed using this URL: https://github.com/dlandon/unraid-snap/raw/master/powerdown-x86_64.plg

 

[ICDeadPpl]

cache_dirs won't start, tried starting it from web UI and aldso via '/etc/rc.d/rc.cachedirs start'.

 

[Interstellar]

cache_dirs won't start, tried starting it from web UI and aldso via '/etc/rc.d/rc.cachedirs start'.

 

 

Same here... nothing in the log either!

[jumperalex]

Hmmm working for me. Which is to say... It works... So what is different?

[JaY_III]

Hmmm working for me. Which is to say... It works... So what is different?

 

can you walk us through how to start it?

 

Settings -> Folder Caching -> Status:Stopped

Cant seem to see the start button either

 

[Moussa]

Hmmm working for me. Which is to say... It works... So what is different?

 

can you walk us through how to start it?

 

Settings -> Folder Caching -> Status:Stopped

Cant seem to see the start button either

 

Change the 'Folder caching function' setting to Enabled and then the Apply button at the bottom.

[JaY_III]

Hmmm working for me. Which is to say... It works... So what is different?

 

can you walk us through how to start it?

 

Settings -> Folder Caching -> Status:Stopped

Cant seem to see the start button either

 

Change the 'Folder caching function' setting to Enabled and then the Apply button at the bottom.

 

That isnt working for me

 

[soana]

Same here - cache_dirs will not start.

 

next I did this:

1.uninstall plugin

2. reboot

3. install plugin and enable, after apply the service did start

4. reboot - the service shows enabled but it is stopped and will not start again.

 

syslog:

Dec  2 23:11:55 Tower2 logger: plugin: installing: /boot/config/plugins/dynamix.cache.dirs.plg
Dec  2 23:11:55 Tower2 logger: plugin: running: 'anonymous'
Dec  2 23:11:55 Tower2 logger: plugin: skipping: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs-2014.11.28.txz already exists
Dec  2 23:11:55 Tower2 logger: plugin: running: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs-2014.11.28.txz
Dec  2 23:11:55 Tower2 logger: 
Dec  2 23:11:55 Tower2 logger: +==============================================================================
Dec  2 23:11:55 Tower2 logger: | Installing new package /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs-2014.11.28.txz
Dec  2 23:11:55 Tower2 logger: +==============================================================================
Dec  2 23:11:55 Tower2 logger: 
Dec  2 23:11:55 Tower2 logger: Verifying package dynamix.cache.dirs-2014.11.28.txz.
Dec  2 23:11:55 Tower2 logger: Installing package dynamix.cache.dirs-2014.11.28.txz:
Dec  2 23:11:55 Tower2 logger: PACKAGE DESCRIPTION:
Dec  2 23:11:56 Tower2 logger: Package dynamix.cache.dirs-2014.11.28.txz installed.
Dec  2 23:11:56 Tower2 logger: 
Dec  2 23:11:56 Tower2 logger: 
Dec  2 23:11:56 Tower2 logger: plugin: creating: /tmp/start_service - from INLINE content
Dec  2 23:11:56 Tower2 logger: plugin: running: 'anonymous'
Dec  2 23:11:56 Tower2 logger:  downloading & installing cache_dirs script ... failed
Dec  2 23:11:56 Tower2 logger: 
Dec  2 23:11:56 Tower2 logger: -----------------------------------------------------------
Dec  2 23:11:56 Tower2 logger:  dynamix.cache.dirs has been installed.
Dec  2 23:11:56 Tower2 logger:  This plugin requires Dynamix webGui to operate
Dec  2 23:11:56 Tower2 logger:  Copyright 2014, Bergware International
Dec  2 23:11:56 Tower2 logger:  Version: 2014.11.28
Dec  2 23:11:56 Tower2 logger: -----------------------------------------------------------

[JaY_III]

Same here - cache_dirs will not start.

 

next I did this:

1.uninstall plugin

2. reboot

3. install plugin and enable, after apply the service did start

4. reboot - the service shows enabled but it is stopped and will not start again.

 

 

Interesting.  Seems to work on a re-instal on my end too following your steps.

Also like your results a reboot will not allow it to restart

 

Doing some more quick tests and will report back

 

edit:

 

Tried disabling before a reboot, with no luck. It apears a reboot breaks the Folder Caching.

 

If you can not get it to work uninstall and reinstall.

After every reboot you will also have to repeat the uninstall and reinstall.

 

However no reboot is required between removing and reinstalling the plugin.

 

Tested with Dynamix Cache Directories 2014.11.28

Dynamix webGui 2014.12.01

 

[dlandon]

The cachedirs plugin downloads the cache_dirs script each time the plugin is installed.  If the Internet is not available (network may not be ready yet on a reboot) or the download does not succeed, the plugin will successfully install but the cache_dirs script will not be available.  That is why it won't start - the cache_dirs script is not available.  I've passed this along to bonienl with some ideas on how to fix.

 

For the time being, remove and then re-install the cachedirs plugin until a fix is made.

[digitalfixer]

Bonienl

 

I modified the dynamix.cfg file and added the key. The sleep button is now displayed.

 

Kevin.

 

Can you uninstall and re-install S3.sleep.

 

It should add the key sleep="plugins/dynamix.s3.sleep/Sleep.php" under display settings, once this key exists the sleep button becomes visible.

[bonienl]

The cachedirs plugin downloads the cache_dirs script each time the plugin is installed.  If the Internet is not available (network may not be ready yet on a reboot) or the download does not succeed, the plugin will successfully install but the cache_dirs script will not be available.  That is why it won't start - the cache_dirs script is not available.  I've passed this along to bonienl with some ideas on how to fix.

 

For the time being, remove and then re-install the cachedirs plugin until a fix is made.

 

This is indeed happening. I will look into an approach that suites the requirements. For the time being use the workaround as explained above.

 

[bonienl]

Bonienl

 

I modified the dynamix.cfg file and added the key. The sleep button is now displayed.

 

Kevin.

 

Can you uninstall and re-install S3.sleep.

 

It should add the key sleep="plugins/dynamix.s3.sleep/Sleep.php" under display settings, once this key exists the sleep button becomes visible.

 

Good to hear, I have made a correction to the installation script as well, this will become available in an upcoming version.

 

[soana]

The 2014.12.03 update for the Dynamix Cache Directories solved the issue for me. Thanks!!!

[EdgarWallace]

My unRAID main server is showing a Dynamix System Temperature like this: ##?°C

 

cat /boot/config/sensors.conf
# sensor configuration
chip "nct6776-isa-0a30"
label CPUTIN "System Temp"
label SYSTIN "Peripheral Temp"

 

cat /boot/config/go
#!/bin/bash
/usr/local/sbin/emhttp &

cp /boot/scripts/rsync_backup.sh /etc/cron.daily
installpkg /boot/packages/etherwake-1.09-x86_64-4cf.txz

modprobe coretemp
modprobe nct6775

/usr/bin/sensors -s

sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8 C  (crit = +106.0 C)
temp2:        +29.8 C  (crit = +106.0 C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +39.0 C  (high = +85.0 C, crit = +105.0 C)
Core 0:         +35.0 C  (high = +85.0 C, crit = +105.0 C)
Core 1:         +39.0 C  (high = +85.0 C, crit = +105.0 C)
Core 2:         +36.0 C  (high = +85.0 C, crit = +105.0 C)
Core 3:         +36.0 C  (high = +85.0 C, crit = +105.0 C)

nct6776-isa-0a30
Adapter: ISA adapter
Vcore:          +1.02 V  (min =  +0.60 V, max =  +1.49 V)
in1:            +1.82 V  (min =  +1.62 V, max =  +1.99 V)
AVCC:           +3.36 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.36 V  (min =  +2.98 V, max =  +3.63 V)
in4:            +1.54 V  (min =  +1.35 V, max =  +1.65 V)
in5:            +1.27 V  (min =  +1.13 V, max =  +1.38 V)
in6:            +1.46 V  (min =  +1.42 V, max =  +1.52 V)
3VSB:           +3.36 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:           +3.14 V  (min =  +2.70 V, max =  +3.63 V)
fan1:          1032 RPM  (min =  300 RPM)
fan2:           951 RPM  (min =  300 RPM)
fan3:             0 RPM  (min =  300 RPM)  ALARM
fan4:          1048 RPM  (min =  300 RPM)
fan5:          2173 RPM  (min =  300 RPM)
SYSTIN:         +36.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
CPUTIN:         +34.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
AUXTIN:          +2.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
PECI Agent 0:   +34.5 C  (high = +95.0 C, hyst = +92.0 C)
                         (crit = +100.0 C)
PCH_CHIP_TEMP:   +0.0 C  
PCH_CPU_TEMP:    +0.0 C  
PCH_MCH_TEMP:    +0.0 C  
intrusion0:    ALARM
intrusion1:    OK
beep_enable:   enabled

 

Is there anything that I have overlooked? I have noticed that there is nct6776 in the sensors.conf and nct6775 in the go script but that was what sensors-detect is showing:

modprobe nct6776
modprobe: FATAL: Module nct6776 not found.

Thanks for any advise.

[JaY_III]

My unRAID main server is showing a Dynamix System Temperature like this: ##?°C

 

cat /boot/config/sensors.conf
# sensor configuration
chip "nct6776-isa-0a30"
label CPUTIN "System Temp"
label SYSTIN "Peripheral Temp"

 

cat /boot/config/go
#!/bin/bash
/usr/local/sbin/emhttp &

cp /boot/scripts/rsync_backup.sh /etc/cron.daily
installpkg /boot/packages/etherwake-1.09-x86_64-4cf.txz

modprobe coretemp
modprobe nct6775

/usr/bin/sensors -s

sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8 C  (crit = +106.0 C)
temp2:        +29.8 C  (crit = +106.0 C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +39.0 C  (high = +85.0 C, crit = +105.0 C)
Core 0:         +35.0 C  (high = +85.0 C, crit = +105.0 C)
Core 1:         +39.0 C  (high = +85.0 C, crit = +105.0 C)
Core 2:         +36.0 C  (high = +85.0 C, crit = +105.0 C)
Core 3:         +36.0 C  (high = +85.0 C, crit = +105.0 C)

nct6776-isa-0a30
Adapter: ISA adapter
Vcore:          +1.02 V  (min =  +0.60 V, max =  +1.49 V)
in1:            +1.82 V  (min =  +1.62 V, max =  +1.99 V)
AVCC:           +3.36 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.36 V  (min =  +2.98 V, max =  +3.63 V)
in4:            +1.54 V  (min =  +1.35 V, max =  +1.65 V)
in5:            +1.27 V  (min =  +1.13 V, max =  +1.38 V)
in6:            +1.46 V  (min =  +1.42 V, max =  +1.52 V)
3VSB:           +3.36 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:           +3.14 V  (min =  +2.70 V, max =  +3.63 V)
fan1:          1032 RPM  (min =  300 RPM)
fan2:           951 RPM  (min =  300 RPM)
fan3:             0 RPM  (min =  300 RPM)  ALARM
fan4:          1048 RPM  (min =  300 RPM)
fan5:          2173 RPM  (min =  300 RPM)
SYSTIN:         +36.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
CPUTIN:         +34.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
AUXTIN:          +2.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
PECI Agent 0:   +34.5 C  (high = +95.0 C, hyst = +92.0 C)
                         (crit = +100.0 C)
PCH_CHIP_TEMP:   +0.0 C  
PCH_CPU_TEMP:    +0.0 C  
PCH_MCH_TEMP:    +0.0 C  
intrusion0:    ALARM
intrusion1:    OK
beep_enable:   enabled

 

Is there anything that I have overlooked? I have noticed that there is nct6776 in the sensors.conf and nct6775 in the go script but that was what sensors-detect is showing:

modprobe nct6776
modprobe: FATAL: Module nct6776 not found.

Thanks for any advise.

Change your lables so the wording is the same as in the guide.

I doing this off memory but I think it should be

 

 

label temp1 "MB Temp"

label temp2 "CPU Temp"

 

Or

 

label temp1 "CPU Temp"

label temp2 "MB Temp"

 

Depending on what's correct for your system

[EdgarWallace]

Changed the file, removed the plugin, reinstalled the plugin and everything's fine now 

 

Thanks a lot JaY_III.

 

However I do have a question though. I just guess that the initial label "CPUTIN" (see my last post) equals the CPU Temp and "SYSTIN" is showing the MB Temp? Both labels have changed now:

 

nct6776-isa-0a30
Adapter: ISA adapter
MB Temp:        +37.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
CPU Temp:       +35.5 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor

 

And the Supermicro web gui is showing something different (pls. see attached screenshot).

[digitalfixer]

Updated S3 sleep plugin.

 

Still no sleep button on Array Operation.

 

dynamix.cfg

 

[display]
date="%c"
number=".,"
scale="-1"
align="right"
tabs="0"
text="0"
view=""
total="1"
spin="1"
usage="0"
icons="1"
banner=""
theme="white"
unit="C"
hot="45"
max="55"
poll="0"
refresh="1000"
sysinfo="/Tools/SystemProfiler"
[confirm]\nsleep="1"\n

 

Kevin.

[Julian0o]

Hi there, i have a Problem with the webinterface. I installed the beta12 and everything worked fine. Now i installed the s3 sleep plugin. I pasted this link in the install box and clicked install: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg

The installation went through. But now i have only text and in the web gui. I restarted the server and deleted the s3.sleep plugin from /boot/config/plugins Reboot again. The plugin doesn't show up anymore, but the webinterface is still crap. With chrome and internet explorer.

[dlandon]

Hi there, i have a Problem with the webinterface. I installed the beta12 and everything worked fine. Now i installed the s3 sleep plugin. I pasted this link in the install box and clicked install: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg

The installation went through. But now i have only text and in the web gui. I restarted the server and deleted the s3.sleep plugin from /boot/config/plugins Reboot again. The plugin doesn't show up anymore, but the webinterface is still crap. With chrome and internet explorer.

 

Don't delete plugins from the flash drive.  You should always use the plugin manager on the webgui to install and remove plugins.

 

Re-install the plugin and then remove it using the plugin manager and see if that clears it up.

[Julian0o]

thats the problem That does not work because of the web gui not offering all features. I can click uninstall and nothings happening.

 

I deleted the dynamics folder in the plugins directory because there were old files from a prevoise version. Then the Webgui was working fine. Now i rebooted the server and now it isnt responding. I have to look at it when i am at home.

[dlandon]

You'll probably have to start fresh with all plugins removed manually and add them back.  I would delete all files and directories from the /boot/config/plugins directory.

 

Be sure to delete /boot/plugins if it is there.  This is left over from the v5 and early v6 dynamix install.

[PeterB]

I'm having trouble getting temperature sensors working on my X9SCM-iiF mobo.

 

I've been through the wiki:

root@Tower:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8 C  (crit = +106.0 C)
temp2:        +29.8 C  (crit = +106.0 C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +46.0 C  (high = +85.0 C, crit = +105.0 C)
Core 0:         +36.0 C  (high = +85.0 C, crit = +105.0 C)
Core 1:         +38.0 C  (high = +85.0 C, crit = +105.0 C)
Core 2:         +43.0 C  (high = +85.0 C, crit = +105.0 C)
Core 3:         +47.0 C  (high = +85.0 C, crit = +105.0 C)

nct6776-isa-0a30
Adapter: ISA adapter
Vcore:         +0.68 V  (min =  +0.60 V, max =  +1.49 V)
in1:           +1.86 V  (min =  +1.62 V, max =  +1.99 V)
AVCC:          +3.39 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:         +3.38 V  (min =  +2.98 V, max =  +3.63 V)
in4:           +1.52 V  (min =  +1.35 V, max =  +1.65 V)
in5:           +1.26 V  (min =  +1.13 V, max =  +1.38 V)
3VSB:          +3.33 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:          +3.17 V  (min =  +2.70 V, max =  +3.63 V)
fan1:         2606 RPM  (min =  300 RPM)
fan2:         1421 RPM  (min =  300 RPM)
fan3:            0 RPM  (min =  300 RPM)  ALARM
fan4:            0 RPM  (min =  300 RPM)  ALARM
fan5:         1336 RPM  (min =  300 RPM)
SYSTIN:        +42.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
CPUTIN:        +37.5 C  (high = +95.0 C, hyst = +92.0 C)  sensor = thermistor
AUXTIN:         +2.0 C    sensor = thermistor
PECI Agent 0:   +0.0 C  
CPUTIN:        +37.5 C  (high = +80.0 C, hyst = +75.0 C)
cpu0_vid:     +0.000 V
intrusion0:   OK
intrusion1:   ALARM

root@Tower:~#

 

From this I identify SYSTIN and CPUTIN on the nct6776 as the labels for the values I want to display, so I create my sensors.conf thus:

root@Tower:~# cat /boot/config/sensors.conf
# lines starting with "#" are comments and ignored
# sensor configuration

chip "nct6776-isa-0a30"

label SYSTIN "MB Temp"
label CPUTIN "CPU Temp"

root@Tower:~#

 

Now, the driver is identified as:

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

 

so I set up my go file thus:

root@Tower:~# cat /boot/config/go
#!/bin/bash
#
# Turn on the variable clock speed (power save) feature
modprobe acpi-cpufreq

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


# Enable alternate AHCI controllers
/boot/config/enable_ahci.sh

#Mount docker device
mkdir -p /mnt/docker
mount /dev/disk/by-id/ata-ST3500418AS_5VME2D7A-part1 /mnt/docker
#
# Start the Management Utility
/usr/local/sbin/emhttp &

root@Tower:~#

 

However, even after a reboot and reinstalling the plugin, I still se the temperatures displayed as '##'

 

I do note the following in my syslog:

Dec  3 22:00:06 Tower kernel: w83627ehf: Found NCT6776F chip at 0xa30

, and further down I see:

Dec  3 22:00:08 Tower logger: Starting go script
Dec  3 22:00:08 Tower kernel: nct6775: Found NCT6776D/F or compatible chip at 0x2e:0xa30
Dec  3 22:00:08 Tower kernel: nct6775: probe of nct6775.2608 failed with error -16

 

So, I have some doubts in my mind ... it seems that the nct6776 chip is recognised by a w83627ehf driver and loading the nct6775 driver produces an error -16.