[Dynamix - V6 Plugins]

On 2/26/2024 at 5:58 AM, dopeytree said:

 

I was playing with this plugin the other day before a new build. It seems to work but does the bug where it shows blank.

 

Also it includes any unassigned drives and I couldn't quite workout the code to exclude them.

 

It doesnt seem to activate itself after a reboot. So you seem to have to go in choose the PWM fan and click apply again. Then the fan should spin down from your bios default 100%.

 

The plugin definitely needs some work.

 

I've changed tract and am just using bios and a manual fan controller at 50%.

 

If you do want to control from within unraid I'd suggest maybe using a usb controller and liquid CTL instead of this plugin

 

 

I've also noticed very odd behavior and it not working correctly after restart if PWM1 isn't set to "Enabled" in the plugin - even if it's not being used.  I've had to enable PWM1 and leave it all blank for it to work on reboot.  Unfortunately I have not been able to figure what is causing this..

 

 

20 hours ago, Nirin said:

Dynamix Fan Control

 

Currently in the log it's showing that the 'hottest drive' is 48c, and it setting the speed of the fan appropriately. Fine. 

 

However the hottest drive is actually 65c (it's an NVME) which I was going to set to ignore anyway as the fan doesn't cool that drive, but it seems dynamix is ignoring it anyway (even though I haven't ticked the 'ignore' option in the settings for fan control). 

 

The hottest hard drive though... is only 40c. So it's not those that it's looking at either. 

 

The drive that is 48c is a sata ssd, which isn't in the array or mounted, and which isn't available in the 'ignore' list for control fan. So Dynamix seems to be registering and tracking the temps of drives not in the array, but only allows you to ignore drives that -are- in the array? 

 

Seems like a bug. Two bugs actually, as it's also ignoring the nvme for no reason. So it's ignoring one drive it shouldn't, and tracking one drive it shouldn't. 

 

A few of us reported the NVME ignore bug a while back...  I'm not great at *nix scripting - or how to fix it, but did narrow it down to WHY.  The problem is how it's interpreting an errorcode from SDSPIN.  There was a problem a while back where it would spinup drives when polling drives, so it checks first to see if it's spun up.  Standard HDDs return a 0 or 1 - NVMe drives return something else, and the autofan plugin is only looking for 0 or 1.  Here's the bugreport on Git: https://github.com/bergware/dynamix/issues/83

[[Support] devzwf - iVentoy]

Thanks for putting this docker together!  It's working great except one thing I have noted:

 

When I attempt to stop the container it will not stop correctly. I get an "Execution Error" popup from GUI about 1 minute after clicking stop (timeout is 60s) and it shows "Exited (137)" as the status.  It starts back up fine though, so I'm not sure if anything is actually "broke" here.

[Dynamix - V6 Plugins]

Somewhere along the lines I lost the percentage next to the RPM in the footer for System Temp.  In the syslog I can see:

 

autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 2492rpm) to: 114 (44% @ 1354rpm)

 

But in the Unraid footer I see the fan RPM and a 0% next to it all the time.  Any suggestions on what to check for this?  It looks like the system temperature plugin is supposed to pull the percentage from autofan, but it's getting a 0.

[Dynamix - V6 Plugins]

10 hours ago, KrisMin said:

Since pool discs temperature is not reported while disks are spinned down and I have System AutoFan tied to discs temperature, the fans are stopping. I need them to be in min rpm while discs are down. Would you consider adding this as a feature (checkbox or something) ?

You need to set the "Minimum PWM Value" to something high enough to keep them spinning.  That's how I fixed mine, you might have to play with the value to find what works. 255 is "Max" - 65 works well for my system.

[[Support] Linuxserver.io - Emby]

Thanks for looking at it saarg.  I tried linuxserver/emby:amd64-beta and that gave me the correct 4.5.0.13 version.  Tried just "beta" again and it rolled back to 4.4.3.0.  I opened "advanced" in docker and hit "force update" on the beta tag and then it switched back to 4.5.0.13...  Weird, dunno if there was something cached somewhere but that appears to have resolved it.

[[Support] Linuxserver.io - Emby]

Could someone tell me if I am doing something wrong trying to update the beta version on this docker?  If I set the repository to: linuxserver/emby:beta it for some reason reverts me back to the 4.4.3.0 version of Emby.  If I use linuxserver/emby:4.5.0.13-ls48 or linuxserver/emby:4.5.0.12-ls46 it will install the correct version.  I'm definitely not a docker expert, but in looking at the "digest" numbers it seems like just the "beta" tag should be working.

[Recommend NIC for unRAID]

I've had problems with Realtek NICs not always being able to hit full gigabit speeds when heavily loaded.  Intel and Broadcom are two widely used NICs in the enterprise server area and I've used both with unRAID without issue.  You can usually pick up a PRO/1000 PT PCIe card on eBay for $15 or less.  Sometimes you can find the newer Intel i350 cards for around $30.  Either one would be more than good enough for an unRAID system.  Just make sure it has the right height bracket on it!