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
- ATCISTutor
StephenB wrote: The RN102/RN104 are OS6 only.
You can see the picture in the "performance" tab. However, the graphs are not available on the RN1xx. Per the manual:
I'm not sure why this limitation is there, but I wish it weren't.Note: Status graphics are not supported for ReadyNAS 102 and 104 systems.
Unbelievable. . . Why would someone sell a product that was less than 100% functional right out of the box (and at least 8 firmware updates later)? Especially considering that a legacy device such as the Ultra 4 is about 90% functional without requiring any hard core hacking. I just don't get it. . . - mdgm-ntgrNETGEAR Employee RetiredThe resources required for the graphics might put too much load on low powered systems such as the 102/104.
- ATCISTutor
mdgm wrote: The resources required for the graphics might put too much load on low powered systems such as the 102/104.
Interesting hypothesis. Just curious, by that do you mean while someone is actually viewing the Performance page in the Web GUI, or generating the historical data in the background?
Unfortunately I don't know much about the Marvell Armada 370, but in theory, how does it compare (performance wise) to an Intel Atom D410 CPU like the one found in the Ultra 4? I am consistently amazed at how much work that single core low power CPU can perform. Mine pulls and processes six H.264 video streams (from surveillance cameras) 24/7/365, and the CPU utilization rarely peaks over 50% utilization. Considering how much (perhaps I should have said "how little") it cost me, I must say I couldn't be happier with it. :-D - mdgm-ntgrNETGEAR Employee RetiredIntel CPUs even the one in the Ultra 4 are much faster than the Marvell Armada 370-and the Ultra 4 has double the RAM of the 102/104.
- ATCISTutor
mdgm wrote: Intel CPUs even the one in the Ultra 4 are much faster than the Marvell Armada 370-and the Ultra 4 has double the RAM of the 102/104.
Wow, fascinating stuff. I must say mdgm, the wealth of information that you possess never fails to amaze me :) - StephenBGuru - Experienced UserIf someone were to post a how-to with instructions on installing a performance benchmark program on the various ReadyNAS, I think it there would be enough interest to get results from most (if not all) of the platforms.
- Hi guys,
I have now taken the plunge and installed OS6 on my Pro, however, I really need some guidance in terms of stabilising my fan control speeds as well as getting the temp graphs to work.
Thus far I have ready the forum posts and have done the following:
Step 1apt-get update && apt-get upgrade
apt-get install lm-sensors fancontrol
echo "#fancontrol" > /etc/fancontrol
Step 2
Used the powerconfig command as suggested http://www.readynas.com/forum/viewtopic.php?f=51&t=71155#p395324
Step 3/etc/init.d/fancontrol stop
/etc/init.d/fancontrol start
/etc/init.d/fancontrol restart
Here is the output after sensors:root@READYNASPRO:/sys/devices/platform/coretemp.0# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +27.0 C (high = +84.0 C, crit = +100.0 C)
Core 1: +27.0 C (high = +84.0 C, crit = +100.0 C)
Core 2: +21.0 C (high = +84.0 C, crit = +100.0 C)
Core 3: +21.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.74 V (min = +0.84 V, max = +1.89 V)
AVCC: +3.20 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.20 V (min = +2.98 V, max = +3.63 V)
in4: +1.22 V (min = +0.38 V, max = +1.32 V)
in5: +1.49 V (min = +0.09 V, max = +0.30 V) ALARM
in6: +1.02 V (min = +0.95 V, max = +1.05 V)
3VSB: +3.17 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.07 V (min = +2.70 V, max = +3.63 V)
fan1: 1004 RPM (min = 42187 RPM, div = 8) ALARM
fan2: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan3: 3125 RPM (min = 3375 RPM, div = 8) ALARM
fan4: 0 RPM (min = 5273 RPM, div = 128) ALARM
fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM
temp1: +46.0 C (high = +127.0 C, hyst = +125.0 C) sensor = thermistor
temp2: +24.5 C (high = +80.0 C, hyst = +123.0 C) sensor = CPU diode
temp3: +19.5 C (high = +80.0 C, hyst = +123.0 C) sensor = thermistor
cpu0_vid: +0.000 V
Fancontrol file#fancontrol
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/w83627ehf.2576
DEVNAME=hwmon0=coretemp hwmon1=w83627dhg
FCTEMPS= hwmon1/device/pwm2=hwmon1/device/temp2_input hwmon1/device/pwm1=hwmon1/devic
FCFANS= hwmon1/device/pwm2=hwmon1/device/fan2_input hwmon1/device/pwm1=hwmon1/device/
MINTEMP= hwmon1/device/pwm2=30 hwmon1/device/pwm1=55
MAXTEMP= hwmon1/device/pwm2=60 hwmon1/device/pwm1=60
MINSTART= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MINSTOP= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MINPWM= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MAXPWM= hwmon1/device/pwm2=200 hwmon1/device/pwm1=80
I have modded by Pro with a q6600.
Any help would be appreciated. - Update!
I have graphing in Frontview and have been able to regulate my fans.
Here is the lm-sensors vs the Frontview readings for the fans:
Output from lm-sensors OS6
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +39.0 C (high = +84.0 C, crit = +100.0 C)
Core 1: +40.0 C (high = +84.0 C, crit = +100.0 C)
Core 2: +31.0 C (high = +84.0 C, crit = +100.0 C)
Core 3: +32.0 C (high = +84.0 C, crit = +100.0 C)
w83627dhg-isa-0a10
Adapter: ISA adapter
Vcore: +1.19 V (min = +0.00 V, max = +1.74 V)
in1: +1.73 V (min = +0.84 V, max = +1.89 V)
AVCC: +3.20 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.20 V (min = +2.98 V, max = +3.63 V)
in4: +1.22 V (min = +0.38 V, max = +1.32 V)
in5: +1.49 V (min = +0.09 V, max = +0.02 V) ALARM
in6: +1.02 V (min = +0.94 V, max = +1.04 V)
3VSB: +3.17 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.07 V (min = +2.70 V, max = +3.63 V)
fan1: 1180 RPM (min = 10546 RPM, div = 8) ALARM
fan2: 0 RPM (min = 5273 RPM, div = 128) ALARM
fan3: 2311 RPM (min = 831 RPM, div = 8)
fan4: 0 RPM (min = 5273 RPM, div = 128) ALARM
fan5: 0 RPM (min = 1054 RPM, div = 128) ALARM
temp1: +49.0 C (high = +127.0 C, hyst = +125.0 C) sensor = thermistor
temp2: +35.0 C (high = +80.0 C, hyst = +123.0 C) sensor = CPU diode
temp3: +18.5 C (high = +80.0 C, hyst = +123.0 C) sensor = thermistor
cpu0_vid: +0.000 V
OS 4.2.25Fan SYS 912 RPM OK
Fan CPU 2057 RPM
Fancontrol file for Pro
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/w83627ehf.257
DEVNAME=hwmon0=coretemp hwmon1=w83627dhg
FCTEMPS=hwmon1/device/pwm3=hwmon0/device/temp2_input hwmon1/device/pwm1=hwmon1/d
FCFANS=hwmon1/device/pwm3=hwmon1/device/fan3_input hwmon1/device/pwm1=hwmon1/dev
MINTEMP=hwmon1/device/pwm3=20 hwmon1/device/pwm1=10
MAXTEMP=hwmon1/device/pwm3=65 hwmon1/device/pwm1=25
MINSTART=hwmon1/device/pwm3=28 hwmon1/device/pwm1=16
MINSTOP=hwmon1/device/pwm3=26 hwmon1/device/pwm1=14
MINPWM=hwmon1/device/pwm3=16 hwmon1/device/pwm1=14
MAXPWM=hwmon1/device/pwm3=28 hwmon1/device/pwm1=22
I have done various tests and can report the following regarding OS 6.1.5:
1. OLED on Pro Box remains lit
2. WOL does not work
3. Readynas Drop, Readynas Cloud, Readynas Replicate, Readynas Remote all work!
4. Temperature graphs work (after applying fix as suggested in this forum)
5. Status animations (ie. Fans, Aux, etc.) do not work.
6. Addons work flawlessly
7. Hard drive temperatures are 8-10 degrees (i.e OS6:32c 4.2.25: 40c)
All in all, OS6 is a huge improvement from 4.2.25. Frontview boots up faster, services work wonderfully.
I am presently running a Pro with 4gigs of Ram and a Q6600 cpu.
Thanks. - arnomcAspirantSince 6.0.6 I don't have anymore the fan spinning like crazy so I didn't bothered to apply any fix, neither paid much attention to the temp that I suspected to be higher than reality.
My Ultra2 is now under 6.1.6, and today I finally did a Factory default to benefit from the NTRFS bug fix. After this factory default, I noticed that the temperatures where, now, correctly displayed (my NAS is on a balcony close to fridge temperature).
Well I was happy to see the system temp at 16°C, hdd temps at 21-22°C and CPU at 31°C. Then I restored the config file to gain the users accounts etc.. Here my problems is that the temp displayed came back to the faulty readings : all temps are increased by 5 to 10°C higher !
My question is : If I do an OS reinstall would it solve this temps reading problem ? I don't mind reconfiguring the NAS if I have to, but what I want to avoid is that after putting all my data back (2-3days..) then realizing that I need to do again a factory default !! (and then rebuild volume and put back everything again...).
your knowledge would be really helpful to save me a lot to time and hassle !!
thanks
note: i checked that I don't have any process burning the cpu/syst temp. - arnomcAspirantFinally I tried an OS reinstall and I had same kind of temperature. Then I started a Factory Default, and I will soon see what temperature I will have.
I have look on the temps a third morning (same weather conditions) and they were in-between the first and second reading. the cpu temp is just easy to leave 35°C when complete idle, and with just 5% activity it goes fast to 42°C or more. I guess such a climb is due to the fact that it is nearly passively cooled (the only fan is not exactly on top of it). I'll leave it here as I never had the noise of the fan at full speed.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!