UPS Time is incorrect

nilesf wrote:

I don't, but for those who are time sensative this maybe an issue for them. It also draws attention to what if this was a longer duration of "on-battery"? How will the ReadyNAS respond if a 14 second duration is multiplied into hours? Will the ReadyNAS multiply the offset differance? Just a ten fold would mean an entire minute. Assuming a 10 fold: PowerChute would be 14*10=140/60=2.3xxx (round to 2.3 minutes) ReadyNAS would be 6*10=60 or 1 minute. If this is the case then this could be a very big problem for those who rely on the ReadyNAS to report correctly. It also shows the lack of quality in the code. Niles

Very speculative. You are for some reason assuming PowerChute is correct in its reporting and the ReadyNAS is at fault. Do you have evidence that supports that conclusion?

You have no evidence at all to support your theory that the error is somehow proportional to the outage time. The NAS is getting this information from the UPS, so the two UPS's are the devices that signal the power up/power down event. It is quite possible that the NAS (and maybe PowerChute) are polling for status, and that the error is simply a result of the polling interval. This seems like a more plausible explanation to me, it is at least equally plausible.

If you want to gather proper evidence, you have a very easy way to proceed. Just unplug the UPS for a while, then plug it back in. Track the time, and see what both devices report. It shouldn't be difficult to measure what the error is, and how it relates to outage duration. (Best to have a backup before you deliberately create power issues).

In any case, the signal that really matters is the battery life remaining, since that is what drives the clean shutdown (which preserves the data in the RAID array). So perhaps as part of your testing you should let the power completely drain from the UPS and confirm that the NAS in fact does the proper shutdown. It would be prudent to ensure that no disk writes are being done during that test. So maybe disconnect the NAS from the network, and make sure no backup jobs are running.