Dynamix - V6 Plugins


Recommended Posts

4 hours ago, Michael Meiszl said:

even with fan speed plugin it just tells me "no pwm controllers found" or something alike 😞

(I even do not want to control the fans, I would be glad already if I could read the current rotation speeds to check if all 5 fans are still ok)

Same here. The fan plugin does not detect any fan.

 

On my previous board I thought that I did not need the fan plugin for the CPU/case fans to show up. They were all detected by the sensors plugin.

 

grafik.thumb.png.216e199c8311f03fbb28dab91b5fd86f.png

 

I have found one possible workaround to set acpi_enforce_resources=lax

But I am not sure if this wise to do so. It has risks and even the page itself does not suggest this workaround.

Edited by Pete0
Link to comment

You sure thats the MB temperature? It says amdgpu. I think 'MB Temp' is set by the plugin. Or does the internal GPU count as MB temperature? Then I wonder why my CPU temperature is detected but not the internal GPU of the 4350.

Edited by Pete0
Link to comment
29 minutes ago, Pete0 said:

You sure thats the MB temperature? It says amdgpu

No, and I don't really care about her. Maybe it is the 2nd CPU sensor (they have differnent ones for the chip himself and for the whole package). I take the higher one as a reference.

There are a many more temps offered by the plugin, most of the are from the 4 NVMe "drives".

 

Total output of sensors is:
 

nvme-pci-0d00
Adapter: PCI adapter
Composite:    +26.9°C  (low  = -273.1°C, high = +69.8°C)
                       (crit = +72.8°C)
Sensor 1:     +26.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +31.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0c00
Adapter: PCI adapter
Composite:    +27.9°C  (low  =  -0.1°C, high = +74.8°C)
                       (crit = +79.8°C)

k10temp-pci-00c3
Adapter: PCI adapter
CPU Temp:     +45.0°C

amdgpu-pci-0e00
Adapter: PCI adapter
vddgfx:        1.33 V
vddnb:       993.00 mV
MB Temp:      +37.0°C
slowPPT:       4.00 mW

nvme-pci-0400
Adapter: PCI adapter
Composite:    +36.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +36.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +40.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0100
Adapter: PCI adapter
Composite:    +26.9°C  (low  =  -0.1°C, high = +74.8°C)
                       (crit = +79.8°C)

but, as one can see, there is not a single fan listed 😞

 

Edited by Michael Meiszl
Link to comment

Hello,

 

First of all, many thanks for all the excellent work on the Dynamix plugins, I'm using many of these plugins on my two Unraid servers and I'm extrememely pleased with them.

 

I post here because I have a weird issue with the S3 plugin.

 

WOL works fine on one of my servers (Asus P8Z77-V LX), though I had to enable the Realtek adapter and the Realtek BIOS to get WOL to work.

 

On the other (Asus P8P67 Pro), WOL works fine if I manually ask the sytem to go to S3 standby, but for some reason WOL doesn't work (I can't wake the system up when I send the same magic packet to the same MAC address using the same software) if the system goes on stanbye according to the settings in the S3 plugin. The S3 settings are the same on both servers (after 15 min of array inactivity and medium ethernet activity). The "g" parameter is selected and enabled when you check with ethtools eth0.

 

Here is what is reported with the server that works:


Settings for eth0:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  1000baseT/Half 1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        master-slave cfg: preferred slave
        master-slave status: master
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: external
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: g
        Link detected: yes
 

And here is what's reported for the server that doesn't work:

Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: on (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
 

Can you spot anything that could explain why WOL works when the server is put in stanby manually, but not when the plugin sends it to sleep? I've tried everything in the BIOS of that server: enabling/disabling EPU, enabling/disabling the Intel Ethernet adapter ROM, resetting to defaults and only enabling the wake up with PCI (needed to enabled WOL on the Intel ethernet), I can't find settings that also works when the system goes to sleep by itself and not manually.

 

Many thanks for any help.

 

Link to comment

I'm also not able to use the fan control app.  I did some searching and installed the NerdPack, Pearl and also the Temp Control software as shown here:  https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing

 

Unfortunately, "Detect" is still greyed out and I don't have the choice of a fan controller.

 

I just want my fans to slow down when the machine is idle, like it used to with Windows before I made it into my server.  Any suggestions?

 

Link to comment
On 4/10/2022 at 4:28 AM, Pete0 said:

Same here. The fan plugin does not detect any fan.

 

On my previous board I thought that I did not need the fan plugin for the CPU/case fans to show up. They were all detected by the sensors plugin.

 

grafik.thumb.png.216e199c8311f03fbb28dab91b5fd86f.png

 

I have found one possible workaround to set acpi_enforce_resources=lax

But I am not sure if this wise to do so. It has risks and even the page itself does not suggest this workaround.

 

i would not recommend the acpi_enforce_resources=lax

 

i've tried that before and it caused unraid to fail to boot until removed. which lead me to find this:

 

about asus and the buggy issues with reading fan/temps:
https://bugzilla.kernel.org/show_bug.cgi?id=204807

 

oct 2021 - lot of asus wmi boards got supported via NCT677x:
https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/?id=cd0b8e410937

 

so basically you just have to wait for newer kernel to get better support.

you using 6.10rc3 ?

Link to comment
7 minutes ago, zoggy said:

you should try upgrading to next release (6.10rc4) and see if everything is magically supported for ya (as it includes much newer linux kernel/drivers/etc).

It wont help. as already said I AM on RC4 and nothing has changed. The fans are still invisible (to UNRAID, with the windows tool "hwinfo" i can see them without problem (and not even a driver is needed for this)

Hmm.thumb.jpg.54003355661fdf5e6eefd56337debcf4.jpg

Link to comment
47 minutes ago, zoggy said:

you should try upgrading to next release (6.10rc4) and see if everything is magically supported for ya (as it includes much newer linux kernel/drivers/etc).

Not sure how stable an unraid RC is but I'd rather stay on stable builds. Missing temperature and fan sensors isn't worth any possible risk.

Link to comment
55 minutes ago, Michael Meiszl said:

It wont help. as already said I AM on RC4 and nothing has changed. The fans are still invisible (to UNRAID, with the windows tool "hwinfo" i can see them without problem (and not even a driver is needed for this)

Hmm.thumb.jpg.54003355661fdf5e6eefd56337debcf4.jpg

 

unless you are both using the same motherboard then i dont see how you can use the logic that it wont make a difference. as ive even linked proof that x boards had improvements in detection of wmi sensors via kernel update.

Link to comment
18 minutes ago, Pete0 said:

Not sure how stable an unraid RC is but I'd rather stay on stable builds. Missing temperature and fan sensors isn't worth any possible risk.

 

you can just start the system up with newest rc, just dont start array if your worried about anything with your data/dockers/etc.

then check to see if sensors/fans etc are working so you gather data and know. then revert back to stable release for actual peace of mind and daily use.

 

Link to comment
3 minutes ago, zoggy said:

unless you are both using the same motherboard then i dont see how you can use the logic that it wont make a difference.

unless you dont know that all these asus mobo are totally similar in respect of the sensors, your guess is legal, but totally wrong.

All those 570x boards from ASUS contain the same chips, use the same UEFI Bios and so on. They just differ in addon devices like wifi or nvme slots. They assign the pcie lanes different, but the chipset and the management stuff is the same.

So the try that you suppose to him is a total waste of time.

(and obviously he is not willing to take such a risk too)

 

Link to comment
3 hours ago, Michael Meiszl said:

unless you dont know that all these asus mobo are totally similar in respect of the sensors, your guess is legal, but totally wrong.

All those 570x boards from ASUS contain the same chips, use the same UEFI Bios and so on. They just differ in addon devices like wifi or nvme slots. They assign the pcie lanes different, but the chipset and the management stuff is the same.

So the try that you suppose to him is a total waste of time.

(and obviously he is not willing to take such a risk too)

 

If you actually click on the link the kernel bug report you would see that yes, while the mobo are similar one has to add the mobo string to the appropriate driver to make it the sensor info work. Its comically stupid and does not scale, which is about half of the chatter about with how dumb getting sensors data with asus is.

 

Then if you would have clicked on the link I shared about the driver you would see even further proof of this. How even different variations of the same board have to be added due to how its checked.

 

snippet:

Quote

+static const char * const asus_wmi_boards[] = {

+ "PRIME B460-PLUS",

+ "ROG CROSSHAIR VIII DARK HERO",

+ "ROG CROSSHAIR VIII HERO",

+ "ROG CROSSHAIR VIII IMPACT",

+ "ROG STRIX B550-E GAMING",

+ "ROG STRIX B550-F GAMING",

+ "ROG STRIX B550-F GAMING (WI-FI)",

+ "ROG STRIX Z490-I GAMING",

+ "TUF GAMING B550M-PLUS",

+ "TUF GAMING B550M-PLUS (WI-FI)",

+ "TUF GAMING B550-PLUS",

+ "TUF GAMING X570-PLUS",

+ "TUF GAMING X570-PLUS (WI-FI)",

+ "TUF GAMING X570-PRO (WI-FI)",

+};

 

 

As you noted what mobo you have, can see others reporting same issue:
ROG STRIX X570-F GAMING - https://bugzilla.kernel.org/show_bug.cgi?id=204807#c112

 

Your hwinfo noted that card has NCT6798D but nct6775 driver is to be used.
While sensors-detect knows to associate the NCT67* to nct6775 it doesnt mean that the driver fully supports your mobo.
Some of it is deciding which method to get the sensor data and which can use wmi and so on, where the whole whitelisting mobo name comes into play.

 

Looking at that linux driver history for nct6775, can see that "ROG STRIX X570-F GAMING" was added:
2021-10-12 - https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/drivers/hwmon/nct6775.c?id=6e2baac88cddbb440095c45058bc666df3108a1f

 

Then you would have to see what kernel that then made it into, and if you are using it.
Which is why I asked the other use if you just tried newer linux kernel to see if it works.
As I've been in this same boat, where I had 0 support and then newer kernel exposed some sensor data.. so now I get cpu temp but still no mobo or fans (until 6.10x)

 

Edited by zoggy
Link to comment
On 5/9/2015 at 12:27 PM, DanielCoffey said:

Apologies for repeating a previously asked question but I am still trying to get AutoFan working and have not seen a reply.

 

I was wondering how to set up and use the AutoFan script in Dynamix.

 

I had a quick look and could not get any of the PWM channels on my motherboard to be detected. Is there anything I need to run first or edit to get my PWM channels detected correctly? PWM Controller dropdown just has "None" as the only entry. I am running 6beta15 with no additional plugins.

 

Motherboard used : Gigabyte H97N-WIFI with two PWM channels (one for CPU, one for case fans)

I'm 16/134 pages into this thread and looking for this too. I have autofan installed from the community app tab and everything updated but can't figure out how to get the fans to ramp up with hard drive temp. unraid shows pwm controller as "w83795g - pwm x" (x=1-8, Only 1 selectable at a time) , pwm fan has "/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/fan1_input", and excluded drives I have set to none. but I am still getting high drive temp warnings galore with no fan speed increases. Does anyone have any TLDR instructions for me to get this working? Hopefully a "Click here and check these boxes" type of thing, I don't know codeing...

 

Currrent system is:

Chenbro NR12000 with

"TYAN S5512, Version empty
American Megatrends Inc., Version V8.B14
BIOS dated: Fri 16 Nov 2018 12:00:00 AM EST" per the dashboard

 

Hard Drives are Seagate 6TB (Ironwolf I think, Don't recall) Spinning Rust, a Crucial SSD for cache, Seagate Exos (Spinning Rust) assigned to a VM, and boot drive is a SanDisk thumbdrive.

 

Thinking of "Upgrading" to a supermicro chassis/board soon (Hot-swap bays, may be older board though....) so I don't know if it'll work right on that and not this or vice-versa......

Unraid_AutoFanSpeed.png

Link to comment
  • 2 weeks later...
On 10/29/2021 at 12:37 PM, multiplY said:

Hi, since i updated to unraid Version 6.9.2, i have a Problem with the S3 Sleep Plugin.

It seemed to shut the system down instead of sleep and never came back up, i mirrored the syslog to flash and now finaly found the time to look into it but i don't really understand why its happening:

The Server was supposed to go sleep at 2:00 and wakeup the same day at 19:00.

To Achive this i set this custom command before sleep:

echo 0 > /sys/class/rtc/rtc0/wakealarm
echo `date '+%s' --date='19:00:00'` > /sys/class/rtc/rtc0/wakealarm

It was working fine for years.

 

In the syslog i now saw whats happening:

Its going to sleep at night as planned:

Oct  6 02:00:16 unRAID s3_sleep: Disk activity detected. Reset timers.
Oct  6 02:01:16 unRAID s3_sleep: All monitored HDDs are spun down
Oct  6 02:01:16 unRAID s3_sleep: Extra delay period running: 0 minute(s)
Oct  6 02:01:16 unRAID s3_sleep: Initialize TCP activity counter
Oct  6 02:02:16 unRAID s3_sleep: All monitored HDDs are spun down
Oct  6 02:02:16 unRAID s3_sleep: Check TCP/SSH/TTY/IP activity
Oct  6 02:02:38 unRAID s3_sleep: Communication state is idle
Oct  6 02:02:38 unRAID s3_sleep: Execute custom commands before sleep
Oct  6 02:02:38 unRAID s3_sleep: Enter sleep state now
Oct  6 02:02:38 unRAID kernel: PM: suspend entry (deep)
Oct  6 02:02:38 unRAID kernel: Filesystems sync: 0.003 seconds

But when it wakes up, it seems to do some stuff that was supposed to be done before sleep but i never looked into the syslog before the problem so it could be normal:

Oct  6 19:00:12 unRAID kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct  6 19:00:12 unRAID kernel: OOM killer disabled.
Oct  6 19:00:12 unRAID kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Oct  6 19:00:12 unRAID kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct  6 19:00:12 unRAID kernel: e1000e: EEE TX LPI TIMER: 00000011
Oct  6 19:00:12 unRAID kernel: sd 5:0:0:0: [sde] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 6:0:0:0: [sdf] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 6:0:0:0: [sdf] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 5:0:0:0: [sde] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 4:0:0:0: [sdd] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
Oct  6 19:00:12 unRAID kernel: sd 2:0:0:0: [sdb] Stopping disk
Oct  6 19:00:12 unRAID kernel: sd 3:0:0:0: [sdc] Stopping disk
Oct  6 19:00:12 unRAID kernel: bond0: (slave eth0): link status definitely down, disabling slave
Oct  6 19:00:12 unRAID kernel: device eth0 left promiscuous mode
Oct  6 19:00:12 unRAID kernel: bond0: now running without any active interface!
Oct  6 19:00:12 unRAID kernel: br0: port 1(bond0) entered disabled state
Oct  6 19:00:12 unRAID kernel: ACPI: Preparing to enter system sleep state S3
Oct  6 19:00:12 unRAID kernel: PM: Saving platform NVS memory
Oct  6 19:00:12 unRAID kernel: Disabling non-boot CPUs ...

After that it seems to do normal wakeup stuff:

Oct  6 19:00:12 unRAID kernel: smpboot: CPU 1 is now offline
Oct  6 19:00:12 unRAID kernel: smpboot: CPU 2 is now offline
Oct  6 19:00:12 unRAID kernel: smpboot: CPU 3 is now offline
Oct  6 19:00:12 unRAID kernel: ACPI: Low-level resume complete
Oct  6 19:00:12 unRAID kernel: PM: Restoring platform NVS memory
Oct  6 19:00:12 unRAID kernel: smpboot: Scheduler frequency invariance went wobbly, disabling!
Oct  6 19:00:12 unRAID kernel: Enabling non-boot CPUs ...
Oct  6 19:00:12 unRAID kernel: x86: Booting SMP configuration:
Oct  6 19:00:12 unRAID kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct  6 19:00:12 unRAID kernel: CPU1 is up
Oct  6 19:00:12 unRAID kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Oct  6 19:00:12 unRAID kernel: CPU2 is up
Oct  6 19:00:12 unRAID kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct  6 19:00:12 unRAID kernel: CPU3 is up
Oct  6 19:00:12 unRAID kernel: ACPI: Waking up from system sleep state S3
Oct  6 19:00:12 unRAID kernel: sd 2:0:0:0: [sdb] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 5:0:0:0: [sde] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 3:0:0:0: [sdc] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 4:0:0:0: [sdd] Starting disk
Oct  6 19:00:12 unRAID kernel: sd 6:0:0:0: [sdf] Starting disk

After that, there seems to be the problem, s3_sleep initiates a shutdown, which its not supposed to do and while at the same time still wakeup tasks are execudet like spinup:

Oct  6 19:00:12 unRAID s3_sleep: Shutdown system now
Oct  6 19:00:12 unRAID emhttpd: read SMART /dev/sdc
Oct  6 19:00:12 unRAID shutdown[27671]: shutting down for system halt
Oct  6 19:00:12 unRAID init: Switching to runlevel: 0
Oct  6 19:00:12 unRAID s3_sleep: System woken-up. Reset timers
Oct  6 19:00:12 unRAID init: Trying to re-exec init
Oct  6 19:00:14 unRAID kernel: mdcmd (46): nocheck cancel
Oct  6 19:00:15 unRAID emhttpd: Spinning up all drives...
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdd
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sde
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdb
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdf
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sdc
Oct  6 19:00:15 unRAID emhttpd: read SMART /dev/sda
Oct  6 19:00:15 unRAID emhttpd: Stopping services...
Oct  6 19:00:15 unRAID emhttpd: shcmd (74385): /etc/rc.d/rc.libvirt stop
Oct  6 19:00:15 unRAID root: Waiting on VMs to shutdown

Here are my Plugin-settings, its Version 3.0.8

image.thumb.png.82f14d30b85509932fcc9a5e899dd958.png

Full syslog is also attached. I hope you can help me with this problem, thanks in advance.

syslog 222.37 kB · 1 download

 

 

Hey. Did you manage to fix this? I have the same issue, it automatically shuts system down when waking up from sleep. Highly annoying. Another issue is that when it goes to sleep about 50% of the times it automatically wakes up from that sleep immediately after.

Link to comment
  • 3 weeks later...

Hello guys.
I am running one of my Unraid instances on an old hardware. AMD A8 APU on a ZOTAC A75ITX-B-E mini-ITX mobo.
I've installed System Temp plugin and perl from nerdpack. Now it detects k10temp + nct6775. 
If I load NCT6775 drivers, it gives me values that are absolutelly wrong.
If I load k10temp drivers, it gives me only one temperature value and nothing about fans.
See attachments.

 

Is there a workaround for this?

k10-00.png

k10-01.png

nct-00.png

nct-01.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.