<<SOLVE>> Fan Speed

[maxdo]

Hi to all,
would i like to ask you if there is any way to mange the speed of the fan.
Actualy run even at the max speed.

thanks

[fvdw]

That could mean that your disk temperature is above the threshold that can be set in the disk menu. (Temperature guard). You can change the threshold at which the fan daemon will start

[Jocko]

That could mean that your disk temperature is above the threshold that can be set in the disk menu.

or the fan daemon is not running but in this case you should have a system warning when you load the firmware web-interface.
To check this point, please to post the output

Code: Select all

ps axf

and see also if you have a warning

[maxdo]

Hi to all,
in effect in the disk setup....i have not enable the service :(
Now it is activated, and the fan it is come back regular and in silent mode.
in effect i don't seen this parameter in the disk setup (i'm expect to find a specific menu kind Fan SEtup or similar).
So, thanks for your support.
have a great day.
ciao

[Jocko]

Hi

Nope, it is not the explanation.
From the firmware interface, there is no control to enable/disable the fan daemon. In all cases the fan must be on if the device has one. :scratch
What you enabled is the hard drive temperature guard daemon which will stop the nas if it detects a disk temperature too hot. So not related with the fan control

I assume either the fan daemon was hanged or was not running and all is now restored if you have rebooted the nas.

In the ps command you should see this line

Code: Select all

/usr/sbin/fan-d

[maxdo]

:please ooops

ok. in effect i'd reboot the device too, after change the configuration.

running the command ps axf, i've back:

root@fvdwsl-base:/ # ps axf
PID TTY STAT TIME COMMAND
2 ? S 0:00 [kthreadd]
4 ? I< 0:00 \_ [kworker/0:0H]
5 ? I 0:00 \_ [kworker/u2:0]
6 ? I< 0:00 \_ [mm_percpu_wq]
7 ? S 0:00 \_ [ksoftirqd/0]
8 ? I 0:00 \_ [rcu_preempt]
9 ? I 0:00 \_ [rcu_sched]
10 ? I 0:00 \_ [rcu_bh]
11 ? I< 0:00 \_ [netns]
279 ? S 0:00 \_ [oom_reaper]
280 ? I< 0:00 \_ [writeback]
282 ? I< 0:00 \_ [crypto]
283 ? I< 0:00 \_ [kintegrityd]
285 ? I< 0:00 \_ [kblockd]
291 ? I< 0:00 \_ [ata_sff]
309 ? I< 0:00 \_ [md]
401 ? I< 0:00 \_ [rpciod]
402 ? I< 0:00 \_ [xprtiod]
403 ? S 0:00 \_ [kswapd0]
415 ? I< 0:00 \_ [nfsiod]
416 ? I< 0:00 \_ [cifsiod]
417 ? I< 0:00 \_ [cifsoplockd]
418 ? S 0:00 \_ [jfsIO]
422 ? S 0:00 \_ [jfsCommit]
423 ? S 0:00 \_ [jfsSync]
424 ? I< 0:00 \_ [xfsalloc]
425 ? I< 0:00 \_ [xfs_mru_cache]
570 ? S 0:00 \_ [scsi_eh_0]
571 ? I< 0:00 \_ [scsi_tmf_0]
574 ? S 0:00 \_ [scsi_eh_1]
575 ? I< 0:00 \_ [scsi_tmf_1]
579 ? I< 0:00 \_ [smflush]
580 ? S 0:00 \_ [spi0]
581 ? I 0:00 \_ [kworker/u2:3]
672 ? S< 0:00 \_ [aoe_tx0]
673 ? S< 0:00 \_ [aoe_ktio0]
732 ? I< 0:00 \_ [raid5wq]
735 ? I< 0:00 \_ [dm_bufio_cache]
736 ? I< 0:00 \_ [kmpathd]
737 ? I< 0:00 \_ [kmpath_handlerd]
757 ? I< 0:00 \_ [ipv6_addrconf]
760 ? I< 0:00 \_ [dsa_ordered]
784 ? I< 0:00 \_ [kworker/0:1H]
785 ? S 0:00 \_ [jbd2/sda7-8]
786 ? I< 0:00 \_ [ext4-rsv-conver]
805 ? S 0:00 \_ [jbd2/sda1-8]
806 ? I< 0:00 \_ [ext4-rsv-conver]
838 ? I< 0:00 \_ [iscsi_eh]
862 ? S 0:00 \_ [jbd2/sda5-8]
863 ? I< 0:00 \_ [ext4-rsv-conver]
1532 ? S 0:00 \_ [jbd2/md0-8]
1533 ? I< 0:00 \_ [ext4-rsv-conver]
2899 ? I 0:00 \_ [kworker/0:2]
2900 ? I 0:00 \_ [kworker/0:1]
2903 ? I 0:00 \_ [kworker/0:0]
1 ? Ss 0:03 init
847 ? Ss 0:00 /usr/sbin/buttonsd
1024 ? Ss 0:00 /usr/sbin/fan-d
1048 ? S<s 0:00 /sbin/udevd --daemon
1399 ? Ss 0:00 /sbin/mdadm --monitor --daemonise --scan --delay=600
1583 ? Ss 0:00 /usr/bin/httpd -f httpd.conf -d /etc
1586 ? S 0:28 \_ /usr/bin/httpd -f httpd.conf -d /etc
1723 ? S 0:27 \_ /usr/bin/httpd -f httpd.conf -d /etc
1589 ? Ss 0:01 /usr/sbin/noflushd -n 15 /dev/sda /dev/sdb
1619 ? Ss 0:00 /usr/bin/discoverd
1627 ? Ss 0:00 /usr/bin/rpcbind
1645 ? Ss 0:00 dropbear -p 22 -r /rw_fs/etc/dropbear/dropbear_rsa_ho
2904 ? Ss 0:00 \_ dropbear -p 22 -r /rw_fs/etc/dropbear/dropbear_rs
2906 pts/0 Ss 0:00 \_ -sh
2927 pts/0 R+ 0:00 \_ ps axf
1664 ? Ss 0:00 /usr/sbin/hostd 7200
1687 ? Ss 0:00 /usr/sbin/temp-guard 56
1744 ? Ss 0:00 /usr/sbin/nmbd -D -l /var/log/samba
1746 ? Ss 0:00 /usr/sbin/smbd -D -l /var/log/samba
1754 ? S 0:00 \_ /usr/sbin/smbd -D -l /var/log/samba
1756 ? S 0:00 \_ /usr/sbin/smbd -D -l /var/log/samba
1972 ? Ss 0:00 /bin/ntpd -p 192.168.1.30
2065 ? Ss 0:00 /usr/sbin/vnstatd -d
2917 ? Ss 0:00 /usr/sbin/fan-d

and if i run the command /usr/sbin/fan-d
i've back
fan5big daemon version 10 21 sept 2020 started
fan5big: temperature limit = 47 oC
root@fvdwsl-base:/ # fan5big: disks installed: sda=1 sdb=1 sdc=0 sdd=0 sde=0
fan5big: an driver path is /sys/bus/i2c/devices/0-003e/hwmon/hwmon0/
fan5big: disk temperatures sda 47 sdb 42 sdc -1 sdd -1 sde -1
fan5big: temperature below limit(47) fan off, temp = 47

so maybe that the service was not running, before the reboot.

do you think that i need to do other check about? :hail
ciao

[Jocko]

so maybe that the service was not running, before the reboot.

Yes it is my opinion.
Now you have to abort the additional fan daemon that you have started like one is already running (1024 ? Ss 0:00 /usr/sbin/fan-d)

Code: Select all

kill -9 2917

If you do not have rebooted again the nas.

do you think that i need to do other check about?

No nothing else to do

[maxdo]

:applause
thanks. have a great day.
ciao