Dynamix - V6 Plugins

[bonienl]

Dynamix Disk IO doesn't work with NVMe devices, don't know if you need one to test, but any chance you can fix it?

 

Can you post an output of

 

cat /proc/diskstats

 

And let me know which is the NMVe device

 

[bonienl]

Not 100% sure if this is a defect with Bleeding Edge or with the stock UI (not in the mood to diagnose it properly  )

 

But, it appears that the dynamix webUI update available footer is not honoring the OS version checks.

 

I can manually edit /tmp/plugins/dynamix.plg, bump up the OS version AND the version tags , and I get the footer stating that an update is available for dynamix, when in fact I should not be seeing that.

 

You actually found a bug in 6.x series (since the footer announcement feature was introduced).

 

The good news; correction is made, if you want to test then install latest version of Dynamix Bleeding Edge plugin.

 

[JorgeB]

Can you post an output of

 

cat /proc/diskstats

 

And let me know which is the NMVe device

 

It's nvme0n1 (or nvme0n1p1)

 

Thanks.

 

 

 

Linux 4.4.19-unRAID.

root@Tower7:~# cat /proc/diskstats
   7       0 loop0 2277 0 154448 877 8985 0 903728 13721 0 4318 14598
   7       1 loop1 68 0 2688 14 0 0 0 0 0 7 14
   7       2 loop2 0 0 0 0 0 0 0 0 0 0 0
   7       3 loop3 0 0 0 0 0 0 0 0 0 0 0
   7       4 loop4 0 0 0 0 0 0 0 0 0 0 0
   7       5 loop5 0 0 0 0 0 0 0 0 0 0 0
   7       6 loop6 0 0 0 0 0 0 0 0 0 0 0
   7       7 loop7 0 0 0 0 0 0 0 0 0 0 0
  43       0 nbd0 0 0 0 0 0 0 0 0 0 0 0
  43     128 nbd1 0 0 0 0 0 0 0 0 0 0 0
  43     256 nbd2 0 0 0 0 0 0 0 0 0 0 0
  43     384 nbd3 0 0 0 0 0 0 0 0 0 0 0
  43     512 nbd4 0 0 0 0 0 0 0 0 0 0 0
  43     640 nbd5 0 0 0 0 0 0 0 0 0 0 0
  43     768 nbd6 0 0 0 0 0 0 0 0 0 0 0
  43     896 nbd7 0 0 0 0 0 0 0 0 0 0 0
  43    1024 nbd8 0 0 0 0 0 0 0 0 0 0 0
  43    1152 nbd9 0 0 0 0 0 0 0 0 0 0 0
  43    1280 nbd10 0 0 0 0 0 0 0 0 0 0 0
  43    1408 nbd11 0 0 0 0 0 0 0 0 0 0 0
  43    1536 nbd12 0 0 0 0 0 0 0 0 0 0 0
  43    1664 nbd13 0 0 0 0 0 0 0 0 0 0 0
  43    1792 nbd14 0 0 0 0 0 0 0 0 0 0 0
  43    1920 nbd15 0 0 0 0 0 0 0 0 0 0 0
   8       0 sda 870 4826 61699 4792 518 83 1124 25117 0 13120 29909
   8       1 sda1 851 4826 60635 4753 518 83 1124 25117 0 13093 29870
259       0 nvme0n1 1624061 0 14698526 254224 8252375 0 107073268 112170185 0 2                                                                                        86024 112751618
259       1 nvme0n1p1 1624020 0 14698182 254223 8252174 0 107073268 112169875 0                                                                                         285872 112741377
   8      16 sdb 9727 1241632 10016742 397932 10281 1249179 10077048 230201 0 85                                                                                        711 628615
   8      17 sdb1 9698 1241632 10016278 397803 10281 1249179 10077048 230201 0 8                                                                                        5582 628488
   8      32 sdc 1179 60836 501792 772 747046 124341531 1000708584 11610198 0 12                                                                                        01918 11610749
   8      33 sdc1 1165 60836 501544 770 747042 124341531 1000708584 11610191 0 1                                                                                        201910 11610712
   8      64 sde 557 8860 81206 2768 5 509 4112 12 0 1473 2780
   8      65 sde1 528 8860 80742 2632 5 509 4112 12 0 1337 2644
   8      80 sdf 520 8793 80374 2981 5 509 4112 10 0 1692 2991
   8      81 sdf1 491 8793 79910 2852 5 509 4112 10 0 1564 2862
   8      96 sdg 332 8562 77022 2547 4 508 4096 11 0 1130 2558
   8      97 sdg1 303 8562 76558 2413 4 508 4096 11 0 996 2424
   8     112 sdh 47027 61 3346337 41601 82512 77 2618380 308960 0 39084 350475
   8     113 sdh1 47015 61 3346153 41597 67457 77 2618380 293633 0 25370 335147
   8      48 sdd 465351 22156030 181077806 2332168 9781 1186933 9571296 290269 0                                                                                         992502 2623816
   8      49 sdd1 465322 22156030 181077342 2332029 9299 1186933 9571296 288519                                                                                         0 991896 2621927
   8     128 sdi 1837 1 113913 13293 197 0 5304 11583 0 18378 24876
   8     129 sdi1 1792 1 111713 12781 111 0 5304 10853 0 17243 23634
   8     144 sdj 124 1 14697 84 11 0 4136 38 0 85 122
   8     145 sdj1 112 1 14513 76 11 0 4136 38 0 77 114
   8     160 sdk 44471 103 14453033 51678 2282 677 2538575 155484 0 33443 207132
   8     161 sdk1 44459 103 14452849 51669 2282 677 2538575 155484 0 33434 20712                                                                                        3
   8     176 sdl 147 0 16129 91 11 0 4136 44 0 91 134
   8     177 sdl1 135 0 15945 85 11 0 4136 44 0 85 128
   9       1 md1 78 0 2178 0 1004 0 493252 0 0 0 0
   9       2 md2 553134 0 171568993 0 6342 0 9567083 0 0 0 0
   9       3 md3 393 0 16813 0 2 0 4096 0 0 0 0
   9       4 md4 363 0 15990 0 2 0 4096 0 0 0 0
   9       5 md5 176 0 12629 0 2 0 4096 0 0 0 0

[bonienl]

Thanks, I made an update to support NVMe devices. Give it a try

[JorgeB]

Thanks, I made an update to support NVMe devices. Give it a try

 

It works Thanks again!

[Squid]

Not 100% sure if this is a defect with Bleeding Edge or with the stock UI (not in the mood to diagnose it properly  )

 

But, it appears that the dynamix webUI update available footer is not honoring the OS version checks.

 

I can manually edit /tmp/plugins/dynamix.plg, bump up the OS version AND the version tags , and I get the footer stating that an update is available for dynamix, when in fact I should not be seeing that.

 

You actually found a bug in 6.x series (since the footer announcement feature was introduced).

 

The good news; correction is made, if you want to test then install latest version of Dynamix Bleeding Edge plugin.

looks good

[Squid]

The one thing that I've missed on the dashboard for quite awhile is the previous behaviour (6.0Beta something) where hovering over the thumbs up icon on the drives would give you the # of reallocated sectors / pending sectors.  Ever since that got removed, I've missed it (don't miss it sending me the excessive notifications however).  Would be sweet if those two highly watched attributes could be implemented into the hover text without having to go to the attributes screen....

[bonienl]

System Buttons

 

On my Elite TV Server its display behaviour is fine, however on my Stacker Media Server its behavious is odd, meaning that the buttons are located below the main menu bar, with a white background on certain Tab(-Subtabs).

 

Both using Windows explorer and both with Tabbed Views.

 

This happens on the Tab(-Subtab): Dashboard, Shares-User Shares, Settings, Plugins-Installed Plugins, Apps-Installed Apps, Stats-Disk Stats and Tools.

 

It not a real problem; just annoying (to the nice layouts).

 

There is limited space in the header and when too many items are displayed the ones at the right side move down.

 

It is possible to move certain items from the header to the settings page and regain space.

 

As Squid mentioned "Users" can be moved. "Stats" can be moved too (if installed).

 

[smap]

bonienl is there any difference between pressing the button "sleep" (manually sending the server to sleep) and letting the server go to sleep by itself?

 

The thing is if I manually set the server to sleep when it wakes up everything is working, if I let it sleep by itself when it wakes up a lot of stuff is not working properly.

[bonienl]

The one thing that I've missed on the dashboard for quite awhile is the previous behaviour (6.0Beta something) where hovering over the thumbs up icon on the drives would give you the # of reallocated sectors / pending sectors.  Ever since that got removed, I've missed it (don't miss it sending me the excessive notifications however).  Would be sweet if those two highly watched attributes could be implemented into the hover text without having to go to the attributes screen....

 

Ok, I reverted back to the earlier 6.1 implementation which fills the context menu with monitored attributes which turned 'bad'.

 

It is available in version 2016.09.26 of Dynamix Bleeding Edge plugin.

[bonienl]

bonienl is there any difference between pressing the button "sleep" (manually sending the server to sleep) and letting the server go to sleep by itself?

 

The thing is if I manually set the server to sleep when it wakes up everything is working, if I let it sleep by itself when it wakes up a lot of stuff is not working properly.

 

No, the same command to sleep is executed. The sleep button is unconditional and immediate, while the sleep script only acts when conditions are met to put the system to sleep.

 

[smap]

bonienl is there any difference between pressing the button "sleep" (manually sending the server to sleep) and letting the server go to sleep by itself?

 

The thing is if I manually set the server to sleep when it wakes up everything is working, if I let it sleep by itself when it wakes up a lot of stuff is not working properly.

 

No, the same command to sleep is executed. The sleep button is unconditional and immediate, while the sleep script only acts when conditions are met to put the system to sleep.

 

Thanks. Strange then that it doesn't have the same behavior when waking up. I'll activate the log maybe I can find out what's failing.

[Frank1940]

Ok, I reverted back to the earlier 6.1 implementation which fills the context menu with monitored attributes which turned 'bad'.

 

It is available in version 2016.09.26 of Dynamix Bleeding Edge plugin.

 

YES!  That is a real positive.  It is so much quicker than tabbing through the attributes pages for each drive.  (I never realized it existed until Squid asked to have it restored!  So thanks, Squid!) 

[Guzzi]

@johnnie.black, as you were interested too, would you like to test it? Simply rename attached file of OP to autofan and copy it into /usr/local/emhttp/plugins/dynamix.system.autofan/scripts and restart the tool (e.g. update a setting in the GUI will restart it using the updated script).

 

I upgraded my board and unfortunately autofan doesn't work anymore, so can't test.

... is it the X11SSM-F that doesn't support autofan anymore? (Asking, because I thought about upgrading to that board too)

[JorgeB]

 

 

... is it the X11SSM-F that doesn't support autofan anymore? (Asking, because I thought about upgrading to that board too)

 

Yep.

[gundamguy]

Now that I am on 6.2 and have my dual parity set up, I'm thinking about installing System Temp for the first time, it seems like it takes a bit more then just installing the plugin, is there a walkthouh or step by step guide on getting System Temp up and running?

[RobJ]

It might be nice to have the Bleeding Edge plugin mentioned in your first post for this thread, along with a description of the current added features, and a disclaimer that it's a constantly changing testbed, is temporary, and not as well tested, a beta thing?  If you do add it, I imagine it would have its own little section, apart from the 'approved' ones.  This is just my opinion, you may prefer it to stay somewhat obscure and private.

[trurl]

Now that I am on 6.2 and have my dual parity set up, I'm thinking about installing System Temp for the first time, it seems like it takes a bit more then just installing the plugin, is there a walkthouh or step by step guide on getting System Temp up and running?

wiki: Setting up CPU and board temperature sensing

[NotYetRated]

Is there any way to filter out some odd spikes I see in my Dynamix Stats? Specifically looking at my history of Network and Storage, my network has a couple of sharp spikes upwards of 160gb/s. This would be awesome, however it is definitely not true. It is scaling the graph to lose all of the useful information of trending. Ditto on disk access, with a couple of random insane spikes upwards of 1gb/s.

[bonienl]

It might be nice to have the Bleeding Edge plugin mentioned in your first post for this thread, along with a description of the current added features, and a disclaimer that it's a constantly changing testbed, is temporary, and not as well tested, a beta thing?  If you do add it, I imagine it would have its own little section, apart from the 'approved' ones.  This is just my opinion, you may prefer it to stay somewhat obscure and private.

 

I keep this plugin purposely low profile. It is not meant to stay, because at some point in time it will be integrated into the official webGUI. It does give me however valuable feedback of experienced users and helps me to correct issues or to make improvements before integration takes place. This in turn ensures well tested code when a new release is made available by LT.

 

[bonienl]

Is there any way to filter out some odd spikes I see in my Dynamix Stats? Specifically looking at my history of Network and Storage, my network has a couple of sharp spikes upwards of 160gb/s. This would be awesome, however it is definitely not true. It is scaling the graph to lose all of the useful information of trending. Ditto on disk access, with a couple of random insane spikes upwards of 1gb/s.

 

Data points are recorded and stored by the sysstats application. Usually spikes occur when there was some unforeseen interruption in the recording. These are stored in the database files and can't be removed afaik.

 

The GUI application does do filtering and removes any unrealistic values. The threshold for this is fixed (hard-coded) and higher than the numbers you see. I need to see how to make that smarter.

 

[NotYetRated]

Is there any way to filter out some odd spikes I see in my Dynamix Stats? Specifically looking at my history of Network and Storage, my network has a couple of sharp spikes upwards of 160gb/s. This would be awesome, however it is definitely not true. It is scaling the graph to lose all of the useful information of trending. Ditto on disk access, with a couple of random insane spikes upwards of 1gb/s.

 

Data points are recorded and stored by the sysstats application. Usually spikes occur when there was some unforeseen interruption in the recording. These are stored in the database files and can't be removed afaik.

 

The GUI application does do filtering and removes any unrealistic values. The threshold for this is fixed (hard-coded) and higher than the numbers you see. I need to see how to make that smarter.

 

Might be shortest putt to just drop the hard code and make it configurable. That way each person and their individual setup can set their cropping limit based on their individual systems? Just a thought. Thanks for the reply!

[gerard6110]

Old issue.  Go to settings - display settings and move the users menu to the settings area

 

Sent from my LG-D852 using Tapatalk

 

OK, moved Users menu to the Settings menu. All buttons now staying on the header.

However, spacing between header menus differs from menu to menu:

Wide: Dashboard, Shares, Settings, Plugins, Docker, Apps, Stats and Tools

Narrow: Main, VMs

[Squid]

Dynamix Bleeding Edge

 

How about when the stop array check box is disabled (due to a parity check in progress or mover running), you put text there stating why its disabled.

 

I always wind up hitting it a couple of times, saying WTF to the computer and then start to look down the screen to try and figure out why.  (Usually its because I got a parity check in progress, but this time I almost sat down and wrote a defect report before I noticed that mover was running)

[bonienl]

Old issue.  Go to settings - display settings and move the users menu to the settings area

 

Sent from my LG-D852 using Tapatalk

 

OK, moved Users menu to the Settings menu. All buttons now staying on the header.

However, spacing between header menus differs from menu to menu:

Wide: Dashboard, Shares, Settings, Plugins, Docker, Apps, Stats and Tools

Narrow: Main, VMs

 

This has to do with your screen resolution. When the screen width is less than 1280 pixels, it needs to scale the picture.