NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
FAN problem after upgrade from 4.2.28 to 6.5.0 T338
Hi All. My first post but been reading from many days. Recently i bought my Netgear NAS, that is RNDP6310-200 which is (by all signs) PRO6 v2, running 6xWD 2TB disks. On 4.2.28 temps were - CPU ...
OK, I see what's going on. Thanks for the logs. Strangely, your fan speed is drifting lower, without us ever adjusting it. It appears to be correlated with disk spindown, but I really don't know why that would have an effect. Anyway, we'll have a change in RC2 that should knock this out once and for all.
Ok... another observation...
This is all about ststem fan (not CPU). CPU is working fine.
I took is to my desk and was looking and waiting...
System fan is indeed turning very very slow... I can see the blades and I'm almost able to count them while they are turning... So it turns definetly too slow...
Every few minutes, it starts to turn at full speed ( I think), making bad noice or air.
After 2-3 minutes it slows down again...
Then everything repeets.
Is it possible to set minimum speed to say 600 - 700 rpm ? Not fixed speed but minimum.. So it could turn faster, but not slower than ... rpm?
This is probably fixed now. You appeared to keep rebooting the
unit for some reason while debugging was taking place, and eventually shut off
remote access; so we could never verify if some changes made actually fixed your system.
Anyway, your fan seems to respond much slower than normal to PWM changes,
which was the root cause of the issue.
Setting the minimum speed to a lower level than what we have hardcoded as the minimum is not something we would support doing and could lead to the system overheating.
Setting the minimum speed to a lower level than what we have hardcoded as the minimum is not something we would support doing and could lead to the system overheating.
Hi,
I've had power option enabled, to turn the unit off for overnight (midnight till 8am), so probably it worked while you were loged in.
Also, I just found that remote access is unticked (I did not turn it off - just enabled it again in case you may want to check if solution was working.
The server itself was not rebooted - but log says some background services were restarted many times.
Tue Apr 19 2016 6:18:05 System: ReadyNASOS background service started. Tue Apr 19 2016 0:00:10 System: The system is shutting down. Mon Apr 18 2016 23:01:49 System: ReadyNASOS background service started. Mon Apr 18 2016 23:01:12 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 22:51:11 System: ReadyNASOS background service started. Mon Apr 18 2016 22:50:34 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 22:48:20 System: ReadyNASOS background service started. Mon Apr 18 2016 22:47:43 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 22:43:13 System: ReadyNASOS background service started. Mon Apr 18 2016 22:42:36 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 22:42:20 System: ReadyNASOS background service started. Mon Apr 18 2016 22:42:04 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 22:38:07 System: Fan System in enclosure Internal speed is below threshold. (540 rpm). Mon Apr 18 2016 22:27:47 System: Fan System in enclosure Internal speed is below threshold. (496 rpm). Mon Apr 18 2016 22:25:19 System: ReadyNASOS background service started. Mon Apr 18 2016 22:24:42 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 22:03:53 System: Fan System in enclosure Internal speed is below threshold. (537 rpm). Mon Apr 18 2016 21:50:26 System: ReadyNASOS background service started. Mon Apr 18 2016 21:48:55 System: The system is rebooting. Mon Apr 18 2016 21:46:43 System: Application htop is installed successfully. Mon Apr 18 2016 21:43:10 System: Fan System in enclosure Internal speed is below threshold. (502 rpm). Mon Apr 18 2016 21:39:57 System: ReadyNASOS background service started. Mon Apr 18 2016 21:39:20 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 21:38:37 System: Fan System in enclosure Internal speed is below threshold. (461 rpm). Mon Apr 18 2016 21:35:25 System: ReadyNASOS background service started. Mon Apr 18 2016 21:34:48 System: ReadyNASOS service or process was restarted. Mon Apr 18 2016 21:29:47 System: ReadyNASOS background service started.
Anyway - I'm leaving unit enabled and will see what will happen.
Many thanks for your effort guys! :)
edit: while I mentioned about speeds adjustments, I was thinking opposite - to set the minimum speed theshold higher than default, in order to force faster spinning. I'd never propose to toast or burn my drives :)
Well 600-700 rpm would be below the default minimum.
Let us know whether/not you still have problems with the fan speed now that some changes have been applied on your system.Well, I have no accessto the box right now, only through readycloud...it shows status but no rpm's nor temp. But I suppose it is ok as when rpm's go down, system status dot goes red with description 'system bad'.. so far it is green.
However, in the morning (till say 11 cet) i was getting alert emails
Ok... so I tested the box... and I'm a bit confused here...
It can be a few hours with no errors, and then next few hours with problems and emails (all regarding system fan)...
If it works well (no errors, rpm about 800) and I restart the box, the errors starts to be sent...
Then if I copy something heavy to / from the box so its temperature rises a bit, usually it helps and next few hours I have no problems...
I noticed that when I have this problem (low rpm and emails) the didks temperature is not displayed in Performance / Status...
I can see then disks dots (green) number, model and capacity but no temperature...
If there is a time when rpm probmel is gone, then I also can see the disks temperature then...
Maybe this would help to trace the cause?
I was thinking if replacinf the fan would help, but this one seems to be ok... at least I think so...
Can you give me a clueif there is something, config file or adjustment method so I can play with it ?
I know linux a bit :) and have ssh access to the box.
I did no try the methods advertised for 6.0 or 6.2.4 as I fount they are not working anymore with 6.5...
Some further changes have been applied on your box now that the remote access is back up again.
Please let us know how it goes.
Hi
I think I am experiencing identical issues to those reported by the original poster.
The box is a Readynas pro business edition that was updated to 6.5.0 - T338
The box and all fans were carefully cleaned before applying the update but now the system fan seems to run very slowly. When it runs below threshold the System temp climbs to 65 and then the fan kicks in and brings it down to 55-56. I believe it used to run cooler than this with OS 4
The errors taht I am getting are all Fan System in Enclosure Internal Spedd is below threshold (405 - 555rpm)
My fan connetions are identical to the OP - the system fan connects to the MB, not the IO board.
Ok I'm back... I let it run for a few days before I report something. Also did a few restarts to make check how it works.
It is better... far better... Altough it still has this issue 2 maybe 3 times a day, the frequency is much much lower... One email and one loud moment then 10-12 hour is ok then again one email... I can live with that :) So thank you so much for help.
What I'd like to know is what / where has been changed in order to make a backup of the settings.
Do not want to loose this cure while upgrading or doing factory reset.
As for hardware setup (this is regarding to previous post), my CPU fan is connected by 4 wire plug to the matherboard, while SYSTEM fan (the big one) is connected to right socket on the small IO board by 3 wire plug.
However, nowhere in the frontend can I see the temperature / speed for the power supply.
As there is (in total) 3 fans, I suppose this should be 3 indicators... - I have just two...
Anyway, thank you very much guys!!
Stan78 wrote:
... it still has this issue 2 maybe 3 times a day, the frequency is much much lower... One email and one loud moment then 10-12 hour is ok then again one email...
Can you send in your logs?
What I'd like to know is what / where has been changed in order to make a backup of the settings.
Do not want to loose this cure while upgrading or doing factory reset.
The changes are already there in 6.5.0-RC1. Your system has some additional debug logging enabled, but that is the only difference in fan control from 6.5.0-RC1.
However, nowhere in the frontend can I see the temperature / speed for the power supply.
As there is (in total) 3 fans, I suppose this should be 3 indicators... - I have just two...
The PSU fan is internal to the PSU, and is not capable of being monitored by software. So we cannot represent its state in the GUI.
Thank you for the answer.
Just sent the logs as requested.
Thank you.
OK, I see what's going on. Thanks for the logs. Strangely, your fan speed is drifting lower, without us ever adjusting it. It appears to be correlated with disk spindown, but I really don't know why that would have an effect. Anyway, we'll have a change in RC2 that should knock this out once and for all.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
