Re: [cobalt-users] Time funked out after reboot

[Mailing Lists <listonly@xxxxxxxxxxxxxxxxxxxx>]

on 8/24/02 1:48 PM, Dave Bonnell stated:

> After I reboot any of my RAQ3i systems the date/time ends up at some time in
> the distant future.
>> Anyone have a clue how I can fix this?  Is the clock battery dead?
> 
> Thanks,
> 
> Dave

Dave

We had the same problem with one of our Raq3's. Reboot and we would be in
the future. A Cobalt engineer was in the machine. We changed the battery,
put a time drift script in, used  NTP servers to no get the same results. 2
thing I noticed. If I rebooted a few times, it might get the right time, or
one that seemed to be consistent was not to reboot but do a shut down. The
start back up. If you don't have physical access this will not work. The
server that was giving us grief is now been upgraded to a Raq4. We no longer
have the time issue. The Cobalt engineer stated that Sun/Cobalt felt there
was a bug in the Raq3 build. Or he felt we had a bad mother board. Sorry for
not having a better answer. We tried every trick that everyone on the list
had.

Dave