NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OS Reinstall worked ... UPS issue?
First off many thanks to Netgear and everyone in this forum...after reading several posts from here...I was able to fix my issue after some initial panic. But I'm wondering what happened or if I have the UPS setup wrong.
My RN104 (with 4x8TB drives and latest FW) has been trucking along for almost 10 years with no issues..but last night, our power went out for 5-10 minutes and the unit turned itself off, despite being physically connected to a UPS. I also have a synology NAS connected to same UPS and it has the USB cable connected to it. My Netgear RN104 is monitoring the UPS using the network SNMP connection from the synology.
When i powered on the Rn104, it booted up fine to 100% but then totally shut off within 30 seconds.
Same thing after several attempts and connecting power directly to wall. I pulled out the drives and when I booted up, it was fine and I could connect to it browser. Put the drives back in, praying for a miracle, but NADA...same behavior, shutdown immediatley following boot up.
I started to panic given that Netgear no longer supports Readynas...but I kept reading and researching. Eventually, from the posts here and the Netgear manual, I decided to try the OS reinstall option and that did the trick...I was able to login and deal with minor IP address issues..but no data loss!
The logs show when the power went out and came back...but then this entry seems odd:
| Jun 21, 2025 01:15:42 AM | System: The system is shutting down. | |
| Jun 21, 2025 01:15:25 AM | System: UPS UPS () is forcing shutdown. |
After I restored, I deleted the UPS SNMP entry(just in case)...but could this be a bug in OS 6 code to read the network UPS? or did I set up wrong? Anyone use a Readynas with SNMP UPS and the codes it receives? No issues on the Synology NAS with the same UPS(via cable) when power came back online.
Also wondering if I should start thinking about a replacement/newer unit. But this is my 2nd Netgear ReadyNas I have owned and I think they work perfect for my use cases.
Again, many thanks to this community.
Sorry for long post...TLDR: Is there something wrong with UPS codes being read by Readynas OS6 or time to replace?
5 Replies
I have an Eaton UPS that's directly connected to my main NAS via USB and to my other NAS via SNMP, so my set-up is similar, but not exactly the same. The big difference is that the secondary NAS doesn't need to talk to the primary, it talks directly to the UPS network card. But if that connection is lost, the secondary NAS simply complains of the lost connection and won't shut down because it doesn't get the command -- it has no impact on the ability to power it back up.
I suspect you have something else going on that only became visible only because of the cycled power. Two things that can cause an almost immediate shut-down are a voltage out of range and a fan not detected as turning. Given it seems to have corrected itself after a couple tries, my first suspect is a failing fan. But the fact that it seemed to work without drives and not with points more toward a power issue -- maybe the power brick and maybe a secondary voltage created form it. Keep an eye on the log for any indication of a low voltage or fan issue.
My RN104 (with 4x8TB drives and latest FW) has been trucking along for almost 10 years with no issues..but last night, our power went out for 5-10 minutes and the unit turned itself off, despite being physically connected to a UPS.
Did it do a graceful shutdown? (I am guessing yes).
rudedog71 wrote:
When i powered on the Rn104, it booted up fine to 100% but then totally shut off within 30 seconds.
Was the Synology turned off when you tried this? I am wondering if the ReadyNAS was continuing to get power status from the Synology.
Is there something wrong with UPS codes being read by Readynas OS6 or time to replace?
It sounds like something might be off with the UPS--- USB ---> Synology --- SNMP ---> ReadyNAS path.
You might try connecting the UPS directly to the ReadyNAS as a test. If that works, another possible path is to set up a NUT server on the Synology, and use the NUT client built into the ReadyNAS (username: monouser, password: pass)
A safe way to test UPS operation is to connect both NAS to normal power, and connect the UPS to a different electrical load. Then you can disconnect the UPS from the main power, and see if both NAS get the power status correctly, and shutdown when the UPS battery drains. Since the power to the NAS is never actually cut, there is no chance of an unclean shutdown.
Did it do a graceful shutdown? (I am guessing yes).
Not sure...how can I tell? I pulled the logs and the kernel log file shows this entry. Should I check another one of the logfiles?
Jun 21 01:16:05 REGNASv2 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Was the Synology turned off when you tried this? I am wondering if the ReadyNAS was continuing to get power status from the Synology.
Yes...I wondered the same but after the OS reinstall the UPS was still configured in the ReadyNas so what prevented the shutdown after the reinstall?
You might try connecting the UPS directly to the ReadyNAS as a test. If that works, another possible path is to set up a NUT server on the Synology, and use the NUT client built into the ReadyNAS (username: monouser, password: pass)
I will try the UPS directly connected to the Readynas...but using the NUT client built into ReadyNas (w Nut client on Synology) is how I had it(and what I meant by SNMP configuration)....is there an alternate way to do UPS--- USB ---> Synology --- SNMP ---> ReadyNAS path. ?
Appreciate the feedback. I will test UPS operation after I complete a full backup of the data on my ReadyNas.
Not sure...how can I tell? I pulled the logs and the kernel log file shows this entry. Should I check another one of the logfiles?
Jun 21 01:16:05 REGNASv2 systemd-shutdown[1]: Sending SIGTERM to remaining processes...Thats a clue that it was a graceful shutdown, and not a power cut.
dmesg.log and systemd-journal.log should tell you if it was not graceful (there would be a message along those lines at the next normal boot).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
