ReadyNAS Pro: System temp running out of spec

Is your chassis fan working? Is it full of dust? How long have you had your Pro?

mromanch wrote:
Can somebody at least let me know what temperature sensor 2 is measuring?

It is the case or general system temp.

Edit 1/19 - I stand corrected - s/b CPU temp.

temp2 is CPU as i have stated above.

My question stands. If your chassis fan cannot remove the hot air, the CPU fan will have to work harder and the CPU could run hotter.

Sorry for the delay in my response. I appreciate your help with this. I was not able to look at the system until just a few days ago, and I had it powered off in then meantime.

I bought my Pro in March of 2009. My chassis fan was clean, inside and out. (Also note that the reading from sensor 1 was always constant during the alarm periods.) I decided to open the case and look inside. The CPU fan was not bad, there was some dust on the cooling block fins, but it didn't look sufficient to me to cause the sudden temperature changes I have been seeing. I decided to inspect/replace the thermal paste on the cooling block. Based on my inspection, I do not believe that there was a good bonding between the thermal grease and the metal cap of the CPU package. I base this on the following: 1) when I removed the cooling block, all the thermal grease remained on the cooling block; 2) there was not even any tinting on the metal cap caused by the thermal grease. I'm not sure what brand thermal grease was used, but according to the Arctic Silver website these are both indications of a poor bond.

Replacing the thermal paste seems to have solved my problem. I did all this Friday evening and have had no issues since then. Prior to this, even when I was not seeing warning, temperatures from sensor 2 seemed to run between 45-60C. It now runs under 30C. My consistency check ran today without any heating issues.

Sorry to dig up this old thread, but I can't find anything more relavent in search.

I have a new ReadyNAS Pro 6 and I'm getting constant warnings regarding the Temp SYS hitting 66C. These are the current readings:
Device Description Status
Disk 1 WDC WD1003FBYX-01Y7B0 931 GB , 42 C / 107 F , Write-cache ON OK
Disk 2 WDC WD1003FBYX-01Y7B0 931 GB , 43 C / 109 F , Write-cache ON OK
Disk 3 WDC WD1003FBYX-01Y7B0 931 GB , 43 C / 109 F , Write-cache ON OK
Fan SYS 2250 RPM OK
Fan CPU 2109 RPM OK
Temp SYS 64 C / 147 F [Normal 0-65 C / 32-149 F] OK
Temp CPU 38 C / 100 F [Normal 0-85 C / 32-185 F] OK

What is the Temp SYS supposed to be measuring? I'm surprised to see a system temp higher than a CPU or HDD temp, since they're usually the source of the system's heat!

I should also point out that the air being pushed out from the side of the unit seems quite cool.

Anybody know if this is likely to be a fault?

I'm running the latest firmware.

rickwookie wrote:
I have a new ReadyNAS Pro 6 and I'm getting constant warnings regarding the Temp SYS hitting 66C.

If it was a firmware issue we'd likely be seeing multiple people reporting virtually identical symptoms, which we're not.

So I'd be suspicious there is a hardware issue with your NAS & I'd strongly recommend you contact Netgear directly. If the unit is new you have 90 days telephone support from Netgear.

Setting up a new ReadyNAS Pro 6 with the RAIDiator 4.2.20 T19 beta, I am also getting what appears to be a swapped SYS and CPU temp reading. I'm not getting temperature warnings, as it's still within the allowable range (~58C for the "SYS" temp and 38C for the "CPU"), but it's still suspicious.

Searching the forums, I suspect it's a firmware issue. If you look at:

http://www.readynas.com/forum/viewtopic.php?f=24&t=58787&p=330566#p330564
(too new to make that a link)

someone else posted a copy/paste from their Pro 6:

interested wrote:

Here is my Status log from PRO6 by outside temp. 3 C: Disk 1 Seagate ST32000542AS 1863 GB , 27 C / 80 F , Write-cache ON OK Disk 2 Seagate ST32000542AS 1863 GB , 26 C / 78 F , Write-cache ON OK Disk 3 Seagate ST32000542AS 1863 GB , 27 C / 80 F , Write-cache ON OK Disk 4 Seagate ST32000542AS 1863 GB , 21 C / 69 F , Write-cache ON OK Fan SYS 892 RPM OK Fan CPU 2280 RPM OK Fan CAS 1854 RPM OK Temp SYS 39 C / 102 F [Normal 0-65 C / 32-149 F] OK Temp CPU 15.5 C / 59 F [Normal 0-85 C / 32-185 F] OK UPS 1 APC Smart-UPS 750, Battery charge: 100%, 82 minutes

The post immediately after that shows:

JohnnyViking wrote:
Mine is: Disk 1 WDC WD20EARS-00MVWB0 1863 GB , 14 C / 57 F , Skrivcacheminne PÅ OK Disk 2 WDC WD20EARS-00MVWB0 1863 GB , 15 C / 59 F , Skrivcacheminne PÅ OK Fläkt SYS 1730 Varvtal OK Temp CPU 24 C / 75 F [Normal 0-80 C / 32-176 F] OK Temp SYS 14 C / 57 F [Normal 0-65 C / 32-149 F] OK UPS 1 Finns inte Ej tillämpligt

Notice that the order of the CPU and SYS readings on the second post are reversed compared to the first, and appear to be in the same order as back when they were "Temp 1" and "Temp 2" (looking at older posts).

So, can anyone else running the latest beta take a look at theirs? Or anyone else with a Pro 6? This feels like a firmware error, but if it's a hardware error, I'd like to know before I get too far along setting up my system.

Edit:
One other example with an Ultra 6 at:
https://www.readynas.com/forum/viewtopic.php?f=24&t=59397

Errantpixel wrote:

Disk 1 Seagate ST32000542AS 1863 GB , 38 C / 100 F , Write-cache ON OK Disk 2 Seagate ST32000542AS 1863 GB , 38 C / 100 F , Write-cache ON OK Disk 3 Seagate ST32000542AS 1863 GB , 36 C / 96 F , Write-cache ON OK Disk 4 Seagate ST32000542AS 1863 GB , 35 C / 95 F , Write-cache ON OK Fan SYS2 897 RPM OK Temp CPU 24 C / 75 F [Normal 0-65 C / 32-149 F] OK Temp SYS 34 C / 93 F [Normal 0-60 C / 32-140 F] OK UPS 1 APC Back-UPS ES 700, Battery charge: 100%, 55 minutes OK

o, can anyone else running the latest beta take a look at theirs? Or anyone else with a Pro 6? This feels like a firmware error, but if it's a hardware error, I'd like to know before I get too far along setting up my system.

Tech support has confirmed that it is a firmware error. This is based on my own case which I had opened with them two months ago.

Have you tried upgrading with T23 beta? This has corrected the problem for me.