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
Iridabike wrote: To run your script:
1) cd to the directory where your script lives
2) enter the name of your script preceded by ./
With your guidance I think I just figured out what is wrong with my script. See below:root@ReadyNAS-U4:/usr/local/etc/scripts# ./UpdateTempGraph.cron
-bash: ./UpdateTempGraph.cron: Permission denied
I'm guessing I should have made the script executable. . . Correct?
Would the command#chmod +x /usr/local/etc/scripts/UpdateTempGraph.cron
be sufficient? - IridabikeAspirantIf you type these commands :
1) cd /
2) find . | grep syslog
It should search all files for anything with syslog in the name or path
ps -A will list all processes running -try it
ps -A | grep syslogd will list any processes with syslogd in them. I am not sure if os6 has this and can't check right now. - IridabikeAspirantYes your script must have execute rights
Chmod 777 yourscriptname
Should sort it. - ATCISTutor
Iridabike wrote: 2) find . | grep syslog
Results in:root@ReadyNAS-U4:/# find . | grep syslog
./lib/systemd/system/syslog.target
./lib/systemd/system/syslog.socket
./usr/share/perl/5.14.2/syslog.pl
./usr/lib/x86_64-linux-gnu/libc/memcpy-syslog-preload.so
./usr/lib/perl/5.14.2/sys/syslog.ph
./usr/lib/perl/5.14.2/bits/syslog.ph
./usr/lib/perl/5.14.2/bits/syslog-path.ph
./usr/lib/perl/5.14.2/bits/syslog-ldbl.ph
./usr/lib/perl/5.14.2/syslog.phIridabike wrote: ps -A will list all processes running -try it
Results in:root@ReadyNAS-U4:/# ps -A
PID TTY TIME CMD
1 ? 00:00:01 systemd
2 ? 00:00:00 kthreadd
3 ? 00:00:00 ksoftirqd/0
4 ? 00:00:02 kworker/0:0
6 ? 00:00:00 migration/0
7 ? 00:00:00 watchdog/0
8 ? 00:00:00 migration/1
10 ? 00:00:00 ksoftirqd/1
11 ? 00:00:02 kworker/0:1
12 ? 00:00:00 watchdog/1
13 ? 00:00:00 khelper
211 ? 00:00:00 sync_supers
213 ? 00:00:00 bdi-default
215 ? 00:00:00 kblockd
320 ? 00:00:00 khubd
327 ? 00:00:00 md
427 ? 00:00:00 rpciod
428 ? 00:00:02 kworker/1:1
449 ? 00:00:00 khungtaskd
454 ? 00:00:00 kswapd0
519 ? 00:00:00 fsnotify_mark
537 ? 00:00:00 nfsiod
557 ? 00:00:00 xfs_mru_cache
559 ? 00:00:00 xfslogd
560 ? 00:00:00 xfsdatad
561 ? 00:00:00 xfsconvertd
570 ? 00:00:00 crypto
585 ? 00:00:00 kthrotld
661 ? 00:00:00 scsi_eh_0
664 ? 00:00:00 scsi_eh_1
667 ? 00:00:00 scsi_eh_2
670 ? 00:00:00 scsi_eh_3
673 ? 00:00:00 scsi_eh_4
676 ? 00:00:00 scsi_eh_5
680 ? 00:00:04 kworker/u:3
682 ? 00:00:00 kworker/u:5
685 ? 00:00:00 btrfs-endio-met
686 ? 00:00:00 btrfs-worker-2
688 ? 00:00:00 target_completi
689 ? 00:00:00 LIO_rd_mcp
690 ? 00:00:00 iscsi_ttx
691 ? 00:00:00 iscsi_trx
692 ? 00:00:00 iscsi_ttx
693 ? 00:00:00 iscsi_trx
694 ? 00:00:00 iscsi_ttx
695 ? 00:00:00 iscsi_trx
696 ? 00:00:00 iscsi_ttx
697 ? 00:00:00 iscsi_trx
797 ? 00:00:00 btrfs-endio-met
844 ? 00:00:00 btrfs-endio-wri
936 ? 00:00:00 btrfs-endio-met
985 ? 00:00:19 md0_raid1
995 ? 00:00:01 md1_raid6
1020 ? 00:00:00 btrfs-genwork-1
1021 ? 00:00:03 btrfs-submit-1
1022 ? 00:00:00 btrfs-delalloc-
1023 ? 00:00:00 btrfs-fixup-1
1028 ? 00:00:00 btrfs-freespace
1029 ? 00:00:00 btrfs-delayed-m
1030 ? 00:00:00 btrfs-cache-1
1031 ? 00:00:00 btrfs-readahead
1032 ? 00:00:00 btrfs-cleaner
1033 ? 00:00:05 btrfs-transacti
1050 ? 00:00:00 sleep
1051 pts/0 00:00:00 ps
1065 ? 00:00:02 kworker/1:2
1079 ? 00:00:03 systemd-journal
1084 ? 00:00:00 udevd
1110 ? 00:00:16 md127_raid5
1133 ? 00:00:00 btrfs-genwork-1
1134 ? 00:00:02 btrfs-submit-1
1135 ? 00:00:00 btrfs-delalloc-
1136 ? 00:00:00 btrfs-fixup-1
1137 ? 00:00:00 btrfs-endio-1
1140 ? 00:00:00 btrfs-endio-wri
1141 ? 00:00:00 btrfs-freespace
1142 ? 00:00:00 btrfs-delayed-m
1143 ? 00:00:00 btrfs-cache-1
1144 ? 00:00:00 btrfs-readahead
1744 ? 00:00:00 flush-btrfs-1
1747 ? 00:00:00 btrfs-endio-met
1748 ? 00:00:00 btrfs-cleaner
1749 ? 00:00:14 btrfs-transacti
1758 ? 00:00:05 avahi-daemon
1763 ? 00:00:00 mdadm
1767 ? 00:00:01 connmand
1768 ? 00:00:00 bond0
1808 ? 00:00:00 rsync
1829 ? 00:00:00 acpid
1848 ? 00:00:00 raidard
1850 ? 00:00:00 udevd
1851 ? 00:00:00 udevd
1854 ? 00:00:00 cron
1857 ? 00:00:00 leafp2p
1859 ? 00:00:00 sshd
1871 ? 00:00:00 avahi-daemon
1872 ? 00:00:00 systemd-logind
1878 ? 00:00:00 dbus-daemon
1905 tty1 00:00:00 agetty
1908 ttyS0 00:00:00 agetty
1982 ? 00:00:29 leafp2p
1994 ? 00:00:00 btrfs-endio-met
2003 ? 00:00:17 fancontrol
2166 ? 00:00:02 nmbd
2168 ? 00:00:04 winbindd
2170 ? 00:00:01 smbd
2171 ? 00:00:00 winbindd
2172 ? 00:00:00 winbindd
2173 ? 00:00:01 winbindd
2174 ? 00:00:00 winbindd
2175 ? 00:00:00 smbd
2176 ? 00:00:01 apache2
2177 ? 00:00:01 apache2
2178 ? 00:00:01 apache2
2179 ? 00:00:00 apache2
2180 ? 00:00:00 apache2
2182 ? 00:07:44 readynasd
2186 ? 00:01:50 qbittorrent-nox
2282 ? 00:01:07 usbhid-ups
2284 ? 00:00:02 upsd
2288 ? 00:00:00 upsmon
2289 ? 00:00:01 upsmon
2381 ? 00:00:00 fvbackup-q
2387 ? 00:00:00 minissdpd
2388 ? 00:00:00 upnphttpd
2395 ? 00:00:00 rcbrokerd
4400 ? 00:00:00 apache2
4507 ? 00:00:00 apache2
6006 ? 00:00:00 flush-btrfs-2
10321 ? 00:00:02 btrfs-worker-2
11370 ? 00:00:00 apache2
11454 ? 00:00:00 apache2
14476 ? 00:00:00 btrfs-worker-3
19608 ? 00:00:00 btrfs-endio-met
23922 ? 00:00:00 rcbrokerd
24327 ? 00:00:00 btrfs-endio-met
25473 ? 00:00:00 btrfs-endio-wri
28336 ? 00:00:00 apache2
28339 ? 00:00:00 btrfs-endio-2
28367 ? 00:00:00 apache2
29043 ? 00:00:00 btrfs-worker-4
30098 ? 00:00:00 sshd
30244 pts/0 00:00:00 bash
30554 ? 00:00:00 btrfs-endio-met
32149 ? 00:00:00 btrfs-endio-met
32631 ? 00:00:00 btrfs-endio-wri
32632 ? 00:00:00 btrfs-endio-wriIridabike wrote: ps -A | grep syslogd
Results in --> Absolutely nothing. . . :-?
Is it just me, or does anyone else think that is bizarre? - ATCISTutorIn case anyone cares. . . I finally got the graph working!
As it turns out it was likely a permissions problem ALL ALONG :oops:
Still something not quite right though. I just checked the ambient room temperature which is approximately 82 degrees F. How can the CPU temperature be 79 degrees F? As I watch the graph over time both temperatures are dropping slightly every minute. The System temperature seems reasonable. It is currently 97 degrees F. I'll keep an eye on things for a while and report back later. . . - ATCISTutorSo now that I have the temperature graph working (kind of), the next step is to work out a few details. So this is what the top of my Performance GUI looks like:

and this is what the temperature graph looks like now:
So my questions are:
1.) As you can see from the upper screenshot, both fans indicate 5355 RPM's in spite of running through the "pwmconfig" instructions detailed previously in this thread. Can I assume that by running OS6 on legacy hardware that those numbers will never represent actual fan speeds?
2.) Based on what I saw during the pwmconfig process, is it safe to assume that the Ultra 4 has no CPU fan at all?
3.) Likewise, are the three graphical thermometers and their corresponding values also just static images and text? I ask because i have NEVER seen any of them change to any other value than what you see above.
4.) If number 3 above is true, why do you suppose that the CPU value is 5 degrees (F) higher than the other two?
Thoughts from the ReadyNAS community at large welcomed. . . - IridabikeAspirantThe graph temps are wrong because readynasd is writing false info to the rrd file every minute as well as your script.
This is why it needs patching as described previously. - ATCISTutor
Iridabike wrote: The graph temps are wrong because readynasd is writing false info to the rrd file every minute as well as your script.
This is why it needs patching as described previously.
Gotchya. . . Again, that task is above the effort I'm willing to go. I just finished turning my little old Ultra 4 into an eight Camera IP Surveillance Network Video Recorder without having to pay NTGR's exorbitant $400 licensing fee. :woot:
I think I'll just be happy with what I've got going on for now; and see if any creative and talented community members attempt to resolve some of these GUI shortfalls on legacy hardware sometime in the future. Thanks again for your help earlier!
Signing off for now. . .
Best wishes, - xmansssAspirantHi,
In my Pro 6 the temperature bars are decreasing as well. My box reads values from the file /run/readynasd/stats/temperature_int_deg.rrd abou 10 sec after the minute and then writes the new values to the file at about 56 sec. after the minute. It looks for me that the value read 10 sec after the minute references the minute before. So my quick fix is to make a copy of temperature_int_deg.rrd file modify the script provided by Iridabike so that it updates the copy and overwrites the file temperature_int_deg.rrd with the copy before 10 sec after the minute. So my script looks like:
#!/bin/sh
#######################################################
sleep 30
Coretemp="/sys/devices/platform/w83627ehf.2576/temp1_input"
Systemp="/sys/devices/platform/w83627ehf.2576/temp2_input"
Ct=`/bin/cat $Coretemp`
C=`/usr/bin/expr $Ct / 1000`
St=`/bin/cat $Systemp`
S=`/usr/bin/expr $St / 1000`
/usr/bin/rrdtool update /run/readynasd/stats/temperature_int_deg.rrd.custom N:$C:$S
sleep 30
cp -f /run/readynasd/stats/temperature_int_deg.rrd.custom /run/readynasd/stats/temperature_int_deg.rrd
It works for me just fine. I hope that helps.
P.S.
I'm still looking for a solution on updating the values under those nice temperature and fan animations :D . - ATCISTutor
xmansss wrote: It works for me just fine. I hope that helps.
Dear xmansss,
Thank you for sharing your idea. Perhaps I'll give that a try after I get some sleep :shhh:xmansss wrote: P.S.
I'm still looking for a solution on updating the values under those nice temperature and fan animations .
Well, if you do happen to figure that out, please do come back and share how you did it!
Take care,
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!