Dynamix - V6 Plugins


Recommended Posts

5 minutes ago, DontWorryScro said:

Weird, i have it installed but i do not have those tabs I see in your screenshot. Maybe another plugin I have is interfering with that.

 

You're not displaying in tabbed mode.  Have you scrolled down?  

Link to comment

after upgrading to 6.10 stable, when i go to "stats" it logs an error in unraid syslog:

 

Quote

May 18 20:08:29 husky nginx: 2022/05/18 20:08:29 [error] 6494#6494: *10910 open() "/usr/local/emhttp/plugins/dynamix.system.stats/images/sys.png" failed (2: No such file or directory) while sending to client, client: 192.168.1.222, server: , request: "GET /plugins/dynamix.system.stats/images/sys.png HTTP/2.0", host: "192.168.1.111", referrer: "https://192.168.1.111/Stats"

 

Link to comment
On 4/8/2022 at 12:47 AM, dnLL said:

I'm using the USB Manager plugin to run an Unraid VM within Unraid and since then, I'm getting this error every night:

fstrim: /mnt/disks/UNRAIDVM: the discard operation is not supported

I could uninstall the plugin and run the fstrim command only on my cache but a fix would be great. Not sure why it tries to trim my USB drive.

Has this been fixed?

Link to comment

The "Share Floor" plugin is broken for me. I think it has something to do with that I use different ports for my web ui. It is trying to acces the web ui on regular https port which is used by my reverse proxy.

 

Scanning downloads ...
Warning: file_get_contents(): Peer certificate CN=`*.mydomainname.com' did not match expected CN=`localhost' in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40

Warning: file_get_contents(): Failed to enable crypto in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40

Warning: file_get_contents(http://localhost/update.htm): failed to open stream: operation failed in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40
updated - new floor setting: 10.3 GB
Scanning media ...
Warning: file_get_contents(): Peer certificate CN=`*.mydomainname.com' did not match expected CN=`localhost' in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40

 

Link to comment
39 minutes ago, mihu said:

The "Share Floor" plugin is broken for me. I think it has something to do with that I use different ports for my web ui. It is trying to acces the web ui on regular https port which is used by my reverse proxy.

 

Scanning downloads ...
Warning: file_get_contents(): Peer certificate CN=`*.mydomainname.com' did not match expected CN=`localhost' in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40

Warning: file_get_contents(): Failed to enable crypto in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40

Warning: file_get_contents(http://localhost/update.htm): failed to open stream: operation failed in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40
updated - new floor setting: 10.3 GB
Scanning media ...
Warning: file_get_contents(): Peer certificate CN=`*.mydomainname.com' did not match expected CN=`localhost' in /usr/local/emhttp/plugins/dynamix.share.floor/scripts/share_floor on line 40

 

 

Thanks for reporting.

Yes, the plugin does not take into consideration non standard ports. This needs to be added.

 

Link to comment

Hi!

I was wondering whether the Cache Dirs plugin is still supported/being developed? I am currently on Unraid 6.10.0.

 

My setup only has one share that uses the array. I have included it and excluded the rest of the shares in the plugin settings but am not sure what else to do. What settings would be smart to change?

  • Upvote 1
Link to comment
2 hours ago, francrouge said:

hi all system temps seem to be broken since i upgrade

 

Can see my MB temps but cpu yes

 

( Got perl )

 

Reboot a couple of times and scan etc

 

 

thx

 

For me I just had to go re-select the probes in settings > system temp. since the sensors names changed as newer linux kernel has better support for my mobo.

Link to comment

Is the Dynamix SSD Trim plugin still required on pools that use BTRFS with encryption? The plugin mentions:

 

Quote

Enables and runs trim on your XFS formatted SSDs (Not required for BTRFS)

 

But I have read that the `discard=async` BTRFS option included as of unRAID 6.9 doesn't work on encrypted drives.

Link to comment

Hi all,

 

I've installed the Dynamix Sleep plugin having configured as such:

image.thumb.png.89b778349135132bbd27f42141e762a2.png

 

But it's not shutting down the server but instead keeps looping on "Initialize TCP activity counter".

image.png.be01f8812c07ed1a3fd5b33e9b824172.png

 

Has anyone seen this before? What can I do to resolve this?

Link to comment

FYI: Sleep function (or Plugin) under unraid 6.10.1 not working properly.

 

I did a Bug report but some told me, thats not a unraid-problem...

 

Description of the problem:

Under unraid 6.10.1, the server went to sleep as normal - no problems so far.

After a wakeup, nothing is reachable... no ping, no GUI, no SSH.

Only a poweroff and a reboot bring the server back to life.

 

The problem:

Electricity costs increased to 50 eurocent/kWh and this Sleep-function is essential!

So i reverted back to 6.9.2

 

 

Edited by Zonediver
Link to comment
1 hour ago, Zonediver said:

FYI: Sleep function (or Plugin) under unraid 6.10.1 not working properly.

 

I did a Bug report but some told me, thats not a unraid-problem...

 

Description of the problem:

Under unraid 6.10.1, the server went to sleep as normal - no problems so far.

After a wakeup, nothing is reachable... no ping, no GUI, no SSH.

Only a poweroff and a reboot bring the server back to life.

 

The problem:

Electricity costs increased to 50 eurocent/kWh and this Sleep-function is essential!

So i reverted back to 6.9.2

 

 

I do an automated closedown of my Unraid server shortly after midnight and then have the BIOS configured to restart it at a predetermined time in the morning?   I could instead us WOL to boot the server if I wanted to.   Is there any reason such an approach is no worth trying in your case and it is important the server sleeps rather than powers off?

Link to comment
1 hour ago, itimpi said:

I do an automated closedown of my Unraid server shortly after midnight and then have the BIOS configured to restart it at a predetermined time in the morning?   I could instead us WOL to boot the server if I wanted to.   Is there any reason such an approach is no worth trying in your case and it is important the server sleeps rather than powers off?

 

Interesting idea... i did not try this because the server-boot take ages - but i will try 👍

 

EDIT: There is an other problem:

When the server boot up, it is necessary to send all disks to standby "by hand".

If i dont do this, the server never went to sleep or in this case did not shutdown...

So a shutdown is not an option.

Edited by Zonediver
Link to comment
1 hour ago, Zonediver said:

When the server boot up, it is necessary to send all disks to standby "by hand".

If i dont do this, the server never went to sleep or in this case did not shutdown...

So a shutdown is not an option.

This particular problem would be easy enough to solve by using the User scripts plugin to issue explicit spindown commands to all the drives just after the array has been started.  Alternatively you could just have a relatively short value set for the spindown time so that they spin down naturally reasonably quickly.

Link to comment
13 minutes ago, itimpi said:

This particular problem would be easy enough to solve by using the User scripts plugin to issue explicit spindown commands to all the drives just after the array has been started.  Alternatively you could just have a relatively short value set for the spindown time so that they spin down naturally reasonably quickly.

 

Thats not the point...

After a reboot, all disk are active, and then went to "idle" and not "standby" - and if the disks are only "idle", the server is doing nothing.

But you NEED the status "standby" to send the server to sleep or shutdown...

I tried this several times... only a manual "push the button <spin down>" sends all disk to "standby".

This propblem exists since more then 5 or 6 years and isn't fixed... and i guess will never been fixed...

And this happens "always after a reboot".

So after "every" reboot, you have to push this f.... button "only once" to send the disks to "standby" - then all is working...

If you know a script, which can do this "push the button" trick, let me know 😉

Edited by Zonediver
Link to comment
1 minute ago, Zonediver said:

...because the auto-shutdown is not working, if the disk are all "idle" and not "standby"...

Are you saying that pressing the Shutdown command in the GUI does not work?   All I do is use the User Scripts plugin to issue the same command that is issued when you press the Shutdown command in the GUI.

Link to comment
15 minutes ago, itimpi said:

Are you saying that pressing the Shutdown command in the GUI does not work?   All I do is use the User Scripts plugin to issue the same command that is issued when you press the Shutdown command in the GUI.

 

The button in the GUI is working, but i dont have a script to do this automaticly...

Link to comment
3 minutes ago, Zonediver said:

 

The button in the GUI is working, but i dont have a script to do this automaticly...

The script I use is:

#!/bin/bash
#noParity=true
logger "overnight powerdown"
powerdown

In User Scripts.  The #noparity line stops the shutdown happening if a parity check is running.

 

I then use a custom schedule of:

15 0 * * 1-6

to shutdown at 15 minutes after midnight except on Sundays (as I have a special task running then that needs the server active).

 

I have set the server BIOS to automatically start up the server again at 9:00 AM and that means it is ready for me about 5 minutes later which about the time I am first likely to want to access it.   Powering off for about 9 hours per day I estimate saves over £100 per year on my electricity bill (may be more now with recent price rises in the UK).    I could also have used WOL as an alternative to a specific time to wake up the server which would be something I could issue dynamically from my iPhone/iPad if I wanted more flexibility on the startup time.

Link to comment
12 minutes ago, itimpi said:

The script I use is:

#!/bin/bash
#noParity=true
logger "overnight powerdown"
powerdown

In User Scripts.  The #noparity line stops the shutdown happening if a parity check is running.

 

I then use a custom schedule of:

15 0 * * 1-6

to shutdown at 15 minutes after midnight except on Sundays (as I have a special task running then that needs the server active).

 

Thats not what i need...

 

My "need" looks like this:

If all disks are spun down, send the server to sleep or shutdown.

 

A specific time is not helpful because a lot of family-members outside are watching Plex - so i cant shutdown at a specific time...

And THAT is my problem! With the sleep plugin and v6.9.2 all is working fine, with 6.10.1, nothing works anymore...

Edited by Zonediver
Link to comment

If you cannot select a time then you are going to have more difficulty.   I simply chose a time I knew was late enough to be very unlikely to impact anybody.

 

I have thought of upgrading the script to check if drives are all spun down before attempting the power down which would be easy enough to do.   That might well allow me to shutdown the server earlier,  but I have not bothered to do that so far.    Checking things like LAN traffic I found to be more problematic.

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.