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 has been running pretty sluggish. I have 4.25TB free of 18.17TB Also I have noticed that the System Temp is always hovering between 71ºC and 73ºC - the CPU temp is always at 35ºC and each of the HDD's vary between 30ºC and 35ºC. Any particular reasons for this and is the sluggishness relatied to the system temp. The NAS is located in a very large room with plenty of ventilation. The fan is always on Cool and running around 1630 - 2040 rpm approx.Bit rot protection is never on from day one. Many thanks in advance. NJP

niallryan wrote: Also I have noticed that the System Temp is always hovering between 71ºC and 73ºC - the CPU temp is always at 35ºC and each of the HDD's vary between 30ºC and 35ºC. Your post title says you have the Ultra 6, but your model number choice is an Ultra 6 Plus. If you want to compare temps with other users, we'll need to clear up what you have. The disk and CPU temps are fine, but system temp does seem high for an Ultra-6, hopefully Sandshark will chime in. I guess you could open the back, and see if there's a lot of dust in the case fan. But I think if you had a fan issue you'd be seeing higher disk temps. niallryan wrote: Over the last few weeks I have noticed that the NAS has been running pretty sluggish. If you haven't tried rebooting, then I suggest doing that first. I'd check the disk health. You can download the full log zip, and look at the SMART stats in disk_info.log, and look for errors generally in system.log and kernel.log. You could also run the disk test from the volume settings wheel (which will take a while). If we can rule out the disks, then I'd suggest running a balance from the volume settings wheel. That can take a while too - though the longer it takes, the more it is needed. niallryan wrote: I have a ReadyNas Ultra 6 with 6 x 4TB WD Red HDD's and all working fine for a couple of years now WD40EFRX? Or WD40EFAX? Hopefully the former. The current WD Red line is all SMR, the current WD Red Plus line is CMR. The WD40EFRX is now in the Red Plus line. How much memory do you have?

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/ -allYou should see that is points to the ULTRA6 configuration: system.conf -> /etc/frontview/sensors/ULTRA6.confThen do cat /etc/frontview/sensors/ULTRA6.confAnd one of the sections should be: label temp2 "System" But here is something odd: chip "coretemp-isa-0000" label temp2 "CPU" compute temp2 @%35, @%35 I 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.

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 .)

niallryan wrote: Earlier StephenB you mentioned to carry out a disk test. I presume you mean using the following options: Scrub, Defrag, Balance, Disk Test. Which order should these be perfomed and would my data be secure I was thinking the disk test first. Scrub and Balance might also be useful - balance might improve your performance. Personally I use the maintainance schedule to run one of these tests every month. niallryan wrote: I know you will say ensure a backup is carried out but should the data be safe even though the disks will have an increased load while tsting, Yes, consider that said... But the tests themselves are safe, the risk is only that disks might fail while they are running.

RN Ultra 6 - System Temp | NETGEAR Communities

19 Replies

StephenB
Guru
Sep 07, 2021
niallryan wrote:

Also I have noticed that the System Temp is always hovering between 71ºC and 73ºC - the CPU temp is always at 35ºC and each of the HDD's vary between 30ºC and 35ºC.

Your post title says you have the Ultra 6, but your model number choice is an Ultra 6 Plus. If you want to compare temps with other users, we'll need to clear up what you have.

The disk and CPU temps are fine, but system temp does seem high for an Ultra-6, hopefully Sandshark will chime in. I guess you could open the back, and see if there's a lot of dust in the case fan. But I think if you had a fan issue you'd be seeing higher disk temps.

niallryan wrote:

Over the last few weeks I have noticed that the NAS has been running pretty sluggish.

If you haven't tried rebooting, then I suggest doing that first.

I'd check the disk health. You can download the full log zip, and look at the SMART stats in disk_info.log, and look for errors generally in system.log and kernel.log. You could also run the disk test from the volume settings wheel (which will take a while).

If we can rule out the disks, then I'd suggest running a balance from the volume settings wheel. That can take a while too - though the longer it takes, the more it is needed.

niallryan wrote:
I have a ReadyNas Ultra 6 with 6 x 4TB WD Red HDD's and all working fine for a couple of years now

WD40EFRX? Or WD40EFAX? Hopefully the former. The current WD Red line is all SMR, the current WD Red Plus line is CMR. The WD40EFRX is now in the Red Plus line.

How much memory do you have?
- niallryan
  Guide
  Sep 07, 2021
  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
  - StephenB
    Guru
    Sep 07, 2021
    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.

Forum Discussion

RN Ultra 6 - System Temp

19 Replies

Related Content

Orbi Systems Manual Factory Reset Process

Blocked telemetry system

System down for maintenance

Enabling SSH access on Readynas Ultra 2

Rbk653Mesh System

NETGEAR Academy

ProSupport for Business