NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Smaky
Apr 19, 2021Guide
System: 3VSB voltage in enclosure Internal is out of spec
After upgrading to firmware 6.10.4 Hotfix 1 I am getting multiple warning showing up in the logs: System: 3VSB voltage in enclosure Internal is out of spec. (2.96 V). Not really sure if I sho...
Smaky
Apr 22, 2021Guide
ok.. looking at boot_info.log I am unable to locate any info for 3VSB:
labelvol0: VCOR minvol0: 0.00 maxvol0: 0.00 labelvol1: DDB18 minvol1: 1.70 maxvol1: 1.89 labelvol2: AVCC minvol2: 3.12 maxvol2: 3.47 labelvol3: VCC3 minvol3: 2.96 maxvol3: 3.63 labelvol4: VCC1_25 minvol4: 1.17 maxvol4: 1.32 labelvol5: VCC1_5 minvol5: 1.41 maxvol5: 1.58 labelvol6: VCC1_05 minvol6: 0.98 maxvol6: 1.10 labelvol7: 3VDUAL minvol7: 3.12 maxvol7: 3.47 labelvol8: VBAT minvol8: 2.96 maxvol8: 3.63 labelvol9: minvol9: 0.00 maxvol9: 0.00 labelfan0: SYS
So not sure what may be wrong.
Sandshark
Apr 22, 2021Sensei - Experienced User
It seems to be labeled 3VDUAL in your NAS. That's the lable used with my Pro2 running OS6.10.5 beta1, also, so I assume it's normal. Maybe somebody else with an Ultra6 running OS6 can confirm.
I did install lm-sensors on my Pro2, and the sensors command from it does report the voltage of 3VSB. So that label is used somewhere within the system.
# apt-get install lm-sensors # sensors coretemp-isa-0000 Adapter: ISA adapter CPU: +62.0°C (crit = +100.0°C) it8721-isa-0a10 Adapter: ISA adapter V5_0: +4.95 V (min = +4.70 V, max = +5.30 V) V3_3: +3.28 V (min = +3.14 V, max = +3.47 V) V+12: +11.82 V (min = +10.82 V, max = +13.18 V) 3VSB: +3.29 V (min = +3.14 V, max = +3.46 V) Vbat: +3.26 V System: 793 RPM (min = 399 RPM) System: +34.0°C (low = +1.0°C, high = +80.0°C) sensor = thermal diode
Since the NAS OS already uses libsensors directly, I didn't (and don't recommend you do) run sensors-detect, which might overwrite the existing configuration.
- SmakyApr 25, 2021Guide
installed lm-sensors and this is what I get:
# sensors coretemp-isa-0000 Adapter: ISA adapter CPU: +59.0°C (high = +84.0°C, crit = +100.0°C) Core 2: +57.0°C (high = +84.0°C, crit = +100.0°C) Core 3: +57.0°C (high = +84.0°C, crit = +100.0°C) w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: +1.18 V (min = +0.00 V, max = +1.74 V) DDB18: +1.75 V (min = +1.62 V, max = +1.98 V) AVCC: +3.06 V (min = +2.98 V, max = +3.63 V) VCC3: +3.06 V (min = +2.98 V, max = +3.63 V) VCC1_25: +1.23 V (min = +1.17 V, max = +1.32 V) VCC1_5: +1.49 V (min = +1.41 V, max = +1.58 V) VCC1_05: +1.03 V (min = +0.98 V, max = +1.10 V) 3VSB: +3.02 V (min = +2.98 V, max = +3.63 V) Vbat: +2.99 V (min = +2.70 V, max = +3.63 V) System: 2636 RPM (min = 620 RPM, div = 128) CPU: 2636 RPM (min = 150 RPM, div = 64) System: +65.0°C (high = +80.0°C, hyst = +127.0°C) sensor = thermistor
Oddly, I have got no additional warnigs.. the restore of the initial 10 TB of data just finished and there have been no additional warnings since I connected the HDD. Now I am restoring a 3 TB drive and no issues whatsoever.
- SandsharkApr 26, 2021Sensei - Experienced User
Smaky wrote:
installed lm-sensors and this is what I get:
# sensors w83627dhg-isa-0a10
Oddly, I have got no additional warnings.. the restore of the initial 10 TB of data just finished and there have been no additional warnings since I connected the HDD. Now I am restoring a 3 TB drive and no issues whatsoever.
OK, my bad. I missed that yours is an Ultra6Plus, not Ultra6, so the limits are different. But it also means it's the same as a Pro6, which I do have. Those limits are correct according to the NV6.conf file your NAS uses and agree with my Pro6. You do look to be right on the edge as far as the 3.3VSB lower limit is concerned. On my Pro6, it's 3.22V. Then again, so are the other 3.3V sources, and all of yours are low.
It could be something wrong with the monitoring system; but without a schematic, I don't know how the various monitors are interrelated. Something as simple as it being a bit warmer could be what threw you over the limit. I recommend that you continue to watch it, as your power supply may be heading to failure if it's not just a monitor issue. If you start to see issues powering on or off or with Ethernet communications, then that's another sign the standby voltage is going bad, and a replacement power supply is the usual fix.
If you are absolutely sure it's a false alarm, you can change the limits in /etc/sensors.d/system.conf. Right now, that should point to /etc/frontview/sensors/NV6.conf. I suggest you make system.conf an actual copy of NV6.conf and then edit that copy. I believe that will keep any OS update from reverting you back, plus it keeps the original intact if you find the edit was a bad idea.
The current limits are set by
set in7_min 3.3 * 0.90 set in7_max 3.3 * 1.10
and you can either change the math or just put in a specific number.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!