Dynamix - V6 Plugins


Recommended Posts

So I have a new build running the latest Unraid 6.6.0 rc-4; and I'm having issues with the temperature plugin.
The sensors correctly read inside the plugin like so:

 

image.png.4e0cd6b5f4d7f521307739f450135954.png

 

However after selecting desired sensors like this:

 

image.png.c275ecfaa351072958cfdd58a037d11c.png

 


And then hitting "Apply"
The sensors all disappear like so:

 

 

image.png.00bb02e7b8d7022e4ca58dab3f999faf.png

 

Hitting "Rescan" and done have no effect, and all of the sensors on the dashboard also disappear (fan speeds)
Running "sensors" in the terminal gives this output:

 

		

		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		

The content of that file looks like this after hitting Apply:

 

		

		# sensors
		chip "nct7904-i2c-0-2e"
		ignore "fan3"
		chip "nct7904-i2c-0-2e"
		ignore "fan4"
		chip "nct7904-i2c-0-2e"
		ignore "fan8"
		chip "coretemp-isa-0000"
		label "temp1" "CPU Temp"
		chip "coretemp-isa-0001"
		label "temp1" "MB Temp"
		chip "nct7904-i2c-0-2e"
		label "fan1" "Array Fan"		


If I delete the file, and then run sensors this is the output I get:

 

 

		

		nct7904-i2c-0-2e
		Adapter: SMBus I801 adapter at 0580
		in1:          +1.04 V
		in2:          +1.04 V
		in3:          +1.48 V
		in4:          +1.24 V
		in5:          +1.23 V
		in6:          +0.58 V
		in7:          +1.84 V
		in8:          +0.53 V
		in9:          +1.78 V
		in10:         +1.79 V
		in11:         +1.21 V
		in12:         +1.21 V
		in13:         +1.21 V
		in14:         +1.21 V
		in15:         +3.31 V
		in16:         +3.16 V
		in20:         +3.32 V
		fan1:        4591 RPM
		fan2:        3026 RPM
		fan3:           0 RPM
		fan4:           0 RPM
		fan5:        3006 RPM
		fan6:        3033 RPM
		fan8:           0 RPM
		temp1:        +36.9°C
		temp2:        +51.5°C
		temp3:        +50.2°C		

		coretemp-isa-0000
		Adapter: ISA adapter
		CPU Temp:     +52.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 0:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 1:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 2:       +46.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 3:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 4:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 5:       +43.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 8:       +45.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 9:       +47.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 10:      +45.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 11:      +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 12:      +45.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 13:      +46.0°C  (high = +83.0°C, crit = +93.0°C)		

		coretemp-isa-0001
		Adapter: ISA adapter
		MB Temp:      +50.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 0:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 1:       +45.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 2:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 3:       +42.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 4:       +46.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 5:       +42.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 8:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 9:       +42.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 10:      +44.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 11:      +40.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 12:      +43.0°C  (high = +83.0°C, crit = +93.0°C)
		Core 13:      +45.0°C  (high = +83.0°C, crit = +93.0°C)		


If I comment out the lines in the config file "chip nct7904-i2c-0-2e" then it works. Not sure if this is a proper fix but its working for now. Hopefully the developer of this plugin can adopt a solution:

 

		

		# sensors
		#chip "nct7904-i2c-0-2e"
		ignore "fan3"
		#chip "nct7904-i2c-0-2e"
		ignore "fan4"
		#chip "nct7904-i2c-0-2e"
		ignore "fan8"
		chip "coretemp-isa-0000"
		label "temp1" "CPU Temp"
		chip "coretemp-isa-0001"
		label "temp1" "MB Temp"
		#chip "nct7904-i2c-0-2e"
		label "fan1" "Array Fan"		

Edited by Xaero
Wrapped bulky things in spoiler tags
Link to comment
3 minutes ago, Squid said:

Tools - Update OS - Switch from Next to Stable and install 6.6.3

Should have probably mentioned; I was experiencing the same problem on Stable as well, and decided to update to see if it would fix it. 

 

Edit: Updated my post with a workaround for this chipset. Seems like a problem with the way lm_sensors uses chip names for filtering. "chip coretemp-isa-0000" works fine but "chip nct7904-i2c-0-2e" does not. This should probably be filed upstream with lm_sensors devs. For now commenting out the chip filters seems to work okay.

Edited by Xaero
Link to comment

Does the S3 Sleep plugin require disks to be spun down in order to permit sleep? My array has Default Spin Down Delay - Never. Not sure when or why it was set to that but that is the current status.

 

I have checked logging for the plugin and it certainly seems to be checking but keeps reporting disk activity on sdb (my Parity 1 drive).

 

Oct 28 07:06:42 NAS-PLEX s3_sleep: Disk activity on going: sdb

Oct 28 07:06:42 NAS-PLEX s3_sleep: Disk activity detected. Reset timers.

Oct 28 07:07:42 NAS-PLEX s3_sleep: Disk activity on going: sdb

Oct 28 07:07:42 NAS-PLEX s3_sleep: Disk activity detected. Reset timers.

Oct 28 07:08:43 NAS-PLEX s3_sleep: Disk activity on going: sdb

Oct 28 07:08:43 NAS-PLEX s3_sleep: Disk activity detected. Reset timers.

Link to comment

I have no idea why there is activity on the parity drive though. The array is idle, mover has completed and it is not doing any rebuilds.

 

S3 Sleep does have "Wait for Array Inactivity (exclude Cache)" set as default. If the Spin Down state is unimportant, I suspect my question is why is Parity 1 holding the array active. Would it be better if I started a separate thread?

 

EDIT : Forcing the drives to spin down causes the S3 Sleep plugin to correctly start counting down towards Sleep.

 

Quote

Oct 28 07:26:53 NAS-PLEX s3_sleep: All monitored HDDs are spun down
Oct 28 07:26:53 NAS-PLEX s3_sleep: Extra delay period running: 30 minute(s)

 

Edited by DanielCoffey
Link to comment
On 10/26/2018 at 10:57 PM, Frank1940 said:

Before doing that I checked and the following packages in Nerdpack were installed:

 

Lbzip

perl

screen

untempter

 

The last three packages were 'On'.

 

I then rebooted the server.  I checked on Folder Caching and found that while it was 'Enable', the Status was 'Stopped'.  I cycled  'Folder Caching Enable' and the status changed to 'Running'.   (The 'Max level depth:' is set to 4)

 

I then waited for the data drives to spin down (Delay set to 45 minutes).  At approximately 57 minutes of uptime, the disks were spun down.   I then started up

Window Explorer and opened up the server. 

 

I went down the following path:    Media  >>>>  All Movies   >>>>  S   (all are directories and the folder S contains 173 files.) 

 

The response for Media and All Movies was instantaneous.  When I got the directory  'S', the green bar started running from left to right.  I went back to Chrome and looked at the 'Main page' for the server.  I could watch as all six data disk spun up.  When the sixth spun up, the file listing now appeared.  

 

My conclusion is that the cache folders may be running but it isn't doing anything.   Diagnostic file is attached. 

 

elsie1-diagnostics-20181026-2252.zip

 

EDIT:  I have done some further testing.  I now really suspect that the cache directory plugin has some serious issues with the latest releases.  First, many folks are finding that it does not start 'running' automatically.  Second, (in my case), even after it is cycled and the the status says it is running, it does not seem to be actually caching any directories or file names.  I can't see any reading activity going on (looking at the Main tab) during the time I would think it should be doing its thing.

 

Does anyone have any thoughts as to what is going on? 

 

Anyone???

Link to comment
33 minutes ago, Frank1940 said:

Anyone???

Cache Dirs has a bug that keeps it from running when the server is started.  @bonienl is aware of it and will fix it.  For the time being, just start it manually.

 

I am not seeing any of the spin up issues you are talking about.  You are caching only one share.  Maybe your other shares are being accessed causing the spin ups.  For the time being, set all your shares in Cache Dirs and see if that helps.

 

Install the File Activity plugin and see if that can help you find the files that are causing the spin ups.

Link to comment
43 minutes ago, dlandon said:

am not seeing any of the spin up issues you are talking about.  You are caching only one share.  Maybe your other shares are being accessed causing the spin ups.  For the time being, set all your shares in Cache Dirs and see if that helps.

 

I know that the disk spinup activity is being caused by Windows Explorer trying to open up a subdirectory.  (ex. "S" on the Media  -> All Movies -> S ).  I have a 2560X1600 monitor and I have see both the Main Tab (using Chrome) and the Windows Explorer screens at the same time.  When the green bar of Windows Explorer was running left to right, the data disks would spin up one by one. As soon as all six disks were spun up, the file list would appear in the Windows Explorer pane.  

 

I implemented your suggestion that I cache all of the Shares instead of just Media.  Then I wrote the first paragraph above.  While writing, I wanted to verify the Windows Explorer response and started doing my testing sequence again.  This time everything seems to be working fine.  The subdirectories all appear to be cached.   However, Data Disks 1, 4, 5, and 6 had spun up and there were reads made on those disks.  (Before starting the cache Directory plugin, I made a printout of the Main tab.) I then spun the data disks down.  I checked some of the other shares (besides Media) and they appear to be cached to the for the first three levels (that's the Depth Level I have set) and going beyond that point requires a wait time for the data disk(s) involved to spin up.  

 

So it appears (from my testing at this juncture) that you have to cache all Shares for Cache Directories to work as well as manually starting it.  By the way, previously I had 'excluded' all of the other directories and that did not work either.  (I had figured out that I should try the 'Include' as opposed to the 'Exclude' much, much earlier in my attempt to solve this.  

Link to comment

I recently implemented the Autofan plugin to control the Noctua NF-F12 fans on the hot-swap drive cages in my server.  There is only one PWM fan header on the MB and I am using the Y-cable that came with the fans to attach two fans to the one header.  I am also using the low-noise adapters (LNA) on each fan. 

 

Some observations:

 

1 - The plugin is doing its job very well and increasing or decreasing fan speeds according to the configured minimum and maximum temps.

2 - Fan speeds do not appear to be accurate.  The attached fans have a maximum rated speed of 1500 rpm +/- 10% without the LNA; with the LNA, the max speed is supposedly 1200 rpm +/- 10%.  Fan speeds reported by the plugin range from ~400 rpm when "off" to ~2700 rpm when at full speed.  Many of the reported intermediate speeds as temperature increases also exceed the supposed 1200 rpm maximum.

 

I also have the System Temperature plugin installed and configured

 

I am not terribly concerned about the reported RPM as the fans speed is scaling appropriately, however, I am curious if the discrepancy is due to misconfiguration, anomlies with the MB sensor (nct6776) or something else.  Again, not a big deal, just curious.

Link to comment
  • 2 weeks later...

Plugin:  Dynamix Stop Shell

Feature Request:

 

can you also check for 'screen' and/or 'tmux' running as well and kill them also.

 

sometimes I have a tmux running and forget about it, one example is I have a log vewer setup, and it keeps some docker log files open which will keep the cache drive from being umounted and hang the array shutdown.

 

Thanks for the consideration

Myk

Link to comment

I have version 6.6.5 installed on a Supermicro server SC825TQ-563LPB, motherboard model X8DTi-F.  I installed Perl from Nerdpack and Dynamix System Temp plugin from Community Applications on my server.  I clicked the detect button and was able to upload drivers.  I had a list to pick from in the drop downs and I made my corresponding selections.  I hit the apply button and there was no information that is displaying on the bottom of GUI.  I went back into the plugin to redo the steps, but now I cannot get any drivers to upload when I click the upload driver button.  The only option that is available for the sensors drop downs is "Not used."  I uninstalled and reinstalled Perl and Dynamix System Temp plugin again, and I still don't get any drivers.

 

Could you please explain how I can get this fixed?

Link to comment

I have a question with the S3 Sleep plugin.  The issue I have is when I set it to “Wait for array inactivity” “Yes, exclude cache”  It still refuses to go to the sleep mode.  I noticed, on the main page with all drives spun down a Temp for one or more of the drives stays and doesn’t turn to *.  Could this be why the system thinks it still up and not inactive? Preventing it from going to sleep.

 

335703380_Screenshot_2018-11-12ServerMain.thumb.png.32e5d31e0c1d71208230aff7216f9d03.png

Any thoughts would be helpful.

Edited by Walter S
Link to comment

@bonienlIt seems the cache-dirs plugin is pretty stable now with unRaid 6.6.5. If you want to pull into your dynamix main, please feel free to do so. I think I have a pull-request that has all the changes, or you can just pull from my master-upstream directly.

 

I'm publishing releases via releases-tab so I don't get git history poluted with old archives. But you can revert that in the plugin, and just use your strategy. Or we could have a conversation about where to host the plugin going forward.

 

Ahh, I just noticed a 13 days old mail in my mailbox I havn't checked for some time. Sorry boniel... :)

Edited by Alex R. Berg
Link to comment

The drivers for my motherboard do not show any of my fans.

 

Also, I can only choose one cpu in system temp plugin. I have 2 cpus in my server and would like temps on both.

 

Anyway to resolve both of these issues? I wanted to use these plugins specifically for fan info and control.

 

Motherboard: Gigabyte ga-7pesh2

 

Quote

it8728-isa-0a30
Adapter: ISA adapter
in0:          +2.22 V  (min =  +2.58 V, max =  +1.54 V)  ALARM
in1:          +1.36 V  (min =  +0.14 V, max =  +0.58 V)  ALARM
in2:          +2.22 V  (min =  +2.93 V, max =  +0.17 V)  ALARM
+3.3V:        +3.29 V  (min =  +3.70 V, max =  +4.51 V)  ALARM
in4:          +2.22 V  (min =  +1.78 V, max =  +2.30 V)
in5:          +1.36 V  (min =  +0.12 V, max =  +2.23 V)
in6:          +2.22 V  (min =  +2.98 V, max =  +1.75 V)  ALARM
3VSB:         +3.29 V  (min =  +5.83 V, max =  +0.89 V)  ALARM
Vbat:         +3.10 V
temp1:        +65.0°C  (low  = +100.0°C, high = -37.0°C)  ALARM  sensor = thermistor
temp2:        +40.0°C  (low  = +103.0°C, high = -58.0°C)  ALARM  sensor = thermistor
temp3:        +54.0°C  (low  = +107.0°C, high = +16.0°C)  ALARM  sensor = thermistor
intrusion0:  ALARM

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +40.0°C  (high = +66.0°C, crit = +76.0°C)
Core 0:       +37.0°C  (high = +66.0°C, crit = +76.0°C)
Core 1:       +38.0°C  (high = +66.0°C, crit = +76.0°C)
Core 2:       +39.0°C  (high = +66.0°C, crit = +76.0°C)
Core 3:       +40.0°C  (high = +66.0°C, crit = +76.0°C)
Core 4:       +40.0°C  (high = +66.0°C, crit = +76.0°C)
Core 5:       +39.0°C  (high = +66.0°C, crit = +76.0°C)
Core 6:       +37.0°C  (high = +66.0°C, crit = +76.0°C)
Core 7:       +36.0°C  (high = +66.0°C, crit = +76.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Package id 1:  +45.0°C  (high = +66.0°C, crit = +76.0°C)
Core 0:        +40.0°C  (high = +66.0°C, crit = +76.0°C)
Core 1:        +38.0°C  (high = +66.0°C, crit = +76.0°C)
Core 2:        +41.0°C  (high = +66.0°C, crit = +76.0°C)
Core 3:        +45.0°C  (high = +66.0°C, crit = +76.0°C)
Core 4:        +36.0°C  (high = +66.0°C, crit = +76.0°C)
Core 5:        +41.0°C  (high = +66.0°C, crit = +76.0°C)
Core 6:        +36.0°C  (high = +66.0°C, crit = +76.0°C)
Core 7:        +40.0°C  (high = +66.0°C, crit = +76.0°C)

 

Edited by naik
Link to comment
1 minute ago, Frank1940 said:

 

Does this mean that those of us who were on @Alex R. Berg's fork of of the Preclear plugin will end up back on this version or will we have to uninstall and reinstall?  

Presumably, if you installed the forked .plg file, you will have to uninstall / reinstall as the plg points to a different github address.

Link to comment
19 minutes ago, Frank1940 said:

 

Does this mean that those of us who were on @Alex R. Berg's fork of of the Preclear plugin will end up back on this version or will we have to uninstall and reinstall?  

This is not the Preclear plugin, but the Dynamix Cache Dirs plugin ;)

You would need to uninstall the forked version and install this version.

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.