NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
glem
May 22, 2013Aspirant
Easy fix fan/temp OS6 issues on x86 legacy #no support
>> EDIT - 2014-04-12 <<
Before to hack your system, update first to 6.1.7. Built-in fancontrol support is there!
6.1.7 has been released: http://www.readynas.com/forum/viewtopic.php?f=1&t=76000
>> EDIT <<
Here is how to fix fan and temperature issues on legacy x86 systems running OS 6.x, until built-in support is there.
I'd previously created this post http://www.readynas.com/forum/viewtopic.php?f=51&t=70133&start=255#p393886 but it will be easier for community to have fancontrol file examples for all models in a dedicated post.
It's a very easy and reliable method to monitor fan and temperature with lm-sensors and fancontrol standard packages.
No change on GUI reports.
NO WARRANTY / NO SUPPORT !!!
with root access, execute the following commands:
edit /etc/fancontrol file and copy the following file example corresponding to your model http://www.readynas.com/forum/viewtopic.php?f=51&t=71155#p395324
or create your own /etc/fancontrol file using pwmconfig command http://www.readynas.com/forum/viewtopic.php?f=51&t=71155&p=395324#p395318
fancontrol daemon start automaticaly when you install it.
restart fancontrol daemon for changes in file /etc/fancontrol take effect
to interact with fancontrol daemon, use
You can display sensors values with sensors command
Before to hack your system, update first to 6.1.7. Built-in fancontrol support is there!
6.1.7 has been released: http://www.readynas.com/forum/viewtopic.php?f=1&t=76000
>> EDIT <<
Here is how to fix fan and temperature issues on legacy x86 systems running OS 6.x, until built-in support is there.
I'd previously created this post http://www.readynas.com/forum/viewtopic.php?f=51&t=70133&start=255#p393886 but it will be easier for community to have fancontrol file examples for all models in a dedicated post.
It's a very easy and reliable method to monitor fan and temperature with lm-sensors and fancontrol standard packages.
No change on GUI reports.
NO WARRANTY / NO SUPPORT !!!
with root access, execute the following commands:
apt-get update && apt-get upgrade
apt-get install lm-sensors fancontrol
echo "#fancontrol" > /etc/fancontrol
edit /etc/fancontrol file and copy the following file example corresponding to your model http://www.readynas.com/forum/viewtopic.php?f=51&t=71155#p395324
or create your own /etc/fancontrol file using pwmconfig command http://www.readynas.com/forum/viewtopic.php?f=51&t=71155&p=395324#p395318
fancontrol daemon start automaticaly when you install it.
restart fancontrol daemon for changes in file /etc/fancontrol take effect
/etc/init.d/fancontrol restart
to interact with fancontrol daemon, use
/etc/init.d/fancontrol stop
/etc/init.d/fancontrol start
/etc/init.d/fancontrol restart
You can display sensors values with sensors command
root@nas-xx-xx-xx:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +43.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +80.0°C, crit = +100.0°C)
it8721-isa-0a10
Adapter: ISA adapter
in0: +12.19 V (min = +8.06 V, max = +10.66 V) ALARM
in1: +4.98 V (min = +2.20 V, max = +3.51 V) ALARM
in2: +3.28 V (min = +0.02 V, max = +0.18 V) ALARM
in3: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM
in4: +1.02 V (min = +1.42 V, max = +2.21 V) ALARM
in5: +1.80 V (min = +1.66 V, max = +0.54 V) ALARM
in6: -12.10 V (min = -25.78 V, max = -0.01 V)
in7: +3.24 V (min = +0.00 V, max = +2.86 V) ALARM
in8: +3.34 V
fan1: 0 RPM (min = 10 RPM) ALARM
fan2: 0 RPM (min = 44 RPM) ALARM
fan3: 851 RPM (min = 11 RPM)
temp1: +0.0°C (low = +57.0°C, high = -25.0°C) ALARM sensor = thermistor
temp2: +0.1°C (low = -16.0°C, high = -123.0°C) ALARM sensor = thermal diode
temp3: +0.1°C (low = +37.0°C, high = -44.0°C) ALARM sensor = thermal diode
cpu0_vid: +2.050 V
173 Replies
Replies have been turned off for this discussion
- renedisAspirantundo temp hacks in 6.1.6:
apt-get remove lm-sensors fancontrol
Installed 6.1.7 and now getting this readings:
Temp graph is also showing now.
I've installed and done this through a remote connection from my work.
So I can't really tell at this moment if the fans are running fine or full RPM without the fix.
Trying to fix the fan RPM reading this evening.
Runing:
Q6600 @ Readynos Pro 6
Edit:
Installed the "temp-fix" again.
No result in showing correct rpm graphs.
CPU temp in browser = Core0
System temp in browser = Temp1
Sensors output:coretemp-isa-0000
Adapter: ISA adapter
Core 0: +40.0°C (high = +84.0°C, crit = +100.0°C)
Core 1: +42.0°C (high = +84.0°C, crit = +100.0°C)
Core 2: +38.0°C (high = +84.0°C, crit = +100.0°C)
Core 3: +38.0°C (high = +84.0°C, crit = +100.0°C)
w83627dhg-isa-0a10
Adapter: ISA adapter
Vcore: +1.14 V (min = +0.00 V, max = +1.74 V)
in1: +1.87 V (min = +0.54 V, max = +0.89 V) ALARM
AVCC: +3.22 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.22 V (min = +2.98 V, max = +3.63 V)
in4: +1.23 V (min = +1.14 V, max = +0.64 V) ALARM
in5: +1.49 V (min = +1.12 V, max = +1.18 V) ALARM
in6: +1.02 V (min = +1.70 V, max = +1.66 V) ALARM
3VSB: +3.20 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.14 V (min = +2.70 V, max = +3.63 V)
Rear-fan: 897 RPM (min = 84375 RPM, div = 16) ALARM
CPU-fan: 1520 RPM (min = 1467 RPM, div = 8)
Outside-fan: 1095 RPM (min = 733 RPM, div = 8)
fan4: 0 RPM (min = 2109 RPM, div = 128) ALARM
fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM
temp1: +56.0°C (high = -1.0°C, hyst = +125.0°C) sensor = thermistor
temp2: +30.5°C (high = +80.0°C, hyst = +123.0°C) sensor = CPU diode
temp3: -38.0°C (high = +80.0°C, hyst = +123.0°C) sensor = thermistor
cpu0_vid: +0.000 V - I just remembered that I had never undone my fan hacks when updating to 6.1.7 RC5.
If I doapt-get remove lm-sensors fancontrol
at this point, will this fix the problem or whether a factory default will be required?
Any ideas before I proceed. - renedisAspirantare your readings fine now or are they malfunctioning?
If they do work, don't remove anything.. - Everything works fine.
I tested with Plex and fan rpms change according to transcoding quality. - Does the lm-sensors package have to be installed for the fans to work properly?
- renedisAspirantlm-sensors package do not have to be installed after the 6.1.7 RC5 update.
My fans are running fine now, only not showing properly in frontview.
I can't really tell if the fan RPM changes if the CPU is under load, but for now... It sounds good.
I did noticed an other failure now that I'm home.
The OLED screen works while booting and showing hostname etc. but after a short time the screen stops working. - Should I proceed in removing lm-sensors then? I wonder what Skywalker has to say about this,
Sent from my iPhone using Tapatalk - GMulfordAspirantI've just done a fresh install of 6.1.7 RC5 on a readynas pro business edition and seems to be working great. Nice to see they have invested some time into getting all the graphs etc working on the legacy devices. :thumbsup:
Only issue is the fans are now too slow, they start at about 2000 then over an hour drop to <800. The temps while copying some data are:
CPU 50c
system 65c
drives 43c
Which isn't too bad although during rebuild the drives hit >50c which isn't good. The main problem is I keep getting an email saying "Fan 'Fan' in enclosure 'Internal' speed is below threshold. (688 rpm)." Is there an option I'm missing to recalibrate the fans like on the old firmware? or a way of speeding them up a bit?
For now I may pop an extra fan on the spare fan header see if that will cool the drives.
Renedis is your OLED screen just turning off? I think it's meant to do that. It pops back up if there is an alert like sync % complete or if you press power button quickly. - mdgm-ntgrNETGEAR Employee RetiredIf the OLED screen stayed on all the time it might burn out prematurely, so only having it on when needed is good.
- renedisAspirantThe screen was always on in the other versions of OS6.
It displayed the hostname and IP adress.
So you guys are telling me that the display should be turned of after a while..
Can't really remember if the screen turned of in OS4.
I'm trying to figure out if it is possible to fix the graphs in Frontview.
the trick with the .conf file in Sensors.D does not work :(compute fan1 0+fan3_input,0-fan3_input
compute temp2 0+temp1_input,0-temp1_input
I have tried different settings without any succes.
Does anyone else got an idea?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!