NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dishmagic66
Apr 26, 2014Guide
How to control fanspeed on a RN104
On special request, here is a workaround for controling the fanspeed of the RN104 ( most likely the same on a 102). For this you will have to SSH in to the NAS. Thanks to Moseleypj for doing the ...
Harps85
Oct 13, 2015Aspirant
Thanks m1byo, easy fix and is working great again. Cheers for the re hash of the script.
pa3555
Oct 31, 2015Aspirant
hi i have a readynas 104 with firmware at 6.4.0 im totaly newbeee on linux i try the first script but i dont know the file type and i have try by work and bug lol but noting work do you have a copy of ur file for me ?my nas run all time at 65 to 75c .... and hdd 35-46c i dont like that and my fan never go up to 800 RPM can u help me ?
sent me the folder and instruction in mail
thx !!
at idle ....

- KardanoNov 05, 2015Luminary
May i ask for folder/files and instructions to? I have a readynas 104 with firmware at 6.4.0.
PM me if it is possible, i give you my e-mail.
Thank you very much.
- m1byoNov 05, 2015Aspirant
Read the first few posts of this thread for the original howto for installing this mod. Those are the step-by-step instructions I used.
you just need to change the main ~/fanoveride script to the one I have suggested as i have just changed the OP's code to support the newer firmware.
- KardanoNov 05, 2015Luminary
I want to ask:
if
MAXTEMP=62500 # MAXTEMP=60 #Max temp -> Fan fastest (Note *1000)
what is maxtemp for 70 degrees? (if you know...)
You settings are too loud for me :-)
thanks for your help.
- pa3555Dec 01, 2015Aspirant
change what ?? i know noting about prog for now i have bypassed my fan with externe controler for speed/temps my cpu is 40C and 3 hdd at 28 now before is 67 cpu and 41 for hdd loll do u have file for that ? i want my server control itself the fan becaus my bypass system is too stressed and too fast fan make eratic RPM change it is temporary system but is not like original
- boryankovDec 07, 2015Aspirant
Need help!!! Everything works apart from start on boot
what have i done wrong, when i manually start service i get this
root@RN104 : service fanoveride start
/etc/init.d/fanoveride: 1: /etc/init.d/fanoveride: #!/bin/sh: not found Starting service.
Service startedafter "update—rc.d fanoveride defaults" i get this
rooteRN104 : update—rc.d fanoveride defaults
update—rc.d: using dependency based boot sequencing
insserv: warning: script 'leafp2p' missing LSB tags and overrides - Bats586Dec 11, 2015Aspirant
Hi,
Has anyone tested this under 6.4.1? Don't want to upgrade until it's compatible
Thanks
Bats
- KardanoDec 15, 2015Luminary
my is worknig under 6.4.1. no problem.
- boryankovDec 16, 2015Aspirant
doesn`t start on boot, what have i done wrong, error when i start manually i posted above
- KardanoFeb 17, 2016Luminary
OK with FW 6.4.2 on RN104. (without any changes till 6.4.1, FW update only)
- ZaInTMar 08, 2016Star
I tweaked this a bit to work better in my environment, not too loud, not too hot. It's still quiet enough to not bother me.
The average CPU temperature is down 14 degrees when the fan is set ~600 RPM higher (running at 1500-1800 RPM, previously never going above 1250. I've NEVER seen the fan above 1600 RPM without modifications, it's insane and it's bad for the hard drives.).
CPU temperature is now 48 degrees (was 62) and hard drives are down ~6 degrees (were 47-51, now 41-42).
This is for RN204 and 6.4.2, but I think it's usable with other units - just find the three correct paths for your model in the beginning of /root/fanoverride.
The fan temperature was somehow set to some insane negative value, and the NOTHING should be multiplied by 100.
I added a timestamp to the log because I run locate32 every hour which indexes the drive and really stresses the NAS, that's the way I came up with the values that I use in the script - by checking how hot it got, how fast the fan spun, and when the drives were being used or not.Also I corrected the spelling error just because it bothered me.
Sorry for my bad English, I'm really tired.
This code was originally written by dishmagic66, modified by m1byo, and now modified slightly by me. All credits go to them.
If you don't have nano, get it. Instructions are somewhere in this thread.
The code for
/root/fanoverride
is
#!/bin/bash ## Variables ## FANPWMPATH=/sys/devices/platform/soc/fd880000.i2c-pld/i2c-0/0-003e/hwmon/hwmon0/fan1_target FANSPEEDPATH=/sys/devices/platform/soc/fd880000.i2c-pld/i2c-0/0-003e/hwmon/hwmon0/fan1_input CORETEMPPATH=/sys/devices/virtual/thermal/thermal_zone0/temp MAXFAN=3500 # Maximum operable speed MINFAN=600 # Minimum operable speed MINTEMP=35 MAXTEMP=75 NEWSPEED=1000 # Initial fan speed (%) ## Functions ## function getReadings { FANPWM=$(cat $FANPWMPATH) FANSPEED=$(cat $FANSPEEDPATH) CORETEMP=$(cat $CORETEMPPATH) } function setFanSpeed { TEMPFAN=$(expr $MAXFAN - $MINFAN) NEWFAN=$(expr $TEMPFAN \* $NEWSPEED) NEWFAN=$(expr $NEWFAN / 100) NEWFAN=$(expr $NEWFAN + $MINFAN) if [ $NEWFAN -lt $MINFAN ]; then NEWFAN=$MINFAN fi if [ $NEWFAN -gt $MAXFAN ]; then NEWFAN=$MAXFAN fi echo New Speed: $NEWFAN RPM echo $NEWFAN > $FANPWMPATH } function calcFanPercent { TEMPRAN=$(expr $MAXTEMP - $MINTEMP) TEMPREL=$(expr $CORETEMP - $MINTEMP) TEMPREL=$(expr $TEMPREL \* 100) TEMPPER=$(expr $TEMPREL / $TEMPRAN) NEWSPEED=$TEMPPER echo New Speed Set: $NEWSPEED % at $(date +%T) } ################################################################### echo "Automatically controlling fan speed..." while true do getReadings echo "Temp: $CORETEMP C FAN: $NEWSPEED% [$FANSPEED RPM] [PWM $FANPWM]" calcFanPercent setFanSpeed sleep 5 done ###################################################################Then just
chmod 755 /root/fanoverride
(The plus thingy that someone wrote about doesn't work)
Create /etc/init.d/fanoverride with this content:
#!/bin/sh ### BEGIN INIT INFO # Provides: FanOverride # Required-Start: $local_fs $network $named $time $syslog # Required-Stop: $local_fs $network $named $time $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Description: FanOverride overrides the default ReadyNAS fan control ### END INIT INFO SCRIPT=~/fanoverride RUNAS=root PIDFILE=/var/run/fanoverride.pid LOGFILE=/var/log/fanoverride.log start() { if [ -f /var/run/$PIDNAME ] && kill -0 $(cat /var/run/$PIDNAME); then echo 'Service already running' >&2 return 1 fi echo 'Starting service.' >&2 local CMD="$SCRIPT &> \"$LOGFILE\" & echo \$!" su -c "$CMD" $RUNAS > "$PIDFILE" echo 'Service started' >&2 } stop() { if [ ! -f "$PIDFILE" ] || ! kill -0 $(cat "$PIDFILE"); then echo 'Service not running' >&2 return 1 fi echo 'Stopping service.' >&2 kill -15 $(cat "$PIDFILE") && rm -f "$PIDFILE" echo 'Service stopped' >&2 } uninstall() { echo -n "Are you really sure you want to uninstall this service? That cannot be undone. [yes|No] " local SURE read SURE if [ "$SURE" = "yes" ]; then stop rm -f "$PIDFILE" echo "Notice: log file is not be removed: '$LOGFILE'" >&2 update-rc.d -f <NAME> remove rm -fv "$0" fi } case "$1" in start) start ;; stop) stop ;; uninstall) uninstall ;; retart) stop start ;; *) echo "Usage: $0 {start|stop|restart|uninstall}" esacI don't think I modified that at all. The only thing that doesn't work is that the script doesn't tell you if the service is already started. That's another reason why I added the timestamp, if you're unsure if the service is started just
less /var/log/fanoverride.log
and check the timestamp.
Anyway, then you run
chmod 755 /etc/init.d/fanoverride update-rc.d fanoverride defaults
Then you either restart or
service fanoverride start
And thats it! (At least that's what I did).
You might have to fix leafp2p as well if you get an error about that, there's instructions for that in https://community.netgear.com/t5/Using-your-ReadyNAS/LSB-issue-on-leafp2p/td-p/929396
Now; can someone please tell me how the unit originally adjust the fan speeds, and how to control the LCD? ;)
- KardanoApr 22, 2016Luminary
Hi all,
One question... when i want to remove this fanspeed on RN104.... how to do it?
Is there any procedure how to do it? can you help me?
Thanks.
- KardanoApr 22, 2016Luminary
Do i need this when go to final 6.5.0? Will it collide with 6.5.0 fan control?
Thanks.
- Stan78Oct 14, 2016Aspirant
Hi Guys,
Is it working for Pro6 under firmware 6.6.0 ??
I use to have a problems with fans overspeed before, then with 'low fan speed' errors.
I had some help from Netgear support, and then it was fine...
A week ago (or so) I replaced old fans (chasis and cpu) with Noctua (as recommanded on this forum).
But now, the unit gets up to error : Disk: System is shutting down because disk in channel 3 (Internal) exceeded safe temperature threshold (60 C).
Then it shuts down.
The fans are working (cpu-620 and chasis 730 RPM)
The temp is cpu - 35, system - 65 !!! and HD temp is about 50 (all in celcius)
So I figured, the system fan is not spinning fast enough...
I changed setting to 'Cool' but no joy..:(
Is the fancontrol now included so I can tweak it somehow, or do I need to install these files?
As there were changes , can someone pls can sumarize this and walk me through?
Thanks
Stan
- Stan78Oct 19, 2016Aspirant
Well, I hope that eventually someone will read this posts...:)
I decided to give it a try - downloaded funcontrol and I'm playing a bit with the settings...
Looks promissing. But can one tell me what 'temp2' represents???
temp1 is system (whatever that means), temp3 is CPU, but temp2 ??
It has no fan assigned in configutation, and orginally was commented out by 'ignore temp' sentense.
It showed up on my frontend (so now I have 3 thermometers), and it shows temperature close to CPU temp, but always higher 2 or degrees.
When defragmenting or scrub ir sunning, the CPU and temp2 rises high, accordingly (all together).
Whould it be a second core maybe ???
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!