3 minutes ago, spl147 said:

Auto fan does start automatically on system boots if the config file is set to enabled. Mine starts every time unraid starts, check the plugin folder for auto fan make sure the config file is correct

 

It is set to enabled in the GUI but does not actually take control of the fans until I make a change.

 

I checked the config/plugin folder but just see files listing out the settings for each fan and a .txz file. Where is the config file you are talking about?

13 minutes ago, TexasUnraid said:

 

It is set to enabled in the GUI but does not actually take control of the fans until I make a change.

 

I checked the config/plugin folder but just see files listing out the settings for each fan and a .txz file. Where is the config file you are talking about?

/flash/config/plugins/dynamix.system.autofan/dynamix.system.autofan.cfg

 

here is the contents of mine:

 

options="-c /sys/devices/platform/nct6775.656/hwmon/hwmon3/pwm4 -f /sys/devices/platform/nct6775.656/hwmon/hwmon3/fan4_input -l 150 -t 35 -T 45 -m 1"
service="1"
controller="/sys/devices/platform/nct6775.656/hwmon/hwmon3/pwm4"
fan="/sys/devices/platform/nct6775.656/hwmon/hwmon3/fan4_input"
pwm="150"
low="35"
high="45"
interval="1"
exclude=""

 

 

13 minutes ago, spl147 said:

/flash/config/plugins/dynamix.system.autofan/dynamix.system.autofan.cfg

 

here is the contents of mine:

 

options="-c /sys/devices/platform/nct6775.656/hwmon/hwmon3/pwm4 -f /sys/devices/platform/nct6775.656/hwmon/hwmon3/fan4_input -l 150 -t 35 -T 45 -m 1"
service="1"
controller="/sys/devices/platform/nct6775.656/hwmon/hwmon3/pwm4"
fan="/sys/devices/platform/nct6775.656/hwmon/hwmon3/fan4_input"
pwm="150"
low="35"
high="45"
interval="1"
exclude=""

 

 

Odd, I have 6 files, one for each fan controller in my system.

 

Some of them I have disabled as I want the bios to control them (CPU fans) which includes channel 1. The others are enabled and show in the cfg files but it does not autostart.

 

Does it only check the first channel to see if it should autostart the whole service?

Odd, I have 6 files, one for each fan controller in my system.
 
Some of them I have disabled as I want the bios to control them (CPU fans) which includes channel 1. The others are enabled and show in the cfg files but it does not autostart.
 
Does it only check the first channel to see if it should autostart the whole service?

Make sure the main config file has service=“1”

24 minutes ago, spl147 said:

Make sure the main config file has service=“1”

Yeah, I figured that was the case but if I do that then autofan will try to control PWM1 which I do not want. Same as if I set it to enable in the GUI I am guessing.

 

I have PWM1 set to disabled in the GUI for this reason but have PWM 3-6 set to enabled. This works fine if I manually start the service by making a mundane change but it does not auto-start.

 

I am guessing that it is only checking PWM1 to see if it should be enabled instead of checking all the cfg files.

1 minute ago, TexasUnraid said:

Yeah, I figured that was the case but if I do that then autofan will try to control PWM1 which I do not want. Same as if I set it to enable in the GUI I am guessing.

 

I have PWM1 set to disabled in the GUI for this reason but have PWM 3-6 set to enabled. This works fine if I manually start the service by making a mundane change but it does not auto-start.

 

I am guessing that it is only checking PWM1 to see if it should be enabled instead of checking all the cfg files.

so you have dynamix.system.autofan.cfg disabled then dynamix.system.autofan-1.cfg or something like that?

 

delete the ones you don't use and rename the first used one to dynamix.system.autofan.cfg, and set service="1" iand the others to 1,2,3, etc. and reboot

5 minutes ago, spl147 said:

so you have dynamix.system.autofan.cfg disabled then dynamix.system.autofan-1.cfg or something like that?

 

delete the ones you don't use and rename the first used one to dynamix.system.autofan.cfg, and set service="1" iand the others to 1,2,3, etc. and reboot

 

Tried that but it just moved the settings up 2 slots, so my PWM 6 settings became PWM 4 settings. etc.

 
Tried that but it just moved the settings up 2 slots, so my PWM 6 settings became PWM 4 settings. etc.

I would set plugin to default, delete all configs and start over

1 minute ago, spl147 said:

I would set plugin to default, delete all configs and start over

 

I already did that early on when I was trying to figure out why it was not controlling the fans before I figured out making a mundane change would get it working. It didn't change anything.

 

Pretty sure it only checks the first cfg file to see if it should start the service, since I don't want that one enabled, it doesn't start it.

10 minutes ago, TexasUnraid said:

 

I already did that early on when I was trying to figure out why it was not controlling the fans before I figured out making a mundane change would get it working. It didn't change anything.

 

Pretty sure it only checks the first cfg file to see if it should start the service, since I don't want that one enabled, it doesn't start it.

open a issue on the github page.

 

i had the same issue a wihle back, deleting everything and starting over fixed it for me, but i only have 1 config file, i use a fan hub and connect to 1 fan header

I don't know even know how to find the github page and have never really used github outside of downloading stuff from it. No idea how to properly open an issue. Still very new to linux.

 

If the start script above works, that should be good enough for now.

5 minutes ago, TexasUnraid said:

I don't know even know how to find the github page and have never really used github outside of downloading stuff from it. No idea how to properly open an issue. Still very new to linux.

 

If the start script above works, that should be good enough for now.

i opened the issue for you and referenced you here

Hi, i like this plugin so much, but i have no idea why i cannot exclude a USB Harddisk that i have mounted over unassigned devices plugin. Any Help?

Edited March 10, 20215 yr by AndreasNe

On 3/10/2021 at 12:18 AM, TexasUnraid said:

I don't know even know how to find the github page and have never really used github outside of downloading stuff from it. No idea how to properly open an issue. Still very new to linux.

 

If the start script above works, that should be good enough for now.

 

On 3/10/2021 at 12:24 AM, spl147 said:

i opened the issue for you and referenced you here

 

thx for your help in this case. i can confirm what @TexasUnraid said. same behavior on my side.

i just deleted the files where service=0 and will see if this helps.

 

i just noticed over night that the service again stopped but I was pretty sure that I ran the command before going to bed. In the morning the service said "stopped", after restarting manually again I saw just some minutes ago that the service stopped again from itself.

 

don't know if this relates to @TexasUnraid's assumption that the first file has to have a service=1 in that folder. So I tried your suggestion with deleting all files with service=0... let's see if the service is stable now.

 

do you have an idea how to check via console if the service is running or not and than maybe fire up the 'start' command as cron every 5min? This would also help i guess but bash scripting and me are no good friends

 

edit:

 

I also put in the name of my nvme drive in the exclude list (in my case it is 'nvme0n1')... let's see if this prevents the fans from getting info from the wrong drive.

Edited March 11, 20215 yr by locutus_lbc

I can confirm that the bash script line above ran at array start works good for getting autofan running with my existing settings and all fans are controlled as I have them setup in the GUI.

3 hours ago, TexasUnraid said:

I can confirm that the bash script line above ran at array start works good for getting autofan running with my existing settings and all fans are controlled as I have them setup in the GUI.

 

And I can confirm that it actually works to exclude NVME devices, when you add them directly to the config file.

 

BUT be careful with the UI... the setting will not be shown if you add a NVME device in the config AND the config file will be overwritten, if you change something in the GUI (so the NVME drive is gone).

 

before changing the file via terminal please be sure that the service has stopped.

to kill all services run:

 

/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan -q

 

maybe you have to run it more than once. for me it just stopped only one instance of the service. I have 2 fan controllers configured.

Check with 'htop' if everything stopped, otherwise kill them in 'htop'.

 

after that change your config file with:

 

nano /flash/config/plugins/dynamix.system.autofan/dynamix.system.autofan*.cfg

 

replace the * with your corresponding config file.

 

In the config file I changed two lines... 

Here is an example of one of my controllers config with a NVME devices excluded. 

 

options="-c /sys/devices/platform/nct6775.656/hwmon/hwmon3/pwm4 -f /sys/devices/platform/nct6775.656/hwmon/hwmon3/fan2_input -l 30 -t 30 -T 40 -m 1 -e sdp,nvme0n1"
service="1"
controller="/sys/devices/platform/nct6775.656/hwmon/hwmon3/pwm4"
fan="/sys/devices/platform/nct6775.656/hwmon/hwmon3/fan2_input"
pwm="30"
low="30"
high="40"
interval="1"
exclude="sdp,nvme0n1"

 

Please notice that I changed it once in the 'exclude' parameter (last line) and once in the 'options' parameter which constructs the service I guess.

 

Restart your service with:

/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan restart

or

/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan start

 

I saw here in the forums that some people had also problems excluding there NVME devices.

 

Hope that the developer will take care of it, but it seems that there is a workaround until then.

 

Kind regards from Berlin

Edited March 11, 20215 yr by locutus_lbc

Hi, autofan has stopped working after upgrading to 6.9.1 it was working fine in 6.9.0 and all the betas and RC's. Its annoying as finally my drives spin down and now something else is broken. Not sure what info is needed but I have this in syslinux: acpi_enforce_resources=lax and this in my GO file: modprobe it87 force_id=0x8628

Hopefully someone knows what has changed to stop this working?

Cheers, Tim

Hello, 

 

I just received my server and have been installing pluggins to get myself going.

I have an issue with Autofan where when I click on detect for pwm fan and minimum pwm value I obtain this error :

 

<br /><b>Warning</b>:  file_put_contents(): Only -1 of 1 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>69</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 1 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>70</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 1 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>71</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 1 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 1 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 2 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>76</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br /><br /><b>Warning</b>:  A non-numeric value encountered in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>78</b><br />

 

I have 62 GB free on /usr...

The free space it's talking about isn't anything to do with your system.  Rather for some reason the sensors aren't accepting the changes the plugin is trying to make to the fan speeds.  

It has been some time since I visited the Unraid forums.

Due to health issues I had to take a break, and unfortunately this break took way longer than anticipated.

But I am back and will start giving support again to Unraid and plugins.

 

First step is an update to the s3_sleep plugin, which now supports the latest features of Unraid 6.9 properly.

Please update this plugin if you are running Unraid 6.9.0 or higher.

 

I need to do a lot of catching up, but feel free to post issues with the Dynamix plugins here and I will look into it.

 

Edited March 13, 20215 yr by bonienl

34 minutes ago, bonienl said:

It has been some time since I visited the Unraid forums.

Good to see you back! And hope you're feeling better.

11 hours ago, Squid said:

The free space it's talking about isn't anything to do with your system.  Rather for some reason the sensors aren't accepting the changes the plugin is trying to make to the fan speeds.  

 

 

That is weird, cause although it returns this error message, it does change the speed of the fans. Let's say the fan is revving at 6000 rpm before, then I click detect, it returns this error on the line, but then the fans rev down to a more natural 2000 rpm.

15 hours ago, bonienl said:

It has been some time since I visited the Unraid forums.

 

Hello bonienl and nice that you are back again.

I thought something bad had happened.

I wish you all the best for your recovery 👍👍👍

Edited March 13, 20215 yr by Zonediver

Hello,

 

I have a bit of a problem with the S3 Plugin, the log shows:

 

Mar 14 11:30:57 NAS s3_sleep: ----------------------------------------------
Mar 14 11:30:57 NAS s3_sleep: s3_sleep process ID 7685 started, To terminate it, type: s3_sleep -q
Mar 14 11:30:57 NAS s3_sleep: Disk activity on going: sdb
Mar 14 11:30:57 NAS s3_sleep: Disk activity detected. Reset timers.
Mar 14 11:31:57 NAS s3_sleep: Disk activity on going: sdb
Mar 14 11:31:57 NAS s3_sleep: Disk activity detected. Reset timers.

 

The problem is, that sdb is spun down and not doing anything. This behaviour appears randomly on SSDs and HDDs. There is nothing scheduled (mover, paritiy etc.) or polling (sata, autofan) in one minute steps. Also the file activity plugin shows nothing. What is wrong here?

 

 

@limetechUpdate:

It seems that the problem has something to do with the intentionally broken SSD standby since 6.9.

When SSDs are set into standbymode via console (hdparm -y), then it works as intended. Right now I'm not able to get back the spindown (=standby) command for SSDs from Unraid 6.8.3, since there is no comment or help on this decision from the developers. That's kind of a dealbreaker, since many chipsets (including mine) go into the lowest C-States, when drives remain active.

 

Thanks in advance

Edited April 3, 20215 yr by TGP

On 3/13/2021 at 9:28 AM, bonienl said:

It has been some time since I visited the Unraid forums.

Due to health issues I had to take a break, and unfortunately this break took way longer than anticipated.

But I am back and will start giving support again to Unraid and plugins.

 

First step is an update to the s3_sleep plugin, which now supports the latest features of Unraid 6.9 properly.

Please update this plugin if you are running Unraid 6.9.0 or higher.

 

Really good to see you back on board, but take your time.

Nothing is more important than your health.

 

 

On 3/13/2021 at 9:28 AM, bonienl said:

I need to do a lot of catching up, but feel free to post issues with the Dynamix plugins here and I will look into it.

 

That sounds great. If you have time, please have a look 1-2 pages back as some of us discussed several issues with and wishes for the Auto Fan Plugin:

- Feature Request: add NVME devices to exclude list via GUI, cause they influence the measurements of the spinning drives (works if manually added to cfg file, but will be overwritten if changes in the GUI are made)

- Feature Request: have the option to give every fan an individual name in Auto Fan - and System Temp Plugin

- possible Bug: if first cfg file in the plugin folder has service="0" the auto fan services does not start on boot/array start or crashes/stopps (workaround: delete all cfg files with service="0" in it)

 

If you need more details on this feel free to contact me. Until than... Stay save, stay healthy

 

kind regards from berlin

Edited March 15, 20215 yr by locutus_lbc
typos and more specific information