OK this is kinda stupid.

 

I keep finding the web interface of my unRAID, saying that the date is some OTHER date and the time some OTHER time.

(in fact I haven't really noticed but I *think* it reports the same wrong date and time)

 

I keep saving the correct date/time, shows up fine, only to discover after a few hours that it is back on the same time.

 

I would agree that this comes from a problematic mobo battery, if:

 

- the mobo was not always on power

- there was no such problem when this was a windows machine

 

So, is it possible to (even using some user customization and running some cron task) resync the clock from an NTP server?

 

 

I suppose you could try http://packages.slackware.it/package.php?q=current/netdate-bsd4-i486-1

 

 

root@unraid:~# netdate time-a.timefreq.bldrdoc.gov time-b.timefreq.bldrdoc.gov
time-a.timefreq.bldrdoc.gov -0.402 Tue Apr  8 09:36:49.000
time-b.timefreq.bldrdoc.gov +0.414 Tue Apr  8 09:36:50.000
time-a.timefreq.bldrdoc.gov +0.324 Tue Apr  8 09:36:50.000

 

 

There's also NTP http://packages.slackware.it/package.php?q=current/ntp-4.2.4p0-i486-1

 

You can extract ntpdate for a simple mechanism via cron or install the whole package.

 

root@unraid:~# cd /
root@unraid:/# tar -xvzf /boot/packages/ntp-4.2.4p0-i486-1.tgz usr/sbin/ntpdate
usr/sbin/ntpdate

root@unraid:~# /usr/sbin/ntpdate time-a.timefreq.bldrdoc.gov 
8 Apr 10:34:00 ntpdate[26297]: step time server 132.163.4.103 offset -3539.928802 sec

 

 

One thing to consider when you install packages.

It installs a bunch of man/doc files that should be removed to save room on your root ram disk

 

I will need a step by step procedure.

 

We can talk in PM, you post it here to help others, or even better post it on wiki.

 

 

Download the packages, I'll see about writing a start up script that will extract/install what is needed.

Then pop something into the cron tables.

 

ok tnx

 

which of the two?

 

 

 

..damn... resets to 5/6/2008 (probably 00:00 too, but I can't verify as I usually see it a few minutes or hours after that)

 

how can this be?

 

is it hardware? I doubt it