Easy fix fan/temp OS6 issues on x86 legacy #no support

Yes the OLED display was turned off automatically in OS4. Momentarily press the power button and you can see the hostname and I.P. again.

mdgm wrote:
Yes the OLED display was turned off automatically in OS4. Momentarily press the power button and you can see the hostname and I.P. again.

I will try this when I get home.
Thank you for the information.

I'm on OS4 (Ultra 6) now and can confirm the display turns off and a momentary press brings it back up.

So about to make the switch straight to 6.1.7 and from what I've been reading I shouldn't have any fan issues with that version. Are there any other traps, I've been trawling through the forums and nothing is standing out at me except:

1/ Do not enable Antivirus.

I installed Antivirus on OS6 (Pro4) once. He will load all 4 threads to 100%! Never again ;)

yehh thanks shibby seems to be some issue with Anti-Virus on legacy boxes with OS6.

I did the upgrade a couple days ago and everything went well, except I forgot to do a factory reset so I freaked out a little when my NAS was sitting there saying "Booting..." for ages.

The only thing I've noticed is the CPU temp isn't correct. IT's sitting at 13c now which is less than the ambient room temp so guessing the sensor readout needs modding. I'm just assuming it starts around 30c when it reads 0c (actually read -1c when it booted up) and I'll count up from there.

Hi.

I have just updated my Pro2 from 6.0.6 to 6.1.7.
I love that fancontrol works in this release, but it runs the fans too slow for me.
Empty nas, rebuilding volume after a factory reset, and the CPU hit's 80C (177F), and the disks are about 45C(113F).
That's a bit much for me (I know the CPU is good for it, but that doesn't mean I like it :) )

I have my own fancontrol script that uses lm-sensors and set's the /sys/devices/platform/it87.2576/pwm1 file every minute through crontab.
Will it be a problem if I set it up to run my script again?
Will my script and the built-in fancontrol compete, making the fan jump like a yo-yo? Is that a problem?
Is there perhaps any way to make the built in fancontrol a bit more agressive?


brgds
Royan

Edit: Pro2
Edit2: lm-sensors

Hi all,

This is my first post after several years of browsing/lurking in this forum, searching for advice and ideas. I want to start with a big THANK YOU!!! to everyone who contributes and makes this community so valuable for ReadyNAS users. I owe it to you and your advice that my boxes are running smoothly (CPU + RAM upgrades) and silently (Noctua fan upgrades) since 2007, and my data is fully secure and available (I learnt here that "a RAID is not a backup" before it was too late...).

Now, to the reason for my post today…

I just updated my ReadyNAS Pro 6 from 6.1.4 to OS6.1.7, and I'm having a few annoying side effects:

• Fan speed alert every 15 minutes: "Fan 'Fan' in enclosure 'Internal' speed is below threshold. (-2 rpm)", as reported by renedis and others several posts back in this thread.
  


• Fan and temperature graphs at the top of the Performance tab in Frontview have been reduced from 2 fans + 3 temps in every OS6 version (up to 6.1.4, at least) to 1 fan + 2 temps now. The only positive is that one of them is working now: 'CPU' shows the actual temperature of one of the CPU cores (temp1_input). The other temperature graph and the fan graph are incorrect (-2 ºC and -2 rpm, respectively). Still, this is an improvement over the 5 frozen graphs prior to the update.

Some additional comments:

• I did not disable the fancontrol and lm-sensors mods prior to updating to 6.1.7 since I read mixed feedback on the fan speeds for legacy boxes, and they were working flawlessly for me. They are still enabled, fans continue adjusting smoothly to internal temperature and sensors continues to provide accurate information, so I am reluctant to disable them unless needed. Sensors output is the following: (non-functional fan sensors -#3, #4 & #5- and temp sensor -#3- are ignored by the modded conf file, so they are not shown)
  

  
  root@______-NAS:~# sensors
  coretemp-isa-0000
  Adapter: ISA adapter
  Core 0:       +51.0 C  (high = +84.0 C, crit = +100.0 C)
  Core 1:       +48.0 C  (high = +84.0 C, crit = +100.0 C)
  Core 2:       +44.0 C  (high = +84.0 C, crit = +100.0 C)
  Core 3:       +48.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)
  V_in1:        +1.76 V  (min =  +1.58 V, max =  +1.93 V)
  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)
  V_in4:        +1.25 V  (min =  +1.13 V, max =  +1.38 V)
  V_in5:        +1.50 V  (min =  +1.35 V, max =  +1.65 V)
  V_in6:        +1.04 V  (min =  +0.90 V, max =  +1.10 V)
  3VSB:         +3.22 V  (min =  +2.98 V, max =  +3.63 V)
  Vbat:         +3.18 V  (min =  +2.70 V, max =  +3.63 V)
  System Fan:  1268 RPM  (min = 1004 RPM, div = 8)
  CPU Fan:     1704 RPM  (min = 1004 RPM, div = 8)
  Sys temp:     +64.0 C  (high = +70.0 C, hyst = +125.0 C)  sensor = thermistor
  CPU temp:     +38.5 C  (high = +80.0 C, hyst = +123.0 C)  sensor = CPU diode
  cpu0_vid:    +0.000 V
  
  root@______-NAS:~# 
  



• Temperature graphing in Frontview (bottom of Performance tab), which was working before thanks to the UpdateTemp script, is working again after recovering the /etc/crontab mods, that were reset after the update.
  
  With the default settings in 6.1.7, Frontview was showing only one line in that graph: 'CPU Temperature', showing the same CPU core #1 value as in the thermometer at the top of that tab (50ºC); the other line, 'System Temperature', was flat at 0. These values were aligned with the indicators at the top of the Performance tab.
  

My questions are:
[list=a:2cycfgzc]

Any suggestions on how to get rid of the fan alert? It would be nice to begin by knowing which fan is causing the alert. This Pro 6 (v2) has 3 non-functional fan sensors, but their value is 0, not -2

Has anyone managed to get the fan & temperature graphs working on a Pro 6 running 6.1.7? Any clues about why there are fewer of them than in previous versions? Have people with other Ultra/Pro units experienced this?

Any ideas about where Frontview stores its config files and which format they use? Has anyone tried to modify them?

Thanks in advance!

Hi Evelez,

I have a Pro6 v2 as well. Bios is the latest version (Flame 2.0). Installed a clean 6.1.6 and then "upgraded" to 6.1.7 using the OS6 firmware upgrade.
The fan alert comes up as yours when rpm go below 700 or something. Had to disable the alert in the settings to avoid getting flooded with email alerts. CPU shows 38C which is correct as well as the SYS with 58C. Only one fan shows but the unit has alt least one more (and the power supply fan).
Looks like we have similar issues only difference is your lmsensor "mod". You may want to do a clean OS 6.1.7 install to get the SYS temp to work but that might be overkill since it wont fix the fan alert - at least it didnt mine.

I have a pro6 v2. I upgraded for the first time from v4.2.26 to v6.1.8. No hack.

Here is what I have regarding temperature and fan:
CPU temp. graph at 39 deg. constant
System temp graph between 53 and 62 deg.
Fan diagram regularly going from 150 rpm to 1600 rpm which seems to be in line with system temperature fluctuations

My only concerns (which seems to be observed by others as well)
* I have only one graph for the Fan, while I assume there is also a CPU fan
* I have regular alerts regarding Fan speed: "Fan 'Fan' in enclosure 'internal' is below threshold (480 rpm)". The value varies here.

It seems the fan speed slows down too brutally (I observed it dropping from 800 to 480 rpm and then to 150 rpm when system temperature allows it). So it is maybe a problem with fan speed regulation

My question: should I be worried about the alert and do something (some kind of hack) or should I just ignore the alert?

I've the same slow fan problem on two ReadyNAS Pros and don't know what to do about it either. I disabled the fan alerts for now because they became too annoying.

Sent from my Nexus 5 using Tapatalk