Hi,

 

I´m trying run Dynamix System Autofan on MSI 460M Mortar, but cannot see properly the fans and show the error below:

 

 

"<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6687.2592/hwmon/hwmon3/fan3_input"

 

I could added the driver NCT6687-isa-0a20 to the GO file in the startup and the temperature for MB and CPU are working fine.

 

I will appreciate any help

 

Maybe a temporary solution:

 

1- Create a folder (/boot/pwmfan)

2- run sensors (In my unraid now I have just one 8TB drive, the temp is showing for me over nvme-pci-0200, sensor 2)

3- run pwmconfig and folow the process for PWM search, the location of the folder (/boot/pwmfan) will need to save the settings.

4- Create a script to run in the background:

        "

#!/bin/bash
#Folder location
cd /boot/pwmfan

#Action 

fancontrol pwmcfg.LyjaWtS8mI

"

 

Edited February 23, 20215 yr by lgil

Is there something I can do to get all temperature monitors for my ASUS ROG STRIX B550-E GAMING motherboard?

This is the only thing I am getting:

 

I think the three k10temp are all CPU temperature but I'm not sure. They are almost always exactly the same. I would really like to also get motherboard temperature.

UPDATE - Fixed 3/13 in plugin update.  Thanks!

 

s3 sleep is broken in Unraid 6.9.0.

Snippet from log - - - - - - - - - - - -

Mar 2 16:04:49 htserv s3_sleep: version=3.0.7

Mar 2 16:04:49 htserv s3_sleep: ----------------------------------------------

Mar 2 16:04:49 htserv s3_sleep: included disks=

Mar 2 16:04:49 htserv s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl

Mar 2 16:04:49 htserv s3_sleep: ----------------------------------------------

Mar 2 16:04:49 htserv s3_sleep: s3_sleep process ID 30890 started, To terminate it, type: s3_sleep -q

- - - - - - - -

Wait for array is set to Yes, exclude cache - cache is sdi.

Array goes to sleep after timeout even though disks are in use.

Plugin worked in 6.8.3.

 

Any thoughts?

 

 

Edited March 19, 20215 yr by drcos
Fixed - Bergware 3/13 update

 

20 hours ago, drcos said:

s3 sleep is broken in Unraid 6.9.0.

Wait for array is set to Yes, exclude cache - cache is sdi.

Array goes to sleep after timeout even though disks are in use.

Plugin worked in 6.8.3.

Any thoughts?

 

Its not broken, just "vice versa" 😉

You can fix this.

If the sleep plug-in is active, you can enter all drives (which you want to monitor) under "Monitor disks outside array:"

There is something "the other way around" - but it is working 😉👍

It seems the plugin does not recognise the array correctly (last update from 6.2020)

 

 

 

Edited March 3, 20215 yr by Zonediver

Hi All,

 

I've been patiently waiting for 6.9 to come out so that i could get my temps and fans working on my ryzen system.

 

I have a ryzen 3600 & ROG STRIX B450-I MB.

 

I managed to get the temps working but the PWM fans arent being recognised.

 

I installed Noctua case fans and CPU fan.

 

Heres my temp set-up in Dynamix System Temperature

 

 

And here what i see in Dynamix Auto Fan Control

 

 

 

Any help would be great.!

 

Cheers

 

D.

Edited March 3, 20215 yr by Big Dan T

On 3/3/2021 at 10:42 AM, Zonediver said:

 

 

Its not broken, just "vice versa" 😉

You can fix this.

If the sleep plug-in is active, you can enter all drives (which you want to monitor) under "Monitor disks outside array:"

There is something "the other way around" - but it is working 😉👍

It seems the plugin does not recognise the array correctly (last update from 6.2020)

 

 

 

I will try that and if it works we will call it the Costanza solution.

-EDIT- The Costanza solution works.

 

 

Edited March 6, 20215 yr by drcos

Hi All,
 
I've been patiently waiting for 6.9 to come out so that i could get my temps and fans working on my ryzen system.
 
I have a ryzen 3600 & ROG STRIX B450-I MB.
 
I managed to get the temps working but the PWM fans arent being recognised.
 
I installed Noctua case fans and CPU fan.
 
Heres my temp set-up in Dynamix System Temperature
 

 
And here what i see in Dynamix Auto Fan Control
 
 

 
Any help would be great.!
 
Cheers
 
D.

You need to run “sensors detect” from the command line to see what drivers you need to load

51 minutes ago, spl147 said:

You need to run “sensors detect” from the command line to see what drivers you need to load

 

I'm guessing this is my problem:-

 

Quote

Driver `to-be-written':
  * ISA bus, address 0x290
    Chip `ITE IT8665E Super IO Sensors' (confidence: 9)

 

 

Yep.

Will the SSD TRIM work for m.2 SSD's in the parity & data disk slots or just cache slots?

1 hour ago, Econaut said:

or just cache slots?

This.

On 2/14/2021 at 7:39 PM, rsutter said:

I believe my UNRAID is being spammed:
root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token

 

I received this on another forum post:

Is it expected to have connections from the US, the UK, Russia, Kazakstan, Lithuania, ?

Unraid is not hardened and is not supposed to face the Internet directly.

 

What can I do to stop this?

 

when i get this error message is usually a browser windows that has a unraid server console session before you did a reboot. Do a close all browsers and see then

 

Hi,

 

any update for the drive NCT6687? When I try to use the Autofan plugin and press detect, the below message show up:

 

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6687.2592/hwmon/hwmon3/fan3_input

 

Any help to fix this?

 

Also checking the file location:

 

Edited March 9, 20215 yr by lgil

On 1/8/2021 at 1:01 PM, mikeyosm said:

I'm getting permission denied in autofan plugin.... Any ideas why? The plugin is detecting my sensor chip nct6683 OK.

 

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>43</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>46</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>49</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6683.2592/hwmon/hwmon3/fan2_input

 

 

Hi Mikeyosm,

 

have you been able to fix the permission denied issue? If yes, could you please share with me?

 

Thank you,

Luis Gil

Sleep plugin issue (ignoring array disks) persists in Unraid 6.9.1.

Costanza solution still working.

My No.1 feature request for the Auto Fan Plugin is to have the option to name the detected fans individually.

In the System Temp Plugin it would be appreciated as well and on the Dashboard Widget.

 

After some days I always forget, which one was for what.  Startin' to get old  

 

Would be great if you consider this as a useful new feature.

 

kind regards from Berlin

Edited March 9, 20215 yr by locutus_lbc

6 minutes ago, locutus_lbc said:

My No.1 feature request for the Auto Fan Plugin is to have the option to name the detected fans individually.

In the System Temp Plugin it would be appreciated as well and on the Dashboard Widget.

 

After some days I always forget, which one was for what.  Startin' to get old  

 

Would be great if you consider this as a useful new feature.

 

kind regards from Berlin

 

Agreed, this and for auto fan to automatically start when the unraid boots / the array is started.

 

I have to manually go into it and make a mundane change to get it to start.

Just now, TexasUnraid said:

 

Agreed, this and for auto fan to automatically start when the unraid boots / the array is started.

 

I have to manually go into it and make a mundane change to get it to start.

 

Agreed as well!!

 

+1 for the Auto Start Option with Server or Array Start...

I'm using a custom script to check and/or restart like it was suggested here in the forums.

 

Would be great to get rid of this

20 minutes ago, locutus_lbc said:

 

Agreed as well!!

 

+1 for the Auto Start Option with Server or Array Start...

I'm using a custom script to check and/or restart like it was suggested here in the forums.

 

Would be great to get rid of this

 

Got a link to said script?

26 minutes ago, TexasUnraid said:

 

Got a link to said script?

 

I made something custom for my use case out of this template:

https://gist.github.com/kidpixo/04d61b42221f6bc8489b

 

1 hour ago, TexasUnraid said:

 

Got a link to said script?

 

or you might want to add a script like this to your custom script plugin and run it after array has started:

 

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

 

you can test it before in your console

 

kind regards

Edited March 9, 20215 yr by locutus_lbc

5 minutes ago, locutus_lbc said:

 

or you might want to add something like this to your custom script which runs after array has started:

 

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

 

you can test it before in your console

 

kind regards

 

Perfect, I have a script that runs at array start already, I will toss this in there.

1 hour ago, locutus_lbc said:

 

I made something custom for my use case out of this template:

https://gist.github.com/kidpixo/04d61b42221f6bc8489b

 

Hi, thank you for the link.

 

I´m really bad on this, but I did try made some changes and the script put the PWM3 at 150 and show the error below:

"Script location: /tmp/user.scripts/tmpScripts/FanSpeed/script
Note that closing this window will abort the execution of this script
Linear PWM Range is 150 to 255 in 9 increments of 11

hdparm - get/set hard disk parameters - version v9.60, by Mark Lord.

clue=11
Usage: hdparm [options] [device ...]

Options:
-a Get/set fs readahead
-A Get/set the drive look-ahead flag (0/1)
-b Get/set bus state (0 == off, 1 == on, 2 == tristate)
-B Set Advanced Power Management setting (1-255)
-c Get/set IDE 32-bit IO setting
-C Check drive power mode status
-d Get/set using_dma flag
-D Enable/disable drive defect management
-E Set cd/dvd drive speed
-f Flush buffer cache for device on exit
-F Flush drive write cache
-g Display drive geometry
-h Display terse usage information
-H Read temperature from drive (Hitachi only)
-i Display drive identification
-I Detailed/current information directly from drive
-J Get/set Western DIgital "Idle3" timeout for a WDC "Green" drive (DANGEROUS)
-k Get/set keep_settings_over_reset flag (0/1)
-K Set drive keep_features_over_reset flag (0/1)
-L Set drive doorlock (0/1) (removable harddisks only)
-m Get/set multiple sector count
-M Get/set acoustic management (0-254, 128: quiet, 254: fast)
-n Get/set ignore-write-errors flag (0/1)
-N Get/set max visible number of sectors (HPA) (VERY DANGEROUS)
-p Set PIO mode on IDE interface chipset (0,1,2,3,4,...)
-P Set drive prefetch count
-q Change next setting quietly
-Q Get/set DMA queue_depth (if supported)
-r Get/set device readonly flag (DANGEROUS to set)
-R Get/set device write-read-verify flag
-s Set power-up in standby flag (0/1) (DANGEROUS)
-S Set standby (spindown) timeout
-t Perform device read timings
-T Perform cache read timings
-u Get/set unmaskirq flag (0/1)
-U Obsolete
-v Use defaults; same as -acdgkmur for IDE drives
-V Display program version and exit immediately
-w Perform device reset (DANGEROUS)
-W Get/set drive write-caching flag (0/1)
-x Obsolete
-X Set IDE xfer mode (DANGEROUS)
-y Put drive in standby mode
-Y Put drive to sleep
-z Re-read partition table
-Z Disable Seagate auto-powersaving mode
--dco-freeze Freeze/lock current device configuration until next power cycle
--dco-identify Read/dump device configuration identify data
--dco-restore Reset device configuration back to factory defaults
--dco-setmax Use DCO to set maximum addressable sectors
--direct Use O_DIRECT to bypass page cache for timings
--drq-hsm-error Crash system with a "stuck DRQ" error (VERY DANGEROUS)
--fallocate Create a file without writing data to disk
--fibmap Show device extents (and fragmentation) for a file
--fwdownload Download firmware file to drive (EXTREMELY DANGEROUS)
--fwdownload-mode3 Download firmware using min-size segments (EXTREMELY DANGEROUS)
--fwdownload-mode3-max Download firmware using max-size segments (EXTREMELY DANGEROUS)
--fwdownload-mode7 Download firmware using a single segment (EXTREMELY DANGEROUS)
--fwdownload-modee Download firmware using mode E (min-size segments) (EXTREMELY DANGEROUS)
--fwdownload-modee-max Download firmware using mode E (max-size segments) (EXTREMELY DANGEROUS)
--idle-immediate Idle drive immediately
--idle-unload Idle immediately and unload heads
--Iraw filename Write raw binary identify data to the specfied file
--Istdin Read identify data from stdin as ASCII hex
--Istdout Write identify data to stdout as ASCII hex
--make-bad-sector Deliberately corrupt a sector directly on the media (VERY DANGEROUS)
--offset use with -t, to begin timings at given offset (in GiB) from start of drive
--prefer-ata12 Use 12-byte (instead of 16-byte) SAT commands when possible
--read-sector Read and dump (in hex) a sector directly from the media
--repair-sector Alias for the --write-sector option (VERY DANGEROUS)
--sanitize-antifreeze-lock Block sanitize-freeze-lock command until next power cycle
--sanitize-block-erase Start block erase operation
--sanitize-crypto-scramble Change the internal encryption keys that used for used data
--sanitize-freeze-lock Lock drive's sanitize features until next power cycle
--sanitize-overwrite PATTERN Overwrite the internal media with constant PATTERN
--sanitize-status Show sanitize status information
--security-help Display help for ATA security commands
--set-sector-size Change logical sector size of drive
--trim-sector-ranges Tell SSD firmware to discard unneeded data sectors: lba:count ..
--trim-sector-ranges-stdin Same as above, but reads lba:count pairs from stdin
--verbose Display extra diagnostics from some commands
--write-sector Repair/overwrite a (possibly bad) sector directly on the media (VERY DANGEROUS)

/tmp/user.scripts/tmpScripts/FanSpeed/script: line 79: [: : integer expression expected

hdparm - get/set hard disk parameters - version v9.60, by Mark Lord.

clue=11
Usage: hdparm [options] [device ...]

Options:
-a Get/set fs readahead
-A Get/set the drive look-ahead flag (0/1)
-b Get/set bus state (0 == off, 1 == on, 2 == tristate)
-B Set Advanced Power Management setting (1-255)
-c Get/set IDE 32-bit IO setting
-C Check drive power mode status
-d Get/set using_dma flag
-D Enable/disable drive defect management
-E Set cd/dvd drive speed
-f Flush buffer cache for device on exit
-F Flush drive write cache
-g Display drive geometry
-h Display terse usage information
-H Read temperature from drive (Hitachi only)
-i Display drive identification
-I Detailed/current information directly from drive
-J Get/set Western DIgital "Idle3" timeout for a WDC "Green" drive (DANGEROUS)
-k Get/set keep_settings_over_reset flag (0/1)
-K Set drive keep_features_over_reset flag (0/1)
-L Set drive doorlock (0/1) (removable harddisks only)
-m Get/set multiple sector count
-M Get/set acoustic management (0-254, 128: quiet, 254: fast)
-n Get/set ignore-write-errors flag (0/1)
-N Get/set max visible number of sectors (HPA) (VERY DANGEROUS)
-p Set PIO mode on IDE interface chipset (0,1,2,3,4,...)
-P Set drive prefetch count
-q Change next setting quietly
-Q Get/set DMA queue_depth (if supported)
-r Get/set device readonly flag (DANGEROUS to set)
-R Get/set device write-read-verify flag
-s Set power-up in standby flag (0/1) (DANGEROUS)
-S Set standby (spindown) timeout
-t Perform device read timings
-T Perform cache read timings
-u Get/set unmaskirq flag (0/1)
-U Obsolete
-v Use defaults; same as -acdgkmur for IDE drives
-V Display program version and exit immediately
-w Perform device reset (DANGEROUS)
-W Get/set drive write-caching flag (0/1)
-x Obsolete
-X Set IDE xfer mode (DANGEROUS)
-y Put drive in standby mode
-Y Put drive to sleep
-z Re-read partition table
-Z Disable Seagate auto-powersaving mode
--dco-freeze Freeze/lock current device configuration until next power cycle
--dco-identify Read/dump device configuration identify data
--dco-restore Reset device configuration back to factory defaults
--dco-setmax Use DCO to set maximum addressable sectors
--direct Use O_DIRECT to bypass page cache for timings
--drq-hsm-error Crash system with a "stuck DRQ" error (VERY DANGEROUS)
--fallocate Create a file without writing data to disk
--fibmap Show device extents (and fragmentation) for a file
--fwdownload Download firmware file to drive (EXTREMELY DANGEROUS)
--fwdownload-mode3 Download firmware using min-size segments (EXTREMELY DANGEROUS)
--fwdownload-mode3-max Download firmware using max-size segments (EXTREMELY DANGEROUS)
--fwdownload-mode7 Download firmware using a single segment (EXTREMELY DANGEROUS)
--fwdownload-modee Download firmware using mode E (min-size segments) (EXTREMELY DANGEROUS)
--fwdownload-modee-max Download firmware using mode E (max-size segments) (EXTREMELY DANGEROUS)
--idle-immediate Idle drive immediately
--idle-unload Idle immediately and unload heads
--Iraw filename Write raw binary identify data to the specfied file
--Istdin Read identify data from stdin as ASCII hex
--Istdout Write identify data to stdout as ASCII hex
--make-bad-sector Deliberately corrupt a sector directly on the media (VERY DANGEROUS)
--offset use with -t, to begin timings at given offset (in GiB) from start of drive
--prefer-ata12 Use 12-byte (instead of 16-byte) SAT commands when possible
--read-sector Read and dump (in hex) a sector directly from the media
--repair-sector Alias for the --write-sector option (VERY DANGEROUS)
--sanitize-antifreeze-lock Block sanitize-freeze-lock command until next power cycle
--sanitize-block-erase Start block erase operation
--sanitize-crypto-scramble Change the internal encryption keys that used for used data
--sanitize-freeze-lock Lock drive's sanitize features until next power cycle
--sanitize-overwrite PATTERN Overwrite the internal media with constant PATTERN
--sanitize-status Show sanitize status information
--security-help Display help for ATA security commands
--set-sector-size Change logical sector size of drive
--trim-sector-ranges Tell SSD firmware to discard unneeded data sectors: lba:count ..
--trim-sector-ranges-stdin Same as above, but reads lba:count pairs from stdin
--verbose Display extra diagnostics from some commands
--write-sector Repair/overwrite a (possibly bad) sector directly on the media (VERY DANGEROUS)

/tmp/user.scripts/tmpScripts/FanSpeed/script: line 79: [: : integer expression expected
Highest temp is: 0
/tmp/user.scripts/tmpScripts/FanSpeed/script: line 90: /sys/class/hwmon/hwmon3/device/hwmon/hwmon3/pwm3_enable: Permission denied
Setting pwm to: 30"

 

Also in the folder /sys/class/hwmon/hwmon3/device/hwmon/hwmon3, i don´t have any permission and pwm3_enable is not present

 

Any of you ever run into the following message? Just started showing up. It goes away once I uninstall the sleep plugin and reappears every time I reinstall it.

 

 
Agreed, this and for auto fan to automatically start when the unraid boots / the array is started.
 
I have to manually go into it and make a mundane change to get it to start.

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