Hey. Not sure if it's been brought up here or if it's just an issue on my end, but the sensor display for the Dynamix System Temperature plugin has a misspelling of the word 'Processor'. It's currently spelt 'Procesor'.

Ok, so I've read through all of this, and a ton of other threads. And I can't find my question..

 

Everything shows up fine in sensors detect

 

Only 2 of the PWN fans listed in the dropdown have anything on detect

 

 

How do I tell which physical fan is which? Or are they the same fan?

 

Also, how do I make sure it's controlling the array fans and not the CPU fan. The CPU fans on the water cooler works fine, I don't want to adjust that. But I have a new setup of fans coming for my Array and I want to control that. But I'm confused how I know which fan is which... I did see people asking to be able to label them, but I'm not even sure how to figure out which fan each input is so I could label them if we had that ability. 

I've got everything set up as i want it with autofan and it works well for me on my Supermicro X9SCM-F for what it matters i also have the following plugins:

 

IPMI (configured with fan control off) and

SYSTEM TEMP (which sees my sensors and controllers)

 

However, Everytime i have to reboot, i have to manually change out and put back the 'PWM FAN' value in the plugin to force the plugin talk to the controller and manage the speed.

 

My BIOS fan controller is set to 'FULL' as i've read that the bios dosn't fight for control of PWM control if it's set like this. If i just reboot unraid and login, the array fans (that i manage with autofan) will be running at 100% until i do the disable/renable, detect process. 

 

Is it likely that the plugin needs to be forced to refresh it's values prior to starting after a fresh reboot on the X9 platform so that it fights for control of PWM from the BIOS? If so, could this be added?

 

Secondly, Am i right in thinking the plugin dosnt display the highest disk temp in the unraid footnote? My autofan plugin simply displays:

 

CPU (temp)/ Mainboard (temp)/ Array Fan (%) but the footnote dosnt tell me what the disk temp is! As this plugin adjusts fans based on disk temp would it not make sense to display the disk temp?  

 

I'd like to get to the bottom of what i need to do to avoid the re-enable/redetect every reboot before the plugin takes control. Ive tried uninstalling and reinstalling and manually clearing out all the old .cfg files for the plugin. But nothing has worked.

 

Cheers for the hardwork this plugin was def needed. Hope someone can shed some light.

Edited February 10, 20224 yr by thestraycat

"SSD TRIM

allows the creation of a cronjob to do regular SSD TRIM operations on the cache device(s). The command 'fstrim -v /mnt/cache' is executed at the given interval."

 

Does it do all cache drives/pools or only /mnt/cache?

 

Thank you

16 minutes ago, wibble said:

Does it do all cache drives/pools or only /mnt/cache?

 

all cache drives/pools, from the syslog ...

 

Feb 15 05:22:09 AlsServer root: /etc/libvirt: 51.8 MiB (54353920 bytes) trimmed on /dev/loop2
Feb 15 05:22:09 AlsServer root: /mnt/vms: 447.5 GiB (480543584256 bytes) trimmed on /dev/nvme1n1p1
Feb 15 05:22:09 AlsServer root: /mnt/cache: 467.4 GiB (501819392000 bytes) trimmed on /dev/nvme0n1p1

 

setting

 

nvme devices 

Hi - I've just installed an SSD to use as a cache and installed the Dynamix Trim plugin too. I've set it up, but is there a way to tell whether it has completed successfully on schedule (is there a log I can access easily)? Thanks in advance.

6 hours ago, PitRejection2359 said:

but is there a way to tell whether it has completed successfully on schedule (is there a log I can access easily)? Thanks in advance.

if you take a look 1 Post upper your question ... 

 

its in the syslog, just search for "trimmed" ...

if you take a look 1 Post upper your question ... 
 
its in the syslog, just search for "trimmed" ...

Thank you!

Sent from my SM-G965F using Tapatalk

Hi guys, I have a problem with Fan Auto Control.
My MB: MSI B460m with community driver installed for nct6687.

Unraid: 6.9.2

 

When I press detect it shows:

 

Quote

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/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/nct6687.2592/hwmon/hwmon2/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/nct6687.2592/hwmon/hwmon2/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/nct6687.2592/hwmon/hwmon2/fan1_input

How can I make this control work? Fans are in full power.

 

Regards.

 

Edited February 17, 20224 yr by emersonicus

On 2/10/2022 at 5:34 AM, thestraycat said:

I've got everything set up as i want it with autofan and it works well for me on my Supermicro X9SCM-F for what it matters i also have the following plugins:

 

IPMI (configured with fan control off) and

SYSTEM TEMP (which sees my sensors and controllers)

 

However, Everytime i have to reboot, i have to manually change out and put back the 'PWM FAN' value in the plugin to force the plugin talk to the controller and manage the speed.

 

My BIOS fan controller is set to 'FULL' as i've read that the bios dosn't fight for control of PWM control if it's set like this. If i just reboot unraid and login, the array fans (that i manage with autofan) will be running at 100% until i do the disable/renable, detect process. 

 

Is it likely that the plugin needs to be forced to refresh it's values prior to starting after a fresh reboot on the X9 platform so that it fights for control of PWM from the BIOS? If so, could this be added?

 

Secondly, Am i right in thinking the plugin dosnt display the highest disk temp in the unraid footnote? My autofan plugin simply displays:

 

CPU (temp)/ Mainboard (temp)/ Array Fan (%) but the footnote dosnt tell me what the disk temp is! As this plugin adjusts fans based on disk temp would it not make sense to display the disk temp?  

 

I'd like to get to the bottom of what i need to do to avoid the re-enable/redetect every reboot before the plugin takes control. Ive tried uninstalling and reinstalling and manually clearing out all the old .cfg files for the plugin. But nothing has worked.

 

Cheers for the hardwork this plugin was def needed. Hope someone can shed some light.

Can anyone help? Can i add a line to my unraid config to issue the command "PWM FAN = 40" on startup? That would at least be a workaround.... 

So I am still trying to figure this out.

I detect, save and load coretemp nct6683 driver, but no fans are detected and not all temps are available. cpu and some others are missing

 

Then I unload the driver, go to terminal an type modprobe nct6683 force=1. Go back to system temp and now all temps are avaliable. The missing temps are now listed with NCT6687 in front of them.

 

After restart the setting are gone.

 

So I added this to the go file. From my understanding it is supposed to force unraid to load more sensors etc on boot.

echo "options nct6683 force=1" >> /etc/modprobe.d/sensors.conf

 

By looking in the sensors.conf after reboot I see all the stuff that is missing listed there

 

chip "nct6687-isa-0a20"
ignore "fan1"
chip "nct6687-isa-0a20"
ignore "fan2"
chip "nct6687-isa-0a20"
ignore "fan3"
chip "nct6687-isa-0a20"
ignore "fan4"
chip "nct6687-isa-0a20"
label "temp4" "CPU Temp"
chip "acpitz-acpi-0"
label "temp1" "MB Temp"

 

So how can I make this available after boot? What am I doing wrong?

 

After reboot:

After unload driver and "modprobe nct6683 force=1" in terminal

 

Edited February 23, 20224 yr by ProphetSe7en

I have a single BTRFS cache drive is the TRIM app still recommended?  How often do you recommend to run it?

Squid:  Thanks for all of the amazing work on these.

 

Can I throw in a feature request to have System Autofan log which fan it is adjusting?   If you want to go further allowing us to add friendly names for each fan such as:   "CPU Fan", "Top Exhaust", etc.

 

Thanks.

I'm having problems with the s3_sleep plugin

 

appears to initiate sleep mode but fails after a few seconds

 

this is my configuration

 

root@Tower:~# cat /boot/config/plugins/dynamix.s3.sleep/dynamix.s3.sleep.cfg 
options="-C 1 -a -c -f 1 -m 40 -e eth0 -N 125000 -D 2"
service="1"
stopDay=""
stopHour=""
checkHDD="-a -c"
hdparm="-f 1"
timeout="40"
checkTCP=""
port="eth0"
idle="125000"
pingIP=""
login=""
setWol=""
preRun=""
postRun=""
forceGb=""
dhcpRenew=""
debug="2"

 

 

and here the debug in syslog

 

Mar  6 18:05:58 Tower s3_sleep: Enter sleep mode
Mar  6 18:05:58 Tower s3_sleep: Enter sleep state now
Mar  6 18:05:58 Tower kernel: PM: suspend entry (deep)
Mar  6 18:05:58 Tower kernel: Filesystems sync: 0.024 seconds
Mar  6 18:06:19 Tower kernel: Freezing user space processes ... 
Mar  6 18:06:19 Tower kernel: Freezing of tasks failed after 20.000 seconds (1 tasks refusing to freeze, wq_busy=0):
Mar  6 18:06:19 Tower kernel: task:smbd            state:D stack:    0 pid:15682 ppid: 14383 flags:0x00004004
Mar  6 18:06:19 Tower kernel: Call Trace:
Mar  6 18:06:19 Tower kernel: __schedule+0x45e/0x4a4
Mar  6 18:06:19 Tower kernel: schedule+0x73/0x99
Mar  6 18:06:19 Tower kernel: request_wait_answer+0xfa/0x1e7
Mar  6 18:06:19 Tower kernel: ? init_wait_entry+0x24/0x24
Mar  6 18:06:19 Tower kernel: fuse_simple_request+0x1b5/0x1f0
Mar  6 18:06:19 Tower kernel: fuse_dentry_revalidate+0x13f/0x297
Mar  6 18:06:19 Tower kernel: lookup_fast+0xd0/0x110
Mar  6 18:06:19 Tower kernel: walk_component+0x63/0x107
Mar  6 18:06:19 Tower kernel: link_path_walk+0x246/0x2cf
Mar  6 18:06:19 Tower kernel: ? memcg_slab_free_hook+0x40/0xfc
Mar  6 18:06:19 Tower kernel: path_lookupat.isra.0+0x45/0x10b
Mar  6 18:06:19 Tower kernel: filename_lookup+0x7c/0xdf
Mar  6 18:06:19 Tower kernel: ? fuse_change_attributes+0xab/0x115
Mar  6 18:06:19 Tower kernel: ? make_kgid+0xe/0xf
Mar  6 18:06:19 Tower kernel: ? getname_flags+0x24/0x146
Mar  6 18:06:19 Tower kernel: ? kmem_cache_alloc+0x108/0x130
Mar  6 18:06:19 Tower kernel: ? getname_flags+0x44/0x146
Mar  6 18:06:19 Tower kernel: vfs_statx+0x72/0x105
Mar  6 18:06:19 Tower kernel: __do_sys_newstat+0x30/0x62
Mar  6 18:06:19 Tower kernel: ? do_fcntl+0x1b7/0x586
Mar  6 18:06:19 Tower kernel: ? __do_sys_fcntl+0x53/0x70
Mar  6 18:06:19 Tower kernel: do_syscall_64+0x5d/0x6a
Mar  6 18:06:19 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar  6 18:06:19 Tower kernel: RIP: 0033:0x150539de6d76
Mar  6 18:06:19 Tower kernel: RSP: 002b:00007ffee7ed45a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000004
Mar  6 18:06:19 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000150539de6d76
Mar  6 18:06:19 Tower kernel: RDX: 00007ffee7ed45b0 RSI: 00007ffee7ed45b0 RDI: 000056290ac835a0
Mar  6 18:06:19 Tower kernel: RBP: 00007ffee7ed4870 R08: 0000000000000001 R09: 0000000000000001
Mar  6 18:06:19 Tower kernel: R10: 000015053a3fe836 R11: 0000000000000246 R12: 00007ffee7ed475c
Mar  6 18:06:19 Tower kernel: R13: 00007ffee7ed45b0 R14: 000056290acb7150 R15: 0000000000000000
Mar  6 18:06:19 Tower kernel: 
Mar  6 18:06:19 Tower kernel: OOM killer enabled.
Mar  6 18:06:19 Tower kernel: Restarting tasks ... done.
Mar  6 18:06:19 Tower kernel: PM: suspend exit
Mar  6 18:06:19 Tower s3_sleep: Wake-up now
Mar  6 18:06:19 Tower s3_sleep: Wake-up from sleep mode
Mar  6 18:06:26 Tower webGUI: Successful login user root from 192.168.2.254

 

Edited March 6, 20224 yr by SimoneM1988

For the system buttons app can we also get optional buttons to enable/disable docker, and VMs.  And also Mover I find myself doing this than shutting down.

On 3/3/2022 at 7:35 AM, dimes007 said:

Squid:  Thanks for all of the amazing work on these.

 

Can I throw in a feature request to have System Autofan log which fan it is adjusting?   If you want to go further allowing us to add friendly names for each fan such as:   "CPU Fan", "Top Exhaust", etc.

 

Thanks.

 

If you read through the thread, this feature has been requested a lot lol

On 3/11/2022 at 8:59 AM, Wyllic said:

 

If you read through the thread, this feature has been requested a lot lol

True.  I can't be the only one.   and I'll admit, i didn't read all 132 pages. 

I'm looking for an easy way to fetch the stats for cputemp, disc actvity and lan activity into some shell vars oder read them via json from somewhere.

Reason for this: I'm writing a script that displays those datas on several OpenRGB LEDs and -strips using different colours and/or bar graphs for them.

The LED stuff is working, but so far I only found a "legal" way to read out the current cpu load (not temp 😞 )

 

Any clue where to pick up this data?

 

1 hour ago, Michael Meiszl said:

the current cpu load (not temp 😞 )

may start here with sensors as command, you get all temps etc from there ...

 

about DISK & NIC load(s) ... some others have some nice ideas, but as these are also available in the dashboard someone sure know which are good to use

3 hours ago, alturismo said:

may start here with sensors as command, you get all temps etc from there ...

Tnx! that really hit the spot for at least cpu temp

 

i also found the current cpuload in /var/local/emhttp/cpuload.ini alrready

 

Now I just need either disk or lan activity... then I could continue.

 

So i just changed motherboard from a gigabyte z590 to a msi z590 and now i cant get any info on fanspeed etc. 
On my gigabyte board I had to include "modprobe it87 force_id=0x8628" in my go file for my fans to show up, but i got no clue on what I´m doing and I´ve tried googling to find some kind of help but nothing. 
If anyone could help me with this I would be forever grateful! 

I´ve run sensors-detect and the only thing that gave me was "HWMON_MODULES="coretemp nct6683" "

On 4/2/2022 at 12:26 PM, BeardElk said:

So i just changed motherboard from a gigabyte z590 to a msi z590 and now i cant get any info on fanspeed etc. 
On my gigabyte board I had to include "modprobe it87 force_id=0x8628" in my go file for my fans to show up, but i got no clue on what I´m doing and I´ve tried googling to find some kind of help but nothing. 
If anyone could help me with this I would be forever grateful! 

I´ve run sensors-detect and the only thing that gave me was "HWMON_MODULES="coretemp nct6683" "

modprobe coretemp nct6683

  

On 4/2/2022 at 6:26 PM, BeardElk said:

So i just changed motherboard from a gigabyte z590 to a msi z590 and now i cant get any info on fanspeed etc. 
On my gigabyte board I had to include "modprobe it87 force_id=0x8628" in my go file for my fans to show up, but i got no clue on what I´m doing and I´ve tried googling to find some kind of help but nothing. 
If anyone could help me with this I would be forever grateful! 

I´ve run sensors-detect and the only thing that gave me was "HWMON_MODULES="coretemp nct6683" "

 

The problem has something to do with that my MSI board uses nct6687d which is supposedly added to nct6683, but something with patches and something else fucks something up. 
It should be working but is not and I´m not 100% on the rest. 
I´ve tried modprobe-ing every possible thing I could think of but nothing works, both with (force_id=0xa20) and without. 

 

If anyone got any ideas im all ears!

1 hour ago, spl147 said:

modprobe coretemp nct6683

 

Did not work. 
All I get is cpu temps and mb temps, no pwm controler. 

1 minute ago, BeardElk said:

 

Did not work. 
All I get is cpu temps and mb temps, no pwm controler. 

Looking through the thread, the nct6683 is causing  issues for alot of people.