I am hoping a Good Samaritan can help me on my way to setting my share floors appropriately.  I downloaded the plug in and set it up in scheduler.  I tried some arbitrary minimum floor settings but I have no idea what I am doing and my log is still full of "shfs: share cache full".   I searched for documentation but have found nothing.  Can anyone give me a few pointers?  Thanks!

 

 

1 hour ago, The Transplant said:

I searched for documentation but have found nothing.  Can anyone give me a few pointers?  Thanks!

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#minimum-free-space

22 hours ago, JorgeB said:

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#minimum-free-space

 

Thanks -  don't understand how the plugin works?  I see in the log that it was installed.  I set it up for daily.  My understanding is that it runs every day and assesses the files and sets the floor accordingly?  Yet it doesn't appear to be doing anything at this time.  Also, if it sets the floor based on the largest file it finds then why does it have a space for minimum?  Is that so I can ensure it doesn't go below a certain value?  And if so what should I set that to if I am depending on it to set the values accordingly?

52 minutes ago, The Transplant said:

 

Thanks -  don't understand how the plugin works?  I see in the log that it was installed.  I set it up for daily.  My understanding is that it runs every day and assesses the files and sets the floor accordingly?  Yet it doesn't appear to be doing anything at this time.  Also, if it sets the floor based on the largest file it finds then why does it have a space for minimum?  Is that so I can ensure it doesn't go below a certain value?  And if so what should I set that to if I am depending on it to set the values accordingly?

should be double the size of the largest file you will be storing. and cache should be moved to the array daily at the latest

The plugin will just adjust the floor from now on for new files. if you had your min free space too low in the past and your cache is already overfilled it won't do anything about that.

It's a preventative measure, not a fix for when things are already wrong.

Edited March 6, 20251 yr by Kilrah

6 hours ago, spl147 said:

should be double the size of the largest file you will be storing. and cache should be moved to the array daily at the latest

I started on this journey to stop my log filling up with this message "shfs: share cache full".  I deduce this is caused by the minimum free space on my cache?  It's set to 50GB.  It seems that a lot of my minimums are set to 50GB - perhaps a default.  So I am not sure I need to be adjusting the minimum free space on the shares?

 

I guess basically I want to know how to get rid of this warning.  Thanks.

On 1/31/2025 at 10:40 AM, spl147 said:

stop fan control, delete dynamix.system.autofan2.cfg rename dynamix.system.autofan1.cfg to dynamix.system.autofan.cfg, remove the line from the go script. then reboot, then start fan control

It worked for me too, but I noticed that now the case fan (the one controlled by Autofan) no longer shows the (%) of RPM, just the RPM. Instead, the CPU fan (controlled by BIOS) that is not configured in Autofan, shows RPM and (%)

Hi there,

 

I'm running Unraid 7.0.0 on a Ryzen 5 4600G. When I first installed, I installed Dynamic System Temperature and it detected drivers automatically. I could see CPU and mainboard temperatures, among others.

 

At some point, after a restart or two, all temperatures have disappeared. Now, I go into the plugin, click "detect," and it returns no results.

 

I can run sensors-detect, but that returns the same result.

 

I have reseated the CPU fan header to no avail. Temperatures are being reported to BIOS just fine. I do some heavy workloads and have recently moved to a new case and cooling setup, so really need to know what my temperatures are looking like.

 

The problem has persisted across Unraid 7.0.0 and 7.0.1.

I run Unraid 7.0.1 and wanted to report that for my system, having "isolcpus=0-1" in the boot options caused the Sleep / WOL functions to stop working. The system was hanging on a WOL command, independently of the NIC.

I had to uninstall all plugins, reset everything, and try to set things back one by one, resetting bios, and so on.

Only took me 8H to figure out it was this simple cpu isolation configuration.

It's unrelated to this plugin, but it's where the information will likely be the most useful.

I don't remember adding that option recently, so it could be an update and hardware specific issues that makes it not compatible anymore. Either case, if it can save someone some headache... It's worth checking :).

Edited March 10, 20251 yr by dboris

Dynamix Auto Fan Control

 

I can get the fans controlled, Fan1 - Blows on my drives, Fan2 - Is one of the Case Fans Fan 3: The fan over my AMD 7945 APU.

 

I am having an issue when my drives go idle, the temps drop and the fans stop even though I have the lowest setting to be 15%.  I have had 3 random system shutdowns, that I believe (but not sure) are due to the APU getting hot because Fan 3 stops.

 

I have tried to disable the fan control for Fan 3, but then it runs at 100% non-stop.  Before I installed the fan control plugin, I believe the motherboard was automatically controlling the speed for that fan.  How can I restore this functionality?  Or how can I make it so Fan 3 never goes completely idle?  APU temps getting over 100c when fans go idle.

Edited March 13, 20251 yr by rbarr110

47 minutes ago, rbarr110 said:

Before I installed the fan control plugin, I believe the motherboard was automatically controlling the speed for that fan.  How can I restore this functionality?

should stay BIOS controlled as long you are not configuring it in the plugin, removing fan3 config ... reboot ...

 

48 minutes ago, rbarr110 said:

Or how can I make it so Fan 3 never goes completely idle? 

may some way (same page upper post)

 

48 minutes ago, alturismo said:

should stay BIOS controlled as long you are not configuring it in the plugin, removing fan3 config ... reboot ...

 

may some way (same page upper post)

 

Thank you for the reply, especially the REBOOT part.  Fan appears to be being controlled again by the motherboard.

7 minutes ago, rbarr110 said:

especially the REBOOT part.

yep, once the OS took control its hard to give control back to BIOS without a reboot

20 hours ago, rbarr110 said:

even though I have the lowest setting to be 15%.

It's common for fans to need at least 30-35% to start/keep running, need to test with yours.

SYSTEM AUTOFAN

 

I've been using this for a while, following a MOBO change, I have been diving more into its operation.

 

I have 2 Fans on drives. The top is on a block of 5 array drives, the bottom is on a block of 5 drives the parity, a passed drive and an SSD pool. The MOBO has 2xNVME Drives on it.

 

I was expecting the plugin to:

check the top fan PWM3 drives as set in the 'exclude drives' and set that fan

THEN

check the bottom fan on PWM4 drives again as set in 'exclude drives' and set that fan.

 

The script seams to check all the drives not excluded and then set both fans. For example in my have SDH and SDK are at the bottom so should only be on PWM4 ... PWM3 drives are all spun down so should be at 0%

 

Note: I have modified the script to report the max temp drive and fan controller to find this

 

Question : should the plugin separately control each fan based on the drives included in that PWM group?

 

 

 

1 hour ago, MrAndyBurns said:

SYSTEM AUTOFAN

 

I've been using this for a while, following a MOBO change, I have been diving more into its operation.

 

I have 2 Fans on drives. The top is on a block of 5 array drives, the bottom is on a block of 5 drives the parity, a passed drive and an SSD pool. The MOBO has 2xNVME Drives on it.

 

I was expecting the plugin to:

check the top fan PWM3 drives as set in the 'exclude drives' and set that fan

THEN

check the bottom fan on PWM4 drives again as set in 'exclude drives' and set that fan.

 

The script seams to check all the drives not excluded and then set both fans. For example in my have SDH and SDK are at the bottom so should only be on PWM4 ... PWM3 drives are all spun down so should be at 0%

 

Note: I have modified the script to report the max temp drive and fan controller to find this

 

Question : should the plugin separately control each fan based on the drives included in that PWM group?

 

 

 

not many fans can do 0% 27% seems to be your lowest

10 minutes ago, spl147 said:

not many fans can do 0% 27% seems to be your lowest

That's true, I was possibly expecting a full stop at 0% as the drives were off.

 

I've also noticed that I'm not actually able to exclude Unassigned drives as they are not in the list ... just looking at options to see if I can include those

1 minute ago, MrAndyBurns said:

That's true, I was possibly expecting a full stop at 0% as the drives were off.

 

I've also noticed that I'm not actually able to exclude Unassigned drives as they are not in the list ... just looking at options to see if I can include those

Just go to the config file to add them

1 hour ago, spl147 said:

Just go to the config file to add them

Thanks @spl147, I did put it in the /boot/config/plugins/dynamix.system.autofan PWM config file, it didn't work and then got overwritten when I restated the service to see if this fixed it... just checked a few hours later and it did work, but then it has litterally just picked up the excluded drive again ... I'll continue to monitor 🤪

5 minutes ago, MrAndyBurns said:

Thanks @spl147, I did put it in the /boot/config/plugins/dynamix.system.autofan PWM config file, it didn't work and then got overwritten when I restated the service to see if this fixed it... just checked a few hours later and it did work, but then it has litterally just picked up the excluded drive again ... I'll continue to monitor 🤪

the plugin is kinda half baked, and doesnt get enough attention to be honest, a board with IPMI is the way to go for full fan control

The Auto Fan Control plugin does not recognize the correct maximum temperature?!

 

 

EDIT: Ok, this is really bad:

1 hour ago, mgutt said:

The Auto Fan Control plugin does not recognize the correct maximum temperature?!

 

 

EDIT: Ok, this is really bad:

post your settings page

3 hours ago, spl147 said:

post your settings page

After disable and enable the first sensor it works as expected again. Settings:

 

I would say the plugin does not recognize hot swapped disks?!

 

4 minutes ago, mgutt said:

After disable and enable the first sensor it works as expected again. Settings:

 

I would say the plugin does not recognize hot swapped disks?!

 

Your refresh interval is way to long, 5 mins between checks could overheat a drive, especially during a parity check. 1 min. max

11 hours ago, spl147 said:

especially during a parity check

I already tested this. No problem so far as those QVO SSDs have a low power consumption and in addition the default airflow keeps them already cool enough. But I repeat the test next week as then 6 additional SSDs will be connected since the last test.

 

Is there a specific reason why the Auto Fan plugin does not use the CPU temps? I would like to use all temp sensors.