NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Turned off after power return
I would like to recall the thread: https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Auto-Power-On-after-Power-Loss/m-p/896012/highlight/true#M49771 and ask about the possibility to ...
Correction: of course Ultra4 is RNDU4000, not RNDP4000
StephenB, I really appreciate your willingness to help and the fact that you provide a detailed solution. Thanks for this!
I use the NAS in a different mode, namely from time to time. I have several of them, but I use some of them every few days or even weeks. I just have a backup there and synchronize data from time to time.
If I turn on the NAS, then at 2:00 at night it automatically turns off (I waited for a long time for OS6 to have a function that only turns off the NAS. At first in OS6 there was only one that turned on and off, and that did not suit me).
I often go away and then turn off the power supply to the circuits at home. After returning, I turn on and all NAS'es turn on, regardless of what I did. There is just a supply voltage and they all turn on.
I want to move one or two NAS'es to other locations. They will be enabled only during backup. I do not want them to be exposed to voltage outages. Why? Because voltage flapping may occur. Even in this forum cases of damage to devices are described, when the voltage appears and disappears.
I expect one simple thing (and not only me): that it will simply not turn on itself (I'm always able to turn it on via WOL). I really like Netgear, but the lack of such functionality makes me think about changing the device to another brand, at least those that don't have UPS.
For reliability reasons, I suggest always using a UPS - no hardware, no OS, and no file system does take power flips easy.
No idea if these legacy NAS with the OS6 "update" would allow WoL or controlling the power-up mode. For the "current" x86/BIOS models, I think the implementation would be feasible, WoL is certainly supported. The point is that Netgear seems to struggle in many areas and design changes and real product enhancements are difficult to achieve."No idea if these legacy NAS with the OS6 "update" would allow WoL..." - it works very good shumaku.
If at least one of the NAS is not always on (at least when any other is on), then sharing the UPS will be an issue. Something has to be on to share the info for the others.. The only way around this that I know of is to use an UPS that has a direct Ethernet connection and use SNMP to monitor it. I think that's available on the old OS4.2.x, but I know it's available on 6.x.
The BIOS update package doesn't change any settings, which are normally in CMOS, not flash memory. It's just a wrapper around the flashrom utility and the AMI-provided BIOS update source file.
With a VGA header installed, the user does have access to the BIOS on a Pro6, and I don't recall seeing a setting for power condition after power loss and recovery. The rack mount systems do have it, though. If there is no setting for it, there is no way to change it.
I'm not sure how the NAS is going to retain the power-on schedule through a power interruption if it doesn't come on at least long enough to re-boot and read the schedule again. That may be the driving factor for not providing an option.
Sandshark wrote:The BIOS update package doesn't change any settings, which are normally in CMOS, not flash memory. It's just a wrapper around the flashrom utility and the AMI-provided BIOS update source file.
Could explain it, expecially the second sentence, please?
Are you sure there is no way to change the power settings by modifying the BIOS bin file?
The BIOS .bin file has the tools to update the BIOS flash chip with BIOS licensed from AMI. If there even is a setting for this, Netgear would have to contract with AMI to make a change to the default setting since nothing in the package changes the actual settings from the defaults. Settings are stored in battery-backed CMOS, not flash memory. Writing to that would require an entirely different tool, which may not even exist..
There is no need to modify the bin file, flash the chip, etc.
I solved the problem simply changing one option in BIOS.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
