NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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
- Hello,
I read here about fan and temperature controls getting it into the frontview page. I have a ReadyNas Pro (Pioneer). The temperature control is working with the pmwconfig tool as described in this thread. I don't get the point if you can get the temperature graphs working without using crontab jobs. Is that possible?
If you look to this reply https://www.readynas.com/forum/viewtopic.php?f=51&t=71155&start=75#p411889, then it should work with adding or modifing a file under 'sensors.d' map. Is this true for the ReadyNas Pro and if so how? I updated to 6.1.6 version.
Thanks for the input already done here. - I've just tested 6.1.6 on my Ultra 4.
Overall happy however my fan is running at 800rpm whereas under 4.2.26 it was running at 1800rpm.
My temp are getting quite high, is this still a problem with OS 6 and I need to manually configure the fan control??
Thanks for any advice... :D - Hi,
first time post here. Great forum :D
I installed 6.1.6 on my ultra 2 and it Works very good exept for the fan Control. The fan stabilizes at 760 rpm and CPU temp is at 60C without load. I Guess this is a bit high. I tried "echo 50 > /sys/devices/platform/it87.2576/pwm1" as root and the fan went to 1500 rpm for a while, but Returns to 760 rpm within 20 minutes or so. System temp is at about 25C.
any advice?
best,
Paal - 60C is perfectly fine for Atom -- maximum operating temperature is 100C. In fact, the internal CPU core temp sensor only becomes accurate over 50C.
- Somehow I can't get the fans in my Ultra 6 to work. I tried a created /etc/fancontrol and tried to create it but the temperature sensors are missing.
sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: N/A (crit = +100.0°C)
Core 1: N/A (crit = +100.0°C)
it8721-isa-0a10
Adapter: ISA adapter
in0: +12.00 V (min = +9.07 V, max = +5.52 V) ALARM
in1: +4.96 V (min = +0.70 V, max = +4.07 V) ALARM
in2: +3.28 V (min = +0.36 V, max = +1.74 V) ALARM
in3: +0.00 V (min = +0.00 V, max = +0.00 V)
in4: +1.13 V (min = +2.96 V, max = +0.08 V) ALARM
in5: +1.80 V (min = +1.08 V, max = +0.58 V) ALARM
in6: -11.87 V (min = -39.23 V, max = -50.17 V) ALARM
in7: +3.26 V (min = +4.49 V, max = +3.53 V) ALARM
in8: +3.34 V
fan1: 2242 RPM (min = 2242 RPM) ALARM
fan2: 0 RPM (min = 693 RPM) ALARM
fan3: 2242 RPM (min = 12 RPM)
temp1: +0.0°C (low = -19.0°C, high = -109.0°C) ALARM sensor = thermistor
temp2: +0.0°C (low = +0.0°C, high = +0.0°C) sensor = thermal diode
temp3: +0.0°C (low = +19.0°C, high = -57.0°C) ALARM sensor = thermal diode
cpu0_vid: +2.050 V# pwmconfig revision 6166 (2013-05-01)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
Found the following devices:
hwmon0/device is coretemp
hwmon1/device is it8721
Found the following PWM controls:
hwmon1/device/pwm1 current value: 0
hwmon1/device/pwm2 current value: 0
hwmon1/device/pwm3 current value: 2
Giving the fans some time to reach full speed...
Found the following fan sensors:
hwmon1/device/fan1_input current speed: 0 ... skipping!
hwmon1/device/fan2_input current speed: 0 ... skipping!
hwmon1/device/fan3_input current speed: 2242 RPM
Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:
Testing pwm control hwmon1/device/pwm1 ...
hwmon1/device/fan3_input ... speed was 2242 now 2235
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon1/device/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon1/device/pwm2 ...
hwmon1/device/fan3_input ... speed was 2242 now 2235
no correlation
No correlations were detected.
There is either no fan connected to the output of hwmon1/device/pwm2,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)
Did you see/hear a fan stopping during the above test (n)?
Testing pwm control hwmon1/device/pwm3 ...
hwmon1/device/fan3_input ... speed was 2242 now 0
It appears that fan hwmon1/device/fan3_input
is controlled by pwm hwmon1/device/pwm3
Would you like to generate a detailed correlation (y)?
PWM 255 FAN 2235
PWM 240 FAN 2220
PWM 225 FAN 2191
PWM 210 FAN 2149
PWM 195 FAN 2083
PWM 180 FAN 2014
PWM 165 FAN 1945
PWM 150 FAN 1859
PWM 135 FAN 1767
PWM 120 FAN 1670
PWM 105 FAN 1558
PWM 90 FAN 1436
PWM 75 FAN 1293
PWM 60 FAN 1138
PWM 45 FAN 960
PWM 30 FAN 6428 (probably incorrect)
PWM 28 FAN 502
PWM 26 FAN 502
PWM 24 FAN 503
PWM 22 FAN 504
PWM 20 FAN 504
PWM 18 FAN 505
PWM 16 FAN 507
PWM 14 FAN 508
PWM 12 FAN 508
PWM 10 FAN 508
PWM 8 FAN 506
PWM 6 FAN 503
PWM 4 FAN 500
PWM 2 FAN 0
Fan Stopped at PWM = 2
Testing is complete.
Please verify that all fans have returned to their normal speed.
The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)?
What should be the path to your fancontrol config file (/etc/fancontrol)?
Loading configuration from /etc/fancontrol ...
Select fan output to configure, or other action:
1) hwmon1/device/pwm3 3) Just quit 5) Show configuration
2) Change INTERVAL 4) Save and quit
select (1-n): 1
Devices:
hwmon0/device is coretemp
hwmon1/device is it8721
Current temperature readings are as follows:
cat: hwmon0/device/temp2_input: Resource temporarily unavailable
/usr/sbin/pwmconfig: line 892: let: S= / 1000: syntax error: operand expected (error token is "/ 1000")
hwmon0/device/temp2_input
cat: hwmon0/device/temp3_input: Resource temporarily unavailable
/usr/sbin/pwmconfig: line 892: let: S= / 1000: syntax error: operand expected (error token is "/ 1000")
hwmon0/device/temp3_input
hwmon1/device/temp1_input 0
hwmon1/device/temp2_input 0
hwmon1/device/temp3_input 0
Select a temperature sensor as source for hwmon1/device/pwm3:
1) hwmon0/device/temp2_input
2) hwmon0/device/temp3_input
3) hwmon1/device/temp1_input
4) hwmon1/device/temp2_input
5) hwmon1/device/temp3_input
6) None (Do not affect this PWM output) - Install 6.1.7 RC5 on your Ultra 6: http://www.readynas.com/forum/viewtopic.php?f=154&t=72282
With 6.1.7 RC5 you won't need to install or use fancontrol.
Welcome to the forum! - AWSOME - thank you so much :-) 6.1.7 RC 5 solves the issue
I was thinking about switching to synology but now my netgear has a UI that is ok and the fans are not running crazy mdgm wrote: Install 6.1.7 RC5 on your Ultra 6: http://www.readynas.com/forum/viewtopic.php?f=154&t=72282
With 6.1.7 RC5 you won't need to install or use fancontrol.
Greetings mdgm!
I've got a quick question for you in this regard. Once I'm ready to install OS6 version 6.1.7 (stable) after it is officially released, should one uninstall or undo all the fancontrol related hacks prior to installing 6.1.7 to insure there won't be any conflicts? Or do you think that the OS updater will take care of all that.
As always, thanks a million for your endless contributions to the ReadyNAS community!- Best to undo the hacks first.
mdgm wrote: Best to undo the hacks first.
Thanks! I just hope I remember how :nashammer:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
