1 hour ago, Squid said:

Which plugin?

Oh sorry, the autofan plugin.

S3 Sleep

Since update to 7.1.2 I am getting many errors just before server goes to sleep should I be concerned? Server is working ok just wondering about the errors.

May 24 00:08:31 Media-Server kernel: Call Trace:
May 24 00:16:21 Media-Server kernel: Call Trace:
May 24 00:35:53 Media-Server kernel: Call Trace:
May 24 00:44:09 Media-Server kernel: Call Trace:
May 24 01:01:57 Media-Server kernel: Call Trace:
May 24 01:12:13 Media-Server kernel: Call Trace:
May 24 01:20:55 Media-Server kernel: Call Trace:
May 24 01:34:26 Media-Server kernel: Call Trace:
May 24 01:45:19 Media-Server kernel: Call Trace:

May 21 22:06:05 Media-Server kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
May 22 22:05:46 Media-Server kernel: Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:08:31 Media-Server kernel: Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:16:21 Media-Server kernel: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:35:53 Media-Server kernel: Freezing user space processes failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 00:44:09 Media-Server kernel: Freezing user space processes failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:01:57 Media-Server kernel: Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:12:13 Media-Server kernel: Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:20:55 Media-Server kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:34:26 Media-Server kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
May 24 01:45:19 Media-Server kernel: Freezing user space processes failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):

Server gui unresponsive, unable to SSH (connection refused), and console commands dont return anything. Local consoles shows the following lines repeating:

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

xxxxxxxlogin: root

Unraid Server OS version: 7.1.2

IPv4 address: 192.xxxxxxxx

IPv6 address: not set

wireless network: not set

it let me attempt to login but would just return the unraid version lines and not ask for a password then just continue repeating the exit codes. shutdown/restart commands returned nothing and then it eventually stopped letting me even try to login.

On 5/25/2025 at 4:59 PM, HiImAWalrus said:

Server gui unresponsive, unable to SSH (connection refused), and console commands dont return anything. Local consoles shows the following lines repeating:

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

crond[22671]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sal 1 1 &> /dev/null

xxxxxxxlogin: root

Unraid Server OS version: 7.1.2

IPv4 address: 192.xxxxxxxx

IPv6 address: not set

wireless network: not set

it let me attempt to login but would just return the unraid version lines and not ask for a password then just continue repeating the exit codes. shutdown/restart commands returned nothing and then it eventually stopped letting me even try to login.

Assuming you've already rebooted to fix, if it happens again from the console can you grab the diagnostics (they'll be saved on the flash drive) and also the output of this command:

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

Small bit of feedback: I would personally have the icon in the header follow the colour scheme of the other icons. The red is too "error"/"attention required", especially with the Unraid notification bell icon applying colour codes on top of the bell to indicate status. It doesn't follow the current design language, IMO.

Regarding the Autofan plugin -> For me it works again after update to Unraid 7.1.3 🙂

On 5/29/2025 at 1:57 PM, Squid said:

Assuming you've already rebooted to fix, if it happens again from the console can you grab the diagnostics (they'll be saved on the flash drive) and also the output of this command:

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

happened again today, I cant grab the diagnostics before hard resetting because console commands are unresponsive while in this state. Do you still want them? Im gonna replace my flash drive because i found some users saying that was the fix for a similar issue.

this time it said this repeating:

"crond[2298]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null"

Here is the output of the command:

total 165

35 drwxr-xr-x 2 root root 881 May 1 08:14 ./

34 drwxr-xr-x 1 root root 120 Jun 6 12:41 ../

5204 -rwxr-xr-x 1 root root 434 Nov 15 2023 agent*

5205 -rwxr-xr-x 1 root root 229 Nov 15 2023 bootmode*

5206 -rwxr-xr-x 1 root root 420 Nov 15 2023 btrfs_balance*

5207 -rwxr-xr-x 1 root root 1397 Jun 6 2024 btrfs_check*

5208 -rwxr-xr-x 1 root root 819 Nov 15 2023 btrfs_scrub*

5209 -rwxr-xr-x 1 root root 775 Nov 15 2023 console*

5210 -rwxr-xr-x 1 root root 37808 May 1 08:14 diagnostics*

5211 -rwxr-xr-x 1 root root 774 Nov 15 2023 disk_size*

5212 -rwxr-xr-x 1 root root 489 Nov 15 2023 emcmd*

5213 -rwxr-xr-x 1 root root 728 Feb 16 06:55 error_interfaces*

5214 -rwxr-xr-x 1 root root 13602 Apr 4 06:37 feedback*

5215 -rwxr-xr-x 1 root root 1693 Nov 15 2023 flash_backup*

5216 -rwxr-xr-x 1 root root 577 Nov 15 2023 ftpusers*

5217 -rwxr-xr-x 1 root root 2399 Nov 15 2023 install_key*

5218 -rwxr-xr-x 1 root root 15620 Jun 28 2024 monitor*

5219 -rwxr-xr-x 1 root root 6538 Feb 25 19:38 netconfig*

5220 -rwxr-xr-x 1 root root 2703 Sep 21 2024 newperms*

5221 -rwxr-xr-x 1 root root 849 Jan 8 19:04 nfsSettings*

5222 -rwxr-xr-x 1 root root 9915 Feb 16 06:55 notify*

5223 -rwxr-xr-x 1 root root 1282 Apr 21 14:00 open_ssl*

5224 -rwxr-xr-x 1 root root 3390 Dec 16 14:58 outgoingproxy*

5225 -rwxr-xr-x 1 root root 1154 Nov 15 2023 parity_control*

5226 -rwxr-xr-x 1 root root 3150 Feb 5 2024 parity_history*

5227 -rwxr-xr-x 1 root root 141 Dec 29 2023 powermode*

5228 -rwxr-xr-x 1 root root 676 Oct 10 2024 reiserfs_check*

5229 -rwxr-xr-x 1 root root 371 Feb 17 11:00 reload_services*

5230 -rwxr-xr-x 1 root root 649 Feb 5 2024 replace_key_job*

5231 -rwxr-xr-x 1 root root 677 Mar 25 19:29 restore_favorites*

5232 -rwxr-xr-x 1 root root 3583 Feb 16 2024 rsyslog_config*

5233 -rwxr-xr-x 1 root root 1437 Nov 15 2023 run_cmd*

5234 -rwxr-xr-x 1 root root 2967 Feb 5 2024 select_case*

5235 -rwxr-xr-x 1 root root 4182 Jul 16 2024 set_proxy*

5236 -rwxr-xr-x 1 root root 826 Nov 15 2023 share_size*

5237 -rwxr-xr-x 1 root root 269 Jul 26 2024 show_interfaces*

5238 -rwxr-xr-x 1 root root 4272 Feb 27 10:26 ssd_trim*

5239 -rwxr-xr-x 1 root root 8080 Mar 22 2024 statuscheck*

5240 -rwxr-xr-x 1 root root 10104 Feb 25 07:45 system_information*

5241 -rwxr-xr-x 1 root root 1771 Apr 21 14:00 update_access*

5242 -rwxr-xr-x 1 root root 369 Feb 17 11:00 update_services*

5243 -rwxr-xr-x 1 root root 1602 Nov 15 2023 upnp_poller*

5244 -rwxr-xr-x 1 root root 104 Nov 15 2023 upnp_poller_start*

5245 -rwxr-xr-x 1 root root 1334 Nov 15 2023 upnp_port*

5246 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config*

5247 -rwxr-xr-x 1 root root 1649 Mar 31 11:27 wireless*

5248 -rwxr-xr-x 1 root root 2640 Jun 30 2024 xfs_check*

5249 -rwxr-xr-x 1 root root 518 Nov 15 2023 zfs_scrub*

On 4/22/2025 at 2:25 PM, kaneda79 said:

@mattalat I temporarily solved the problem following the solution provided by @spl147 

 

Sadly is not working anymore. Only a manual intervention restores the fan behaviour. Probably something changed after the last unraid update.

Update 7.1.3 brought back Dynamix autofan to work properly. I have reapplied @spl147 solution and Lincstation N1 fan is doing is job after any reboot.

On 6/11/2025 at 11:05 AM, kaneda79 said:

Update 7.1.3 brought back Dynamix autofan to work properly. I have reapplied @spl147 solution and Lincstation N1 fan is doing is job after any reboot.

when it works properly on 7.1.3 why did you reapply the @spl147 solution then?

System Temp can't detect, driver is missing and couldn't find it. ITE IT8613E
I'm using AOOSTAR WTR PRO AMD Ryzen 7 5825u 4 Bay Nas Mini PC

any idea?

2 hours ago, AD-963 said:

System Temp can't detect, driver is missing and couldn't find it. ITE IT8613E
I'm using AOOSTAR WTR PRO AMD Ryzen 7 5825u 4 Bay Nas Mini PC

any idea?

your answer is right here:

Driver

"to-be-written':

* ISA bus, address 0xa30

Chip 'ITE IT8613E Super IO Sensors' (confidence: 9)

Note: there is no driver for ITE IT8613E Super IO Sensors yet.

Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Hi All. I noticed that for the Dynamix System Temp plugin it requires Perl. I also saw a note about it being needed for V6 and below? Maybe?

I do not see a package or plugin for PERL. Is this what everyone is noticing? Are we installing temporarily via CLI?

Thanks for your input.

Been automatically installed by the plugin for quite a while, don't need to care about it.

Thank you. I installed the System Temp Plugin. All I could find now is the settings page which seems to be showing whatever 2 temps I selected...I don't see anything that resembles temperature meters or a reporting module for the dashboard.

Is the settings page the only info output from the plugin?

Thanks for the help...

plugin is not starting automatically on 7.1.4. it needs a manual user input to start.

Gotcha…what is the manual user input?

Hey there,

can someone explain the autofan plugin? I get more than 5 pwm controllers listed... how can i see and adjust all of them? Does the plugin only support one?

Regarding Autofan I have again some issues with unraid 7.1.4. Maybe it was also before the case.
It seems like the temp of "nvmeXnX" drives is not correctly detected. For my sata ssd drives temp retrieving works.

In the logs I can only see 0C for the nvme drives:

autofan: Highest disk temp is 0C, adjusting fan speed from: FULL (100% @ 4753rpm) to: OFF (0% @ 0rpm)

autofan: Highest disk temp is 0C, adjusting fan speed from: FULL (100% @ 5000rpm) to: OFF (0% @ 0rpm)

autofan: Highest disk temp is 27C, adjusting fan speed from: FULL (100% @ 2227rpm) to: OFF (0% @ 0rpm)

Hi guys, I installed the autofan plugin but it doesn't show any PWM controller, my motherboard is: Asus B550-XE

Is this normal?

Thanks!

i had to install the driver package to see my pwms, but ive got some and i dont know how to control all of them instead of just one

Check for the ITE IT87 Driver - maybe that applies to your mainboard, too

On 6/26/2025 at 5:01 PM, Alessio.B87 said:

Hi guys, I installed the autofan plugin but it doesn't show any PWM controller, my motherboard is: Asus B550-XE

Is this normal?

Thanks!

run sensors-detect from the commandline, and post the output

Does Factory Reset leave a log file?

I just used it (and it fixed my ethernet not coming up), but it didn't preserve my pools (did preserve the array) and it deleted my go file (so the web server wasn't up). I can fix the things I've found wrong, but want to see precisely what it changed.

Don't have a recent backup of the drive to compare with?

Hello,

I just installed the plugin but no PWM controller is detected.

In my BIOS, I have set both the CPU FAN and SYS_FAN2 to PWM mode. SYS_FAN2 is connected to three PWM fans.

However, nothing is being detected by the plugin.

Any ideas or suggestions would be much appreciated!

Thank you!

1 hour ago, Achlyss said:

Hello,

I just installed the plugin but no PWM controller is detected.

In my BIOS, I have set both the CPU FAN and SYS_FAN2 to PWM mode. SYS_FAN2 is connected to three PWM fans.

However, nothing is being detected by the plugin.

Any ideas or suggestions would be much appreciated!

Thank you!

Have you run sensors-detect?

Edited July 9, 2025Jul 9 by spl147