12gen N-series Nas motherboard (topton, cwwk, ... )
- Thread starter Steffe
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
The lower states generally help you preserve energy. But sometime switching states can be a little bit rough, so I want to see if it works well.
I have not been able to find the fans in Proxmox. I have the BIOS settings for both Automatic and Software.
Has anyone has been able to control the fans from an OS/Software? I have been trying to get this to work with no luck. I paged through this thread and other threads to see if I could resolve it but no luck thus far.
Has anyone has been able to control the fans from an OS/Software? I have been trying to get this to work with no luck. I paged through this thread and other threads to see if I could resolve it but no luck thus far.
I just posted about it here here:
I just got the new CWWK CW-NAS-ADLN-K N150 model, and can report that it has a BIOS from 27/11/2024, so pretty updated.
SATA boot worked out of the box too, hadn't had any issues with it so far at all.
To get the fan controlled with software (PWM), it need to be connected to SYSFAN1. SYSFAN2 or any other header like the Jonsbo N2 fan header won't work, they're locked at 100% speed. In the BIOS you need to set it to be Software controlled, and with a fan speed of 255 (so fans will be at 100% speed before software control kicks in).
Here are the commands needed to be able to control the fans:
One time only:
sudo modprobe it87 force_id=0x8620
#When running through sensors-detect, you just have to say yes to the defaults and add it to modules.
sudo sensors-detect
sudo /etc/init.d/kmod start
Manual Fan Control:
sudo modprobe it87 force_id=0x8620
sudo echo 255 | sudo tee /sys/class/hwmon/hwmon4/pwm3
(255 is 100% speed, 0 is 0% speed.)
I recommend trying to run that last command with 0 for a minute to verify that changing fan speed works. It's not the most responsive command, changing the fan speed often takes 20 seconds or so to kick in, but it eventually does.
Once you've got manual control working, you can start using this: GitHub - desbma/hddfancontrol: Regulate fan speed according to hard drive temperature
For TrueNAS there's this thread: How I used a docker container to adjust the fans from the hdd temp. You need to do the commands I told you about above, then set "modprobe it87 force_id=0x8620" as a TrueNAS pre-init script. See the attached screenshot
Then here's the YAML I used to install the "Custom App" (Apps - Discover Apps - Hamburger menu - Install via YAML):
There you go, that should be everything needed to setup fans with a CWWK CW-NAS-ADLN-KYAML:services: hddfancontrol: cap_add: - SYS_MODULE environment: - DRIVE_FILEPATHS=/dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde - FAN_PWM_FILEPATH=/sys/class/hwmon/hwmon4/pwm3 - FAN_START_VALUE=130 - FAN_STOP_VALUE=70 - MIN_TEMP=30 - MAX_TEMP=55 - INTERVAL_S=30 - TEMP_QUERY_MODE=smartctl - VERBOSITY=debug image: ghcr.io/fightforlife/docker_hddfancontrol:master privileged: True restart: unless-stopped volumes: - /dev:/dev:ro
Do your settings stay persistent over a reboot? I can get it to work but after a reboot, I need to reconfigure the fans.
You mean the "sensors-detect" line? Yeah, that stays for me (and should stay for everyone, if not it's a proxmox specific issue you have).
The "sudo modprobe it87 force_id=0x8620" is run as a pre-init script on every boot, and the docker image auto launches at every boot too, so everything works automatically after rebooting.
The "sudo modprobe it87 force_id=0x8620" is run as a pre-init script on every boot, and the docker image auto launches at every boot too, so everything works automatically after rebooting.
Last edited:
This part - It is not persistent after boot. I have added it to the etc/modules but still no luck.
I see what available sensors and no fans. Once I rerun this command, and then run sensors, the fans are recognized. Trying to understand why.
It's not supposed to be persistent after boot, just run it at every boot via a startup script. I'm not familiar with Proxmox, but surely there's a way to run commands at boot.
Edit:
forum.proxmox.com
Crontab with @reboot should do the trick.
Edit:
Start-up/boot script
How can I create a start up script for proxmox for when the system boots... e.g.: I would like to update "ethtool -K eno1 tso off gso off" to be written each time the system starts
forum.proxmox.com
Crontab with @reboot should do the trick.
Last edited:
Perfect! Thank you again!It's not supposed to be persistent after boot, just run it at every boot via a startup script. I'm not familiar with Proxmox, but surely there's a way to run commands at boot.
Edit:
Start-up/boot script
How can I create a start up script for proxmox for when the system boots... e.g.: I would like to update "ethtool -K eno1 tso off gso off" to be written each time the system starts
Crontab with @reboot should do the trick.
Hey been great reading through this thread and I have learned a lot already so thanks all. I ordered the N150 version of the BKHD-1264 it should be here next week. I was not actually planning on using the onboard SATA as I have a separate 9200i to use. However, I will drop in with any info if the BIOS is different as it's not listed on the site.. I suspect It's identical with just the CPU swapped…
Sorry, just saw your post. So far, this is my backup nas. It's good to see that everything's integrated already, and it's pretty silent. So yeah, nothing to complain about, except the slow post of bios when SATA HDD connected to onboard Sata. 2 minutes before it proceeds to my Unraid Boot. Other than that, no issues.
I actually ordered one since I made that post, I like the board. Did yours ship with the igp disabled in the bios?
No I don't. My m/b is MW-n100-nas, green pcb. Are we talking about same m//b? Do you have the link for latest bios?
I didn't notice whether my igp was disabled or not. With no SATA drives, it boots quickly. With SATA connected, it's almost 2 mins.