Hello, when i installed the helios64 initially i had the problem with the fans spinning at 100% (or really loud) and i solved it somehow. It was working fine with the fans spinning for one second when starting and shutting down the device. Now i finally updated the NAS with
 

sudo apt update
sudo apt upgrade
sudo omv-release-upgrade
sudo reboot

and after the reboot the fans are now spinning really loud again all the time. Is anyone aware of an easy solution or a quick fix?

Someone else had the same problem at https://forum.openmediavault.org/index.php?thread%2F42550-fans-go-on-full-and-stay-there-after-doing-an-update-in-omv-web-control-panel-he%2F= but it seems he either did not solve it or he just forgot to report back. I'm not sure if

is related to my problem.

alking about changing the fans but mentions the PWM Fan control again. On reddit

someone mentions these settings again. I checked and my fancontrol settings seem to be identically or pretty close. In another reddit thread

it was mentioned to "I went to armbian-config => System => CPU, set minimum and maximum CPU speed at 1200000 and set "governor" to "performance".". But its just "Fan too loud" and not "Fan spinning at 100%"

So, i wanted to ask you guys if you know a fix for that problem 😕

Edited January 3, 20233 yr by quokka
Clarifications, formatting

Yes, i checked (and edited) fancontrol and restartet the service afterwards, with no change, unfortunately.

/etc/fancontrol


# Helios64 PWM Fan Control Configuration
# Temp source : /dev/thermal-cpu
INTERVAL=10
FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input
MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40
MAXTEMP=/dev/fan-p6/pwm1=110 /dev/fan-p7/pwm1=110
MINSTART=/dev/fan-p6/pwm1=60 /dev/fan-p7/pwm1=60
MINSTOP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40
# changed from 20 to 40
MINPWM=40
# entirely new line according to one of the posts
MAXPWM=/dev/fan-p6/pwm1=120 /dev/fan-p7/pwm1=65

 

Its so hard to know i solved this once after installing but i can't find the solution anywhere. Oh, i checked the Wiki of the helios as well, there is nothing in the troubleshooting area.

Edited January 3, 20233 yr by quokka

I actually found the solution after some tweaking around with the help of someone in a random chat:

`/etc/fancontrol` is the path `FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input` but `/dev/thermal-cpu/` does not exist (anymore?), but `/dev/thermal-board/` is available -> changed the path, `sudo systemctl restart fancontrol.system` and everything is silent. 

 

Additionally it is possible to recreate the fancontrol file with pwmconfig, but the service need to be stopped for that.

/dev/thermal-cpu is there for me (OMV6 , Debian bullseye: upgraded from OMV5 Debian buster). The symlink is created by /etc/udev/rules.d/90-helios64-hwmon.rules  from  armbian-bsp-cli-helios64 (I have version 22.11.0-trunk of it but I checked and 22.02.1 also has it). Do you have this package installed ?

Can you send the version of `dpkg -l 'linux-image-*-rockchip64'`, '`dpkg -l armbian-bsp-cli-helios64`. Could you also paste the output of `cat /etc/apt/sources.list.d/armbian.list`.

@quokka note that thermal-board is different from thermal-cpu. Both should exist. And they report different values.

(well I do not get thermal-board if I do not explicitly load the lm75 module but that is another matter, maybe due to me running the edge kernel).

As the board is usually 15 degrees below the CPU it is not safe for the CPU to bind the fan to the board temp (they likely will never trigger).

 

OMV has a tendency to remove packages on upgrade (as it forces the upgrades whatever the criticality of the packages the conflict resolution wants to remove).

You want to check you still have armbian-bsp-cli-helios64 installed. If not install and reboot.