SMART Data gone AWOL

Heh, just noticed that the time/date was "Sun Aug 23 21:04:04 CDT 1992" switched to the pool.ntp.org servers, got a fixed timestamp and everything is back to normal.

I have the same issue on my ReadyNas Pro Business edition. I have rebooted, shutdown, recently factory default installed it as well. I was running 4.2.19 until tonight and applied the beta of .20, still exhibiting the same issue.
I tried what fixed it for you, didn't for me.

Same problem for me, thinks it's Aug 1992. Pro Business Edition edition running 4.2.19 using default time-a.netgear.com. Switching to a 0.us.pool.ntp.org seemed to fix it.

$ ntpdate -q time-a.netgear.com
server 209.249.181.22, stratum 1, offset -619315200.055875, delay 0.04462
8 Apr 22:29:16 ntpdate[2783]: step time server 209.249.181.22 offset -619315200.055875 sec
$ ntpdate -q 0.us.pool.ntp.org
server 69.164.217.193, stratum 3, offset -0.060478, delay 0.12123
server 64.73.32.135, stratum 2, offset -0.069485, delay 0.11438
server 209.104.4.231, stratum 2, offset -0.070885, delay 0.09004
8 Apr 22:29:21 ntpdate[2785]: adjust time server 209.104.4.231 offset -0.070885 sec
$

Notified NTGR IT to fix it.

Issue appears to only affect some of the NetGear time servers (not sure how many) e.g. "time-a" and "time-c" which were used on a Pro 6 I just remotely looked at the Frontview for.

My Ultra 6 connects to "time-e" and "time-h" and these servers are still working fine (EDIT: these servers are 3 seconds off apparently, so still no good).

So for now I'd suggest changing the NTP servers used under System > Clock

to time-e.netgear.com and time-h.netgear.com

Don't forget to click Apply.

Alternatively you can use 3rd party time servers or disable the auto update of the clock and set it manually (both of which I think were suggested above). Best to continue to get the time on the unit auto updated as some things may not function properly if the time isn't correct.

You may need to clear your web browser cache (e.g. Temporary Internet Files in Internet Explorer or Safari > Empty Cache in Safari), close Frontview then reopen it for Frontview to return to normal.

Edit: the NetGear servers I thought were O.K. are actually 3 seconds off.

I noticed my clocks were 20 years off as well. What need I do to have it check occasionally?

The problem only afftected FTP files. Files moved by cut/paste had the correct time on the server.

bdissen wrote:
I noticed my clocks were 20 years off as well. What need I do to have it check occasionally?

The problem wasn't the NAS, it was the Netgear time servers.

Choices are:
(a) do nothing, under the theory that it was a rare event and unlikely to happen again
(b) switch to another time server. For instance pool.ntp.org (http://www.pool.ntp.org). Just change the time servers to 0.pool.ntp.org, 1.pool.ntp.org

Both are reasonable responses.