HD200 uptime -- is my HD200 used?

[Grant.Edwards]

I received and set up my HD200 two days ago. When I look at system
info (in stand alone mode), it shows an instance uptime of 865 days 4
hours 50 minutes. Total uptime is 865 days and 5 hours.

Either the uptime calculations are completely broken or my HD200 was
used by somebody else for 2+ years before it was shipped. I'm
guessing the former.

Is there somewhere I need to set the date/time in stand-alone mode?

Or am I wrong in assuming that "uptime" means how long the unit has
been up?

[paulbeers]

I don't think the HD200 has even been available for that kind of time. Most likely that function doesn't work.

[stanger89]

I don't think the HD200 even knows what time/date it is, there's no place to set the date or time, and neither is displayed anywhere that I can recall.

[Grant.Edwards]

Originally Posted by stanger89

I don't think the HD200 even knows what time/date it is, there's no
place to set the date or time, and neither is displayed anywhere that
I can recall.

I looked for someplace to either set the time or configure an NTP
server but could find neither.

But, the uptime of a Linux system doesn't actually depend on knowing
the current date/time. It's simply delta-time since the kernel
booted. The embedded Linux system I'm currently working with always
thinks it's Jan 1, 1970 when it's booted. But the uptime is still
correct.

Cumulative uptime is done by incrementing a non-volatile memory
location periodically, so that doesn't depend on knowing the current
date/time either.

[SDeGonge]

Same issue here. It showed 865 but eventually it reset itself (within a week).

[jpwegas]

Originally Posted by Grant.Edwards

But, the uptime of a Linux system doesn't actually depend on knowing
the current date/time. It's simply delta-time since the kernel
booted. The embedded Linux system I'm currently working with always
thinks it's Jan 1, 1970 when it's booted. But the uptime is still
correct.

Cumulative uptime is done by incrementing a non-volatile memory
location periodically, so that doesn't depend on knowing the current
date/time either.

As you mention, the uptime command reports time since last boot, so if the value is that high it's obviously bogus.

Interestingly, my HD200 thinks it's 1/1/2008 00:00 when it boots. Not sure why that happens instead of the "normal" epoch time of 1/1/1970.

And 5/15/2010 (the date of your post) is about 865 days from 1/1/2008. That probably explains what you're seeing. Although I'm not sure why uptime is reporting that - if I set the date on my HD200 to today, the uptime does not show a high value like 865 days, it reports the actual time since it booted (10 minutes at the moment).

--John

[ToxMox]

Originally Posted by jpwegas

As you mention, the uptime command reports time since last boot, so if the value is that high it's obviously bogus.

Interestingly, my HD200 thinks it's 1/1/2008 00:00 when it boots. Not sure why that happens instead of the "normal" epoch time of 1/1/1970.

And 5/15/2010 (the date of your post) is about 865 days from 1/1/2008. That probably explains what you're seeing. Although I'm not sure why uptime is reporting that - if I set the date on my HD200 to today, the uptime does not show a high value like 865 days, it reports the actual time since it booted (10 minutes at the moment).

--John

Based on this I would say that every time the HD200 boots (or loses power maybe) the hardware date resets to 1/1/2008 then at some point while running acquires the real date.

865 is exactly the number of days between 1/1/2008 and 5/15/2008 and since the change happened while running I guess it thinks it's been running for that long. Just my guess.