Jump to content

Dynamix - V6 Plugins


Recommended Posts

2 hours ago, icezolation said:

Anyone willing to catch me up on the Dynamic S3 Sleep plugin?

 

I am trying to figure out why the plugin is completely ignoring a parity check running. I've set it up like this (see screenshot). Am I missing something?

 

grafik.thumb.png.3872c7dfec12998cc9e21ea7a09daeaf.png

Please also have a look at my fork for the sleep plugin. It fixes some stuff and adds some features.

 

Have a look here:

 

  • Like 1
Link to comment
37 minutes ago, jojo345 said:

Toggle/choose all your drives under "Monitor disks outside array", might help to resolve this problem.

 

p.s.

Execute function: "enable" !?

Added my parity drive to the "Monitor disks outside array" and will test that out. Thank you. Just find it a bit weird that the plugin doesn't wait for sleep/shutdown when a parity check is running.

"Execute function" - yes, I disabled it when I noticed that the server was shutdown during the night because of the Dynamic S3 Sleep.

Link to comment
3 minutes ago, icezolation said:

Added my parity drive to the "Monitor disks outside array" and will test that out. Thank you. Just find it a bit weird that the plugin doesn't wait for sleep/shutdown when a parity check is running.

"Execute function" - yes, I disabled it when I noticed that the server was shutdown during the night because of the Dynamic S3 Sleep.

I think the problem here is, that the disk activity checker is broken with the current sleep version. The plugin does not correctly check if a disk is active. Therefore the plugin decides to goto sleep, because no disk activity.

 

This is also fixed in my fork.

  • Like 1
Link to comment
Posted (edited)

System Temp has a small bug in it which causes the plugin startup script to delete sensors-detect on Unraid 7 betas.

 

# Remove sensors-detect script (Unraid 6.7 and earlier)
source /etc/unraid-version
version=${version:2:2}
if [[ $((${version/./}*1)) -lt 8 ]]; then
  rm -f /usr/sbin/sensors-detect
fi

 

As the above only checks the minor version number, it's evaluating 0 as less than 8 and deleting the script.

 

And once the script is deleted, the plugin can't find any sensors, identify, nor load their drivers .

Edited by Espressomatic
Link to comment
Posted (edited)
On 6/30/2024 at 12:00 AM, d3nny said:

it's not maintained anymore by bergware. So pull request via github is senseless. Last update is more than a year.

Right now it's maintained by unraid itself.

Could the @unraid team please reflect this on the plugin's "about"? Also, I'd be very happy, if this could be incorporated: https://github.com/lm-sensors/lm-sensors/issues/167 I have exactly that chip, but since the driver, outlined there, is not available fan control does not work for me. Thanks.

Edited by amix
fix and additional info
Link to comment
On 7/8/2024 at 10:14 PM, Espressomatic said:

System Temp has a small bug in it which causes the plugin startup script to delete sensors-detect on Unraid 7 betas.

 

# Remove sensors-detect script (Unraid 6.7 and earlier)
source /etc/unraid-version
version=${version:2:2}
if [[ $((${version/./}*1)) -lt 8 ]]; then
  rm -f /usr/sbin/sensors-detect
fi

 

As the above only checks the minor version number, it's evaluating 0 as less than 8 and deleting the script.

 

And once the script is deleted, the plugin can't find any sensors, identify, nor load their drivers .

Looks like there is a PR to fix this
https://github.com/bergware/dynamix/pull/91
but how do we get the sensors-detect script under /usr/sbin back after it's deleted? It is supplied by Unraid and does not come with the Plugin 

Link to comment
9 hours ago, Centurio said:

Looks like there is a PR to fix this
https://github.com/bergware/dynamix/pull/91
but how do we get the sensors-detect script under /usr/sbin back after it's deleted? It is supplied by Unraid and does not come with the Plugin 

For now you can do that, execute the command once and it will be fixed for now:

**REMOVED**

 

PR is already merged, please update the plugin, reboot your servers and it will work as usual.

  • Upvote 1
Link to comment
On 7/9/2024 at 11:12 PM, amix said:

I have exactly that chip, but since the driver, outlined there, is not available fan control does not work for me. Thanks.

Did you already try to install the driver from CA:

grafik.png.80cdf22ac493d5f23aac243873ef793c.png

(please remove all custom things that you maybe applied to the syslinux command line)

  • Thanks 1
Link to comment
15 hours ago, ich777 said:

Did you already try to install the driver from CA:

grafik.png.80cdf22ac493d5f23aac243873ef793c.png

(please remove all custom things that you maybe applied to the syslinux command line)

Holy Moses, there is an addon for that! Thanks so much! I will try asap. Should I remain silent, that will only mean, that I am happy ;-D.

  • Like 1
Link to comment

System Statistics seems to be broken with the v7.0.0 beta.  I just get an empty page when I navigate to the 'Stats' tab.  This is on a system with only a ZFS Pool where the UnRaid Array has been removed.  Possibly the plugin currently needs an UnRaid Array to operate?

 

image.thumb.png.2977aca01e6277fd31a9566d1c12cb60.png

Link to comment
16 minutes ago, ranova said:

Not sure if this can be done, but is there a way to add support for dGPU fan control?

 

short, nope .... GPU fans are by default controlled by their BIOS, software could only control with access to ... which is not given like this on this linux platform, if there would be a cli tool from intel to control the fan, then you could write something together ...

 

sample now with intel tools https://www.oldcai.com/ai/intel-gpu-tools/

 

may write to intel to give some tool to read more, control, ...

Link to comment

Feature request for Fan Auto Control:

Please implement a setting to always autostart. My PMW controller is number 4 in the list, and Fan Auto Control did not start on reboot. Apparently, this is because it only tests the first pmw?

 

Quote

The plugin has an issue where it will only check to see if the first PWM controller is enabled before auto-starting.

So if it’s not enabled then it won’t auto-start, even if others are enabled, which I’m guessing is the issue you’re running into.

The solution I use is to add this to the go file, which will start the plugin regardless:

# Start “Dynamix Auto Fan Control” plugin

/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan ‘start’ &>/dev/null

Link

  • Upvote 1
Link to comment

This did not start autofan when rebooting the server. Does anyone have a better solution I can use? My PMW controller is 4

 

FIXED: 

I changed to using a userscript:

#!/bin/bash
/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan start

 

At first start array only

Edited by Soulplayer
Link to comment

Sorry if it has been asked. I'm also new to unraid. Actually I want to use dynamix stop shell plugin. (already installed) because my unraid won't reboot and the GUI crash (done powerdown -r and it's not work). All I could do is shh. I don't understand how to use this plugin and I couldn't find the tutorial anywhere.  Call me stupid but I've tried for many days. helped would be appreciated

(sorry for my english)

Link to comment
5 hours ago, brutalmethod said:

don't understand how to use this plugin

There is nothing for you to do. The explanation of the plugin is on your Plugins page.

Quote

The Dynamix Stop Shell plugin adds a script which gets invoked when the array is stopped. This script looks for any open shells in /mnt/... and terminate them. This ensures the array can be stopped.

Be aware that automatic terminating of open shells may lead to data loss if an active process is writing to the array.

 

This happens automatically when you stop the array.

  • Like 1
Link to comment
13 hours ago, brutalmethod said:

Sorry if it has been asked. I'm also new to unraid. Actually I want to use dynamix stop shell plugin. (already installed) because my unraid won't reboot and the GUI crash (done powerdown -r and it's not work). All I could do is shh. I don't understand how to use this plugin and I couldn't find the tutorial anywhere.  Call me stupid but I've tried for many days. helped would be appreciated

(sorry for my english)

How long have you waited for the reboot attempt to finish?  Lots of things that can take a while to shut down before it reboots compared to a more typical computer.

  • Like 1
Link to comment

Can you please assist with this issue to do with this driver?,

Or could you advise on another way to get around it, be it a new fan controller?

My current setup
Asus Pro WS WRX90E-SAGE SE

AMD Ryzen Threadripper PRO 7965WX
Noctua NH-D9 TR5-SP6 4U CPU Cooler

Edited by Aedankerr
Didnt list computer parts
Link to comment

hi y'all so i have set up my unraid server to go to sleep, that part goes well.

when i wake it up by wol or with the power button on the tower it start up and just shutdown right after.

I have attached the syslog of the whole wake up shutdown process.

If anyone can help me with that I thank you

best regards

syslog.txt

Link to comment

is the share floor plugin still working with the newest 6.12.11?  I have been running this plugin for almost 2 years and just noticed it is no longer updating the minimum share sizes.  When i run manually the plugin, it immediately reports: "No Shares or Pools updated".  Anyone else seen this before?

 

Thanks,

JD

 

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.

×
×
  • Create New...