NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN Ultra 6 - System Temp
Hi all, I have a ReadyNas Ultra 6 with 6 x 4TB WD Red HDD's and all working fine for a couple of years now and running on OS 6.10.5 Hotfix 1. Over the last few weeks I have noticed that the NAS ...
Hi StephenB,
My apologies - I actually have both but in this case it is the ReadyNas Ultra 6.
The ReadyNas (all) shutdown at about 2am and restart at 10am (my time GMT)
Disk Health seems to be good as no errors at all shoiwng for any of the drives.
Upon Looking for errors in the disk_info.log - I found none
The same with the kernel.log.
There were errors in the system.log - all refering to "apache" eg:
Sep 07 00:36:40 Ombiplex-2 apache2[11496]: [:error] [pid 11496] [client 192.168.1.128:65392] mod_csrf(020): request denied, expired id (26 sec), action=deny, id=-, referer: http://192.168.1.106/admin/index.html
There were a lot of failures for "snapperd" - eg:
Sep 07 01:00:06 Ombiplex-2 snapperd[14222]: loading 213 failed
The WD RED's are actually FYYZ !!
I will wait before running disk test and volume balancing in case the above tell you something or as you say Sandshark may jump in with something.
Thank you for the reply.
Regards
NJP
niallryan wrote:
The WD RED's are actually FYYZ !!
Those are not WD Reds. WD4000FYYZ are WD Re (datacenter) drives.
niallryan wrote:There were a lot of failures for "snapperd" - eg:
Sep 07 01:00:06 Ombiplex-2 snapperd[14222]: loading 213 failed
That does suggest some file system corruption - the NAS is trying to access snapshots, and is unable to. Not great, but I don't think it explains the performance issues.
niallryan wrote:
I will wait before running disk test and volume balancing in case the above tell you something or as you say Sandshark may jump in with something.
I'd proceed with the disk test.
The reported system temperature does rely on a sensor that can go bad. If dust at the sensor was the problem, it would typically be too low. But a poorly working fan can come into play.
The reported (and acted upon) temps also rely in the sensor configuration used by lm_sensors. So, let's make sure that's right. From ssh, execute
ls ./etc/sensors.d/ -all
You should see that is points to the ULTRA6 configuration:
system.conf -> /etc/frontview/sensors/ULTRA6.conf
Then do
cat /etc/frontview/sensors/ULTRA6.conf
And one of the sections should be:
label temp2 "System"
But here is something odd:
chip "coretemp-isa-0000"
label temp2 "CPU"
compute temp2 @%35, @%35I don't see % being a valid operator in lm_sensors. So, I think that's just assigning 35°C to be the reported CPU temperature, because either the chip doesn't really provide it or it's considered unreliable. That you say the CPU is "solid" at 35 seems to confirm that. So, perhaps restricted air flow or poor conduction between the CPU and it's heat sink are problematic.
I no longer have an Ultra6 and only ever used it as a backup, so I never really paid attention to the temperatures since they were never reported as too high. Maybe somebody else can let you know if the Ultra6 system temperature typically runs high.
Hi Sandshark ,
Many thanks for jumping on board.
The reported (and acted upon) temps also rely in the sensor configuration used by lm_sensors. So, let's make sure that's right. From ssh, execute
ls ./etc/sensors.d/ -all
I logged into the NAS in question and entered the command above and got the "No such file or directory" response.
Regards
NJP
niallryan wrote:
Hi Sandshark ,
Many thanks for jumping on board.
The reported (and acted upon) temps also rely in the sensor configuration used by lm_sensors. So, let's make sure that's right. From ssh, execute
ls ./etc/sensors.d/ -all
I logged into the NAS in question and entered the command above and got the "No such file or directory" response.
Regards
NJP
Try
ls /etc/sensors.d/ -all
(leaving off the initial .)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
