I just connected my F4-423 to Eaton 5E700UI-EA ups and it seems to work fine. I set a 1-minute shutdown time to test. I then simulated a power outage, and after 1 minute the NAS shut down, as expected.
My question is:
Can I set the "Time to wait before shutting down the TNAS" as shown in the attached figure, or is there a risk it won't work for some unknown reason? For example, it could be a setting not managed by my UPS or by NAS.
I'm asking this because this way I can use the NAS to its maximum capacity during a power outage.
nicky6501 wrote: ↑11 Jan 2026, 20:03
I just connected my F4-423 to Eaton 5E700UI-EA ups and it seems to work fine. I set a 1-minute shutdown time to test. I then simulated a power outage, and after 1 minute the NAS shut down, as expected.
My question is:
Can I set the "Time to wait before shutting down the TNAS" as shown in the attached figure, or is there a risk it won't work for some unknown reason? For example, it could be a setting not managed by my UPS or by NAS.
I'm asking this because this way I can use the NAS to its maximum capacity during a power outage.
Thank you
Hello! Thank you for your suggestion. Just to confirm your requirement: you hope that after a power outage, the UPS can continue supplying power for a customizable period of time (e.g., X minutes) before safely shutting down the NAS. This is a very practical demand for a delayed shutdown strategy. Currently, the UPS function of the TOS system does not yet support this precise timing setting.
Could you please confirm if our understanding is correct? Your confirmation will help us accurately feedback this requirement to the product team.
My two cents, (or round up to a nickel in USA)
It would seem to me that it would depend on how the NAS is being used. Would the person or persons access the NAS would they still have power? I mean it's nice to keep the unit running as long as possible, but if no one can use it because they lost power as well...
Also, here with my setup I have the network switches on the UPS as well.
Ok this part is off topic, many years ago I was working at the datacenter for Pan American airlines, the worldwide reservation system was there. A power poll was crashed into, knocking out the line power. Now of course the entire datacenter is running on the UPS batteries, they attempt to fire up the diesel generators, well a squirrel(es) had gotten into the unit, so it shorted out. So now the entire datacenter is running purely on batteries. No idea when line power was coming back online. Everything not being used was powered off, monitors, tape drives, any non-production systems. Line power was restored before the batteries died and within a week, additional line power was brought into the datacenter from another route. Oh, and rodent traps installed by the generators as well.
F6-424 & F4-425 Plus at 7.0.0777
F4-424 Pro also at 7.0.0777
D4-320
Sorry, I don't see that your statement(s) make much sense.
Within the UPS setup you can set "until Low battery" and in TOS7 also "Sync with server". Are you implying that these functions don't actually work?.
Why would a "Product Manager" need to refer to the "Team"?
Anyway, The UPS settings as made available through TOS don't allow the determination of what "low Battery" actually means (apart from identifying use time remaining and it's relevant percentage). We also know that the implementation of NUT within TOS has had (and imo probably continues to have) flaws which prevent it operating in practical ways. (Previously posted by several users).
Instead of spending all your time building new versions of the operating system and esoteric apps with limited demand, maybe staff could (Try to) fix what already exists.
The system currently supports the “Until low battery” feature, and it can be used normally.
Please note that switching from mains power to UPS power by itself will not cause system abnormalities. If an unexpected shutdown occurs, it is more likely related to the UPS itself (such as communication issues, inaccurate battery level reporting, or compatibility problems).
How UPS power works:
After the TNAS detects that it is running on UPS power, it continuously monitors the remaining battery level.
When the battery level drops to the minimum threshold defined by the UPS manufacturer (typically 10%, but it may also be 5% or 15%), the system will automatically shut down to prevent a sudden power loss.
Some UPS brands allow this threshold to be customized through their proprietary tools. Please refer to the relevant manufacturer documentation or community guides for details, as the methods vary significantly by brand.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Thank you for your suggestion! Keeping the network switch continuously connected to the UPS is indeed a very good practice. It helps maintain communication between the NAS and local network devices during a power outage, ensuring that the shutdown process can be carried out properly and that remote management remains uninterrupted.
To contact our team, please send email to following addresses, remember to replace (at) with @:
We sincerely apologize—this was indeed an oversight on our part and may have caused some misunderstanding. At present, both of these features are working properly in TOS 7.
We will also further strengthen the training and management of our support team to ensure more accurate and efficient assistance going forward.
Regarding the issue you mentioned about NUT having shortcomings in TOS that make it difficult to use in practice, could you please provide some specific details or examples? We will review them one by one and work toward fixing and optimizing the related issues.
To contact our team, please send email to following addresses, remember to replace (at) with @:
A quick search of this forum will reveal 50 topics devoted to UPS. Sorry, but I am not the only poster who has spoken to these issues and I don't see my function as curator of UPS issues.
For me one big issue (maybe, maybe not) is that @TM writes in the help sections to the effect that any devices (nas) using the TNAS UPS server function as clients must all be connected to the same UPS. NUT was never written that way; it was intended as a 'distributed network' servicing multiple server/client relationships. In this context it is likely (I don't know) @TM has implemented NUT i a non-standard manner. What I know is that it does not really work in (what I would say is) a logical manner relative to NUT manuals/tutorials. Nothing is really configurable since the internals of Linux itself have been "modified" as well as the configuration files of NUT itself and hidden behind obfuscating links and files.
Regarding the non-standard issues you mentioned, they arise from certain practical usage scenarios and historical reasons. We will continue to conduct research and discussions to optimize solutions.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
