NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NVX: temp sensor 2 out of range -116.0C/-176.8F
Hi there,
hopefully I'm right here on the general questions. I have bought a NVX Pioneer Edition. I first upgraded to latest firmware 4.2.22 and installed the NAS and the discs. The first day everything was normal. Installing it to a cabinet I powered the NAS down, put it in the cabinet and when plugging in the power cable the NAS powered on and after some booting was complaining about temperature out of spec. First complains about temp too high (e.g. 127.0C/260.6F) on the LCD panel and also with email alert and immedeately afterwards complains about temp too low as stated above (e.g. -116.0C/-176.8F) with some degrees toggling. Then the NAS sends email alerts regularly with temp too low. I also did a reboot, with the same result.
What is this? How can this be overcome? Thanks for your support!
hopefully I'm right here on the general questions. I have bought a NVX Pioneer Edition. I first upgraded to latest firmware 4.2.22 and installed the NAS and the discs. The first day everything was normal. Installing it to a cabinet I powered the NAS down, put it in the cabinet and when plugging in the power cable the NAS powered on and after some booting was complaining about temperature out of spec. First complains about temp too high (e.g. 127.0C/260.6F) on the LCD panel and also with email alert and immedeately afterwards complains about temp too low as stated above (e.g. -116.0C/-176.8F) with some degrees toggling. Then the NAS sends email alerts regularly with temp too low. I also did a reboot, with the same result.
What is this? How can this be overcome? Thanks for your support!
8 Replies
Replies have been turned off for this discussion
- Hmmhhh... Strange.
I downgraded to firmware 4.2.19. There was only one Temp sensor ("System") visible and that was o.K. There was no further 2nd sensor ("CPU"). Then I upgraded 4.2.20, 4.2.21 and finally back again to 4.2.22 and there is still no CPU temperature sensor now visible. The "System" sensor shows everything o.K.
How ould be? - Your NAS should not be reporting such erroneous temperatures. What firmware version did you upgrade from? I would recommend performing an OS Reinstall on the NVX to overwrite any possibly bad files that originated on the device.
http://www.readynas.com/kb/faq/boot/how ... _boot_menu
Follow that for your unit. Let me know the results. - The first upgrade was from the original factory firmaware on the NAS 4.1.9. I also had some issues to upgrade directly to 4.1.22. There several times was reported the file would be corrupted. After several tries it worked finally.
After initially upgrading to 4.1.22 I did a firmware reinstall with formatting of the disks. Do you think I should redo this again?
CORRECTION: I meant 4.2.9 and 4.2.22. Thanks to readysecure1985 - You must be mistaken.
ReadyNAS x86 units use 4.2.x and ReadyNAS Sparc units use 4.1.x.
Generally, you wouldn't upgrade directly to 4.2.22, you would upgrade to 4.2.15>4.2.16>latest.
I would have recommended upgrading to 4.2.22 and factory defaulting the unit when you first purchased it to clear away any configs from firmwares before 4.2.22.
As you have already done this related stuff, I recommend OS reinstall on your device on 4.2.22 to see if it fixes the temperature reading. readysecure1985 wrote: You must be mistaken.
ReadyNAS x86 units use 4.2.x and ReadyNAS Sparc units use 4.1.x.
yes, you are right, the original factory installed firmware was 4.2.9 and I updated to 4.2.22.
I did the OS reinstall. I will look if this will reoccur. Up to now there is only one temp sensor visible and everything seems o.K. What was strange to me last time, when plugging in the power cable, the NAS started up itself and started complaining on the mentionend "out of range" issue. I think this start up was allready unnormal. Or is this the normal behaviour?
Not true. You could upgrade from 4.2.1 (original release) to 4.2.22 directly. The upgrade scripts along each version carry over to migrate systems.readysecure1985 wrote: Generally, you wouldn't upgrade directly to 4.2.22, you would upgrade to 4.2.15>4.2.16>latest. - Works fine up to now with no further CPU temp messages. Thanks for support!
- an update here:
some months testing revealed a reproducabele behaviour pattern:
- rebooting from frontview worked normal without error messages afterwards
- booting with plug in, the switch on the panel or power scheme resulted in this error messages
I opened a service case and after providing the log files the unit will be exchanged due to "possible minor HW problem"...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
