CkChong

Hi @BL76 , new version is out! It should fix the issue you reported — let me know if anything else comes up. Thanks again for the feedback!

Hi, First of all, that script you ran is actually for AMD (k10temp) systems. Your motherboard looks like Intel, so it’s normal that it didn’t show anything under k10temp. Let’s check a few things step-by-step: Did you install the System Temp plugin and click Detect and Load Driver? In your BIOS, are the fan headers set to PWM / Manual, not Smart or Auto mode? Just to confirm — in FanCtrl Plus, you can see PWM controllers in the dropdown list, but the Identify button doesn’t make the fans react, right? (or are the PWM options completely missing?) If System Temp is loaded correctly and BIOS is already in PWM/manual mode, please share the outputs of the following safe diagnostic commands (these won’t change fan speeds): echo "=== hwmon devices ===" grep -H . /sys/class/hwmon/hwmon*/name echo "" echo "=== Available PWM controllers (safe check) ===" for d in /sys/class/hwmon/hwmon*; do name=$(cat "$d/name" 2>/dev/null) echo "-- $d ($name) --" ls "$d"/pwm* 2>/dev/null done That will help confirm which hwmon chip exposes the PWM interfaces (usually it86xx or nct6xxx for Gigabyte boards). Once we know which one actually has PWM entries, we can test Identify safely from there.

Hi — FanCtrl Plus doesn’t read or control GPU fans; it only works with the motherboard PWM headers (CPU_FAN / CHA_FAN). For PWM2 and PWM7: if Identify shows no response, they’re most likely unused headers. Your board exposes 8 PWM channels and you’ve connected 6 (one CPU fan + five case fans), so that matches. If nothing is connected to PWM2/7, it’s fine to leave them unassigned.

Thanks for the feedback. I found a typo in the .plg. You can ignore this error for now—it doesn’t affect usage. I’ll release an update soon (today or in the next few days) with the fix.

Thanks for the output. It shows your board only has auto mode, no real PWM control. So sadly both FanCtrl Plus and AutoFan can’t adjust the fans on this system.

Please take a look back at the previous few posts above. I already explained this there, and this feature is on the roadmap.

Since you already have System Temp installed and it does detect your Array Fan, it looks like the chip may only support reading RPM, not controlling PWM. Have you tried Dynamix AutoFan before — were you able to actually control the fans with it? If not sure, could you also paste the output of this so we can double check if any PWM controls are exposed? ls /sys/class/hwmon/hwmon*/pwm*

I’ll add an “Always keep fan minimum speed” option to the roadmap. Once I have some time to implement and test it, I’ll include it in a future release.

Yes, that’s actually how the current logic works — when all selected disks are spun down and there’s no active temperature source, the fan will stop completely (or just fall back to your hardware’s own minimum speed). I might consider adding an extra option in the future like “Always keep fans at minimum speed” so that they won’t fully stop. For now, if you’d like to keep them spinning at least at your defined minimum, here are two possible workarounds: 1. Also include an NVMe or SSD in your selection (since those drives don’t spin down), though of course the fan curve will then follow that device too. 2. Enable CPU temperature as an additional source. If this fan doesn’t actually need to follow CPU temps, you can simply set the CPU min–max range to something unrealistically high (e.g. 75 °C – 80 °C). That way, when all disks are spun down, the fan will still see CPU as a source and keep running at your minimum (e.g. 45%).

Thanks a lot for the detailed explanation. Right now FanCtrl Plus uses a linear control curve, so in most cases hysteresis isn’t really needed. But I’ll definitely keep it in mind and consider it in the future if more use cases come up. Also, you can give FanCtrl Plus a try — if the curves are set up properly, you normally shouldn’t run into the ping-pong on/off behavior.

Hello @alturismo , and thanks a lot for the kind words. FanCtrl Plus doesn’t have a hysteresis setting. The way it works is simple: you define a min–max temperature range and a min–max fan speed range, and the plugin automatically scales PWM smoothly between those points. I’m curious — for the hysteresis you mentioned, what would you mainly use it for? Maybe I can learn from your use case.

Thanks for the feedback! 🙏 You can also try enabling the new FCP Airflow option and let me know how it works for you. For more details, check the How to use section under Identify PWM Controller.

Try going into the plugin settings page, click Stop and then Start again. If PWM% still doesn’t show, please paste the output of: ls -l /var/tmp/fanctrlplus

Hi, Just released v1.3.2, which now supports multiple Identify Modes — including Pause, Max Speed, and Pulse. This should make it easier to tell which fan is being controlled, even on boards where fans don’t fully stop. Feel free to update and give it a try.

Yeah, sometimes hardware just acts weird and it’s hard to pin down. If possible, try swapping the two fans between headers — if the issue follows the fan, then it’s the fan itself. If the same header misbehaves again, it’s more likely the motherboard/BIOS side taking control back.

When the fan gets stuck at full speed, can you try Identify — does it still pause the fan? Also, if you click Run Now, do you see a “Manual Run” entry in syslog a few seconds later? And does the log show correct temps and the right PWM output? If the log looks normal but the fan still ignores control (and only a full reboot fixes it), that usually points to the BIOS/EC taking control back, or sometimes a hardware quirk. Maybe try moving that fan to a different CHA_FAN header, re-Identify, and select the correct PWM again in Fan Configuration. That way you can check if it’s always the same fan misbehaving, or if it’s always the same header/socket that loses control.

I haven’t used an IPMI board myself, but from what I’ve seen these boards usually don’t expose normal hwmon pwm* controllers to the OS. The BMC/IPMI tends to own the fan headers instead, which is why FanCtrl Plus (or Dynamix) can’t see them. It might be worth checking with other IPMI users on how they adjust fans under Unraid — most likely through the IPMI plugin or the board’s BMC interface rather than standard hwmon. .

Since it’s back to normal after the reboot, let’s keep an eye on it. If it happens again, please note which header it is and what FanCtrl Plus shows at that moment (PWM %, RPM, disk state). As a simple mitigation, try a small non-zero minimum (e.g. 30–40%) on that header, and make sure no other controller (e.g. Dynamix AutoFan) is active.

Could you try adjusting the BIOS fan settings? Set the used headers to PWM/Manual (not Auto/DC) and disable Fan Stop/auto curve, then test again in FanCtrl Plus. This might sort it out.

Thanks for the suggestion! Give me a bit of time to think about the best way to do this — I’ll most likely revisit it after the 7.2 responsive UI work.

You’re likely still fighting the BIOS/EC. In BIOS, set each fan header to PWM in Smart Fan (not Auto or DC), then try again in FanCtrl Plus. I haven’t used that specific Gigabyte board, so names may differ — just look for PWM mode and avoid Auto/DC.

From a quick look, your Z690 AERO G DDR4 is likely using an ITE (it87 family) Super I/O. Try the IT87 driver from Community Apps and then: Install “ITE IT87 Driver” from Community Apps, then reboot the server (a full reboot, not just stopping/starting the array). BIOS: set each fan header to PWM/Manual, disable Fan Stop and any auto/Smart Fan curve (or set Full Speed) so the BIOS/EC doesn’t fight the OS. Test in Unraid: open FanCtrl Plus → check if PWM controllers show up in the dropdown; set a temporary higher minimum speed to confirm the RPM actually changes. If no PWM controllers show up or RPM doesn’t respond, that board’s EC may be locking fan control and neither plugin can override it. Hope it helps!

Glad it works! Regarding the footer: the % indicator isn’t from FanCtrl Plus or Dynamix AutoFan. It comes from Dynamix System Temp when you select “Array fan speed”. If i remember correctly, AutoFan itself doesn’t add a % there—only RPM. I do plan to add a small footer widget for FanCtrl Plus, but I’ll revisit that after 7.2’s new responsive UI is officially released and I finish the adaptation.

Thanks! Glad you like the Identify feature 😊 For now I’m keeping a 60-second minimum because HDD temps change slowly, and shorter loops can cause fan hunting and extra SMART polls with little benefit. If you need faster reaction, enabling the CPU sensor or slightly raising the per-fan minimum speed usually helps. Once 7.2 is officially out and I’ve finished adapting to the new responsive UI, I can revisit a shorter interval. Out of curiosity, what’s your use case where 1 minute feels too slow?

I haven’t used the Ugreen DXP4800 myself, but you can check the comments above — another user already confirmed success by installing the IT87 plugin to get the PWM fans recognized and controlled with FanCtrl Plus.