Hi. 
 

Anyone having issues with this plugin with a Corsair Commander Pro installed, with interface for the plugin stop listing any sensors and breaking the dashboard temperature and fan values, please see the solution here:

https://github.com/lm-sensors/lm-sensors/issues/369

 

I can confirm it works with the wildcard option. 

 

Files to be changed for a permanent config fix (persisting after a reboot):

>> /etc/sensors.d/sensors.conf

>> /boot/config/plugins/dynamix.system.temp/sensors.conf

 

You can check if the files above are correct if you run "sensors" in the terminal and it responds with all your sensor values.

 

Hope this helps someone.

 

Cheers,

W

On 2/26/2024 at 10: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

 

 

 

It also seems to change the fan input sometimes it's 1 sometimes it's 2. This changed on reboot of course. Now I tried to do a detect, did like 5x, it slows down the fans, meaning its detecting it and goes back to 100%. So something makes it not stick sometimes

On 2/22/2024 at 6:40 PM, Sptz87 said:

I have an issue with auto fan. It looks like upon boot it's not detecting anything. I've set the fans I want to control to 100% in the bios PWM. When I run a "Detect" it detects it correctly, I set my values. If I reboot it shows 0% yet its running at 100%

 

 

If I go back to Auto Fan and try to change any value and save this happens and it also goes missing from System Temp plugin.

 

 

 

I'm having this same issue, where both my fans are showing up in the bottom info bar, and showing the correct tpm, but says 0% next to them. Functionally seems to be working fine, it's just a bug. Did you manage to find a fix?

I have the system temp plugin installed for quite a while. This is my setting (motherboard: Gigabyte B560M AORUS PRO AX), not sure when and how I managed to tune it, but it works:

 

Go file:

...
modprobe it87 force_id=0x8628
...

 

Syslinux config:

 

System temp setting:

 

And the result:

 

All good with the exception I noticed today during boot:

 

Anything strange, misconfigured, weird in my settings (go file mostly)? Is there a correct/better way to setup the drivers needed to have temps and array fan speeds in the GUI?

 

Thanks.

Edited March 2, 20242 yr by Kydonakis

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. 

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

Have you seen the openfancontroller? It may be a better way to go?

https://sasakaranovic.com/projects/openfan-controller/

Available on the unraid app store. 

 

 

On 3/4/2024 at 8:41 PM, dopeytree said:

Have you seen the openfancontroller? It may be a better way to go?

https://sasakaranovic.com/projects/openfan-controller/

Available on the unraid app store. 

 

 

 

Problem with that is the need for an external controller. The point of this is to control fans connected to mobo

Well the solution is to write one's own code to do the task - as the existing solution doesn't function properly. 

Request for feature, a plug in that allows you to display temps from all/any selected sensors detected.

 

corsaircpro-hid-3-2
Adapter: HID adapter
in0:          11.93 V  
in1:           4.94 V  
in2:           3.38 V  
fan1 4pin:   1589 RPM
fan2 4pin:   1643 RPM
fan3 4pin:   1599 RPM
fan4 3pin:   1883 RPM
temp1:        +41.5°C   --- this is the probe stuffed in the LSI heatsink on my server --

the corsair commander pro has 3 or 4 temp sensors. It would be great to monitor probes placed into heatsinks to at least give a little idea of the cooling for tuning the fan plugin. 

 

On 3/8/2024 at 5:39 PM, Sptz87 said:

 

Problem with that is the need for an external controller. The point of this is to control fans connected to mobo

This only works on their board though right? I tried it and it couldn't read my motherboard or corsair controller.

 

After updating Dynamix Auto Fan Control to 2023.02.05a it seems like the Minnimum PWM value is actually now the max PWM value. I had this set to 45  prior and after the update my server will not spin the fans faster than 45% and then my server shutdown due to drives too hot, setting it to 100% seems to work, current fans speed is now 1666 rpm (66%) , thats a lot less than 100%.

Dynamix S3 Sleep plugin is causing issues.

 

Currently running Unraid ver 6.12.4 on both of my Unraid computers. Yesterday I installed Dynamix S3 Sleep plugin that is available via the APPS page on ONE of my Unraid computers.

 

After installing I searched for documentation on how to properly set this plugin up and could find nothing.

 

Link from the MAIN page displays the SLEEP icon and a link to wiki entry that does not work. See screen captures below.

 

However I did find this recommendation in this thread here that I used.

 

 

i set them to these settings. And exited the plugin. Then went back into the settings tab to verify I had saved them. And they were saved.

 

Last night before retiring I pressed the SLEEP icon on the Unraid Dashboard and the server seemed to go to sleep, as I lost my web connection to the server and ALL lights and disk leds were now off.

 

This morning I hit my power button, The computer seemed to awake and all lights and disk leds were no on. There was no usual bootup procedure, So I assumed it was awake.

 

However I could not connect to the server via a browser, nor would it respond to a ping from my Windows 10 computer or Ubuntu pc.

 

So I had to hard reset the beast via the power button.

 

And now it is awake but running a parity check due to the hard reset.

 

I checked the plugin settings this morning and they had returned to the default settings and not the settings I had entered.

 

I checked my log entry for last night to see if the server did in fact go into S3 Sleep mode.

 

I found these entries

 

Mar 17 00:29:00 JUNKYARD s3_sleep: Enter sleep mode
Mar 17 00:29:00 JUNKYARD kernel: PM: suspend entry (deep)
Mar 17 09:27:16 JUNKYARD root: Delaying execution of fix common problems scan for 10 minutes

 

The next after were for this morning.

 

I've removed the plugin until I can find instructions on what are the proper settings to use. I do not want any hard crashes, as this server has been as stable as a finely tuned Chevy small block V8 until installing this plugin.

 

I will NOT be trying this plugin on my other Unraid server.

 

i usually do not have this issue with Dynamix plugins.

 

Frustrated with the lack of documentation and broken link.

 

Cheers & many thanks...

 

 

 

 

Edited March 17, 20242 yr by Vetteman
Correct spelling

16 minutes ago, Vetteman said:

i usually do not have this issue with Dynamix plugins.

 

as alot are using sleep meanwhile ... i wouldnt say its a bad plugin, but what comes into here ...

 

Server Software in combo with alot of Hardware just dont like to suspend to ram and wake ...

 

there is a reason why usually its spoken, Servers dont belong to S3 ...

 

now, there is not much you can adjust or what is correct or wrong, all you setup in the Top belongs when the sleep is auto triggered, sample from my VM Server here (which works flawlessly with sleep, luckily ...)

 

 

so, all you can try now if your Server doesnt repond after awaking ...

 

1/ do you have a monitor attached (or kvm) to check if the local console is up

2/ you can try the force gigabit from the buttom part (to restart the NIC)

 

 

3/ you can try various scripts before / after ... but as mentioned, in the end its usually a hardware issue which just doesnt like S3

 

sorry to say and may be frustrating, but nothing to be upset now vs. anyone ... its a plugin with a feature which may works (or not)

Yes, I do have a kvm switch attach. I did switch to the kvm port the Unraid server was attached to and there was no monitor display, no response from the keyboard. Sorry I did not post this.

 

I also watched SpaceInvader One's youtube video on this plugin 

 

 

Thanks for the reply.

1 hour ago, Vetteman said:

I did switch to the kvm port the Unraid server was attached to and there was no monitor display, no response from the keyboard

then the network reset prolly wont help, if the console would ve been there it would probably solvable ... but if its "stalled" after awaking ... i guess its just not your plugin.

 

sorry to say

Too bad. Prior to running Unraid on this computer, it was a Windows 10 storage pool server and the Windows 10 sleep mode was flawless.

 

I am a bit timid to try this plugin on my other Unraid server for fear of having to do a hard reset resulting in file corruption.

 

Thank you kindly for the replies, much appreciated. Many cheers from Nova Scotia...

2 hours ago, Vetteman said:

Too bad. Prior to running Unraid on this computer, it was a Windows 10 storage pool server and the Windows 10 sleep mode was flawless.

 

I am a bit timid to try this plugin on my other Unraid server for fear of having to do a hard reset resulting in file corruption.

Keep in mind, the plug-in is just a front end for executing sleep commands on a schedule.  If you initiate sleep via the terminal, I strongly suspect you'll have the same issues waking up. 

My old system had major problems with its HBA card after waking from S3 sleep. The issue was fixed after updating my motherboard to the newest BIOS.  So I suggest seeing if updating all your firmware fixes the issue.

I am initiating sleep via the sleep button the plugin generates. My motherboard does have the latest bios.

Cheers

6 hours ago, Vetteman said:

I am a bit timid to try this plugin on my other Unraid server for fear of having to do a hard reset resulting in file corruption.

 

well, you shouldnt use sleep anyhow while file transfers are running ... also a reason in the setup page of this plugin to say wait until no array activity ...

 

i guess you missmatch 2 things now and feared about the parity check which starts after each unclean shutdown.

 

as sample note, when you test something, make sure your array aint moving files around ... when you are aware of this, after a unclean shutdown, just cancel the parity check as its just triggered automatically ... and let it run again on your regular next schedule ....

 

a unclean shutdown doesnt automatically mean there is any corruption, its just a default behaviour to make sure everything is ok to run the parity sync ...thats it  my HDD's would have bean teared down if i always would have run the parity sync after a unclean shutdown in my test scenarios

 

but to make it clear, is it safer, yes, is it needed when you know there was no array activity at all while the unclean shutdown happened, no.

 

i hope you understand what i mean

8 hours ago, alturismo said:

well, you shouldnt use sleep anyhow while file transfers are running ... also a reason in the setup page of this plugin to say wait until no array activity ...

 

i guess you missmatch 2 things now and feared about the parity check which starts after each unclean shutdown.

 

as sample note, when you test something, make sure your array aint moving files around ... when you are aware of this, after a unclean shutdown, just cancel the parity check as its just triggered automatically ... and let it run again on your regular next schedule ....

 

a unclean shutdown doesnt automatically mean there is any corruption, its just a default behaviour to make sure everything is ok to run the parity sync ...thats it  my HDD's would have bean teared down if i always would have run the parity sync after a unclean shutdown in my test scenarios

 

but to make it clear, is it safer, yes, is it needed when you know there was no array activity at all while the unclean shutdown happened, no.

 

i hope you understand what i mean

 

Thanks for the clarification. Since I am the only user of my Unraid servers, I can assure you there was no file activity. The primary use of Unraid is to store my digital photos I've taken (both RAW and processed JPGs & PSDs), 3d models and digital illustrations I've created. I also store backups of my movie & tv DVD shows. and music CDs.

 

I am a retired system admin who administered Novell Netware, Windows, Novell SUSE and Citrix Winframe servers. Whenever a Novell volume was not cleanly dismounted it seems it resulted in file corruption. At least as far as I can recall. Now 70 and have been retired for 5 years, so some stuff is a little foggy. 🙂

 

Most of my computer time now is learning 3D modeling in Blender & 3D Coat and digital illustration techniques with Photoshop, Vue Creator, DAZ Studio, Corel Painter, Rebelle 7, etc.

 

I truly appreciate your reply.

On 2/26/2024 at 11: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

 

 

 

To restart the autofan service after a reboot you can add a script that runs on "At Startup of Array" using the User Scripts app from the community store
 

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

 

Hi Everyone, I am new to Unraid and I have a AsRock Z690 ITX motherboard but I am not able to figure out which one of these is the motherboard temperature to use in the plugin

So the system information plugin says I have "Model: Lenovo H320".. Although the rest of the information is correct.  Thi sis not a Lenovo.  I upgraded to a custum built comptuer quite some time ago.  How do I make it rescan?

On 12/1/2014 at 6:40 AM, bonienl said:

System Temp

 

 

It has been working just fine for many years. But I was so stupid to reinstall it cuz of another problem I tried to find.

Now when I click detect, its find the driver, and then I can see the list of sensors, I chose 1 for cpu and 1 for MB, then click apply, then I it just change to Not Used, and the list is no more. I need to reintall and reboot to get the list back, but the same keep happon.

 

Any idea?

 

 

After clicking APPLY

 

Edited March 31, 20242 yr by ChillZwix