Clock set to the wrong time at boot

synthead · 2011-10-21 21:57:50

This is on a new Toshiba NB505, if it matters. When I boot it, it's set about 12 hours back. I can do a soft reboot and the time will go back again. Linux is the only OS on this guy, so no UTC/localtime problems. The localtime file is set correctly (via rc.conf), and I can ntpdate time.nist.gov back to the correct time. I have the feeling this has to do with the "hwclock" daemon, but running the command manually and even restarting the daemon doesn't seem to cause trouble. What's up?

byte · 2011-10-22 01:19:21

First thing I'd check is the BIOS clock.
Set that to your local time (in case your rc.conf also has localtime) and the rest should get handled automatically.

Last edited by byte (2011-10-22 01:20:32)

Yochai · 2011-10-22 16:38:19

Let me describe my problem and let me know if you having the same happens to you.

My clock is set to

LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Asia/Jerusalem"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

...

DAEMONS=(!hwclock ... network ntpd ...)

Yet every time I shutdown the computer (and I do every night when I go to sleep) the BIOS clock is moving back a few months (but not to factory time).
If I will reset the BIOS time and won't load Arch but just restart the computer the error will not repeat, it happens only on Arch shutdown process.
I've been using hwclock till now and moved to ntpd in hopes it will solve it, but it didn't.
I actually have to fix the BIOS clock every time I restart the computer because the system won't load (as it appears to been shutdown in the future).

csergec · 2011-10-22 17:36:24

Hi Yochai

I have the same config than you in /etc/rc.conf

If Arch is your lonely OS , you have to load the hwclock daemon.
If not ( meaning dual boot with Windows for instance )it is better to use "Localtime" in hardwareclock and still load hwclock

Serge

Yochai · 2011-10-22 18:55:06

Hey csergec,

It isn't the issues.
My original conf was just hwclock, tried to add ntpd, didn't work, tried disabling hwclock didn't work.

I'm only booting Arch so it's something in my configuration, I'm just clueless to where.

alkuzad · 2011-10-22 20:46:03

Did u set

HARDWARECLOCK="localtime"

?

Yochai · 2011-10-23 16:24:20

I've now tried that too with no effect.

whereareyouall · 2011-10-25 12:05:29

synthead wrote:

Linux is the only OS on this guy

I know, it is unlikely. But have you tried another OS like Windows? At least for five minutes? It really is rare, but there are computers where the internal clock just malfunctions ... (or the battery is a little loose ... or something like that)

synthead · 2011-10-25 13:09:15

With the AC plugged in and the battery at 100%, I can reboot the computer without shutting it down and observe that the clock is wrong after it boots.

Stebalien · 2011-10-25 14:30:43

Do the outputs of the following commands agree?:

sudo hwclock --show
date

synthead · 2011-10-26 02:30:29

After a reboot:

$ sudo hwclock --show
Tue 25 Oct 2011 02:29:24 PM EDT  -0.594851 seconds
$ date
Tue Oct 25 14:29:27 EDT 2011
$ sudo ntpdate time.nist.gov
25 Oct 22:29:21 ntpdate[1320]: step time server 192.43.244.18 offset 28674.054351 sec
$ sudo hwclock --show
Tue 25 Oct 2011 02:31:33 PM EDT  -0.063816 seconds
$ date
Tue Oct 25 22:29:33 EDT 2011

Stebalien · 2011-10-26 03:31:41

Have you tried manually saving your system clock (hwclock -w)?

virusso80 · 2011-11-02 07:41:09

Hi all, I have same issues on ALL pc (laptop/desktop) with arch. I'm not able to have clock correctly set on boot. The only way (i know) to set is through ntpd, but everytime it is the same issue. I can not think it's a battery issue. I have a dual boot, but i only use arch, rarely windows. rc.conf time is set to local time. I even realized that boot time is wrong. if i set it correctly...after few time, it goes wrong again.

this is what i have after ntpd sets time. Every boot it's the same problem.

[root@jily ~]# date
Wed Nov  2 07:39:27 CET 2011
[root@jily ~]# hwclock 
Wed 02 Nov 2011 09:28:16 AM CET  -0.739496 seconds

after using hwclock -w time is temporary set but next boot presents the issue again.

It seems to be not only an issue of mine. Could please help me how to fix this?

Thanks in advance

ozar · 2011-11-06 20:58:16

virusso80 wrote:

Hi all, I have same issues on ALL pc (laptop/desktop) with arch. I'm not able to have clock correctly set on boot.

Hello

If you haven't done so already, be sure to check the wiki page regarding time settings and read through it several times to make sure you are following the concept and directions correctly:

https://wiki.archlinux.org/index.php/Time

My machine wouldn't reboot with the correct time either whenever I'd use "UTC" in rc.conf, but once I realized that the hardware clock (BIOS/CMOS) needed to be set with UTC rather than local time and the UTC change was made to rc.conf, it worked properly on all reboots. If you run Arch and Windows on the same machine, I'd recommend setting everything to UTC.

karol · 2011-11-06 21:02:24

Windows can use UTC: https://bbs.archlinux.org/viewtopic.php … 0#p1013080

pouar · 2011-11-09 02:45:37

i had a similar issue recently, i got it working by uninstalling then reinstalling ntp, disabled hwclock (or ntpd) daemons from rc.conf stopped the daemons, reboot, then added the hwclock/ntpd daemon back to rc.conf but configured the daemon to be started last. it worked for me so it might work in your case.

Last edited by pouar (2011-11-09 02:46:29)

tomegun · 2011-11-09 10:06:30

My generic suggestions to anyone who suffers from RTC problems:
Set HARDWARECLOCK to UTC in rc.conf
Delete /var/lib/hwclock/adjtime (it will be regenerated)
Do not use the hwclock daemon in rc.conf
Set the time and timezone correctly in BIOS.

Mr. Alex · 2011-12-12 18:37:42

Hello. Had the same problem and I sort of figured out how to fix it, at least this method worked for me:

1. Delete hwclock from rc.conf autorun (if not done).
2. Add ntpd there and copy it's config from https://wiki.archlinux.org/index.php/NTP but do not include "driftfile" option!
3. Adjust your BIOS clock if incorrect.

Fixed my problem.

virusso80 · 2011-12-12 20:10:25

Mr. Alex wrote:

Hello. Had the same problem and I sort of figured out how to fix it, at least this method worked for me:
1. Delete hwclock from rc.conf autorun (if not done).
2. Add ntpd there and copy it's config from https://wiki.archlinux.org/index.php/NTP but do not include "driftfile" option!
3. Adjust your BIOS clock if incorrect.
Fixed my problem.

does it work even without internet connection?

Mr. Alex · 2011-12-13 10:40:13

Virusso80, yes. Even after several reboots without Internet connection and then two reboots with Internet connection there was no such problem on my Arch.

zim0369 · 2022-03-13 19:44:55

I was facing a similar problem & I always had to `sudo ntpd -gq` on every reboot.

I was able to solve it by:

1. Going into the BIOS and setting the correct time & date.
2. Ran: `sudo ntpdq -gq`
3. sudo hwclock --systohc
4. Reboot. Worked!

HalosGhost · 2022-03-13 19:51:45

zim0369 wrote:

a similar problem

These are probably the operative words in your post. The last post in this thread was from over 10 years ago; in all likelihood, this problem is at least a fair bit different. Please do reread the Code of Conduct you agreed to when you registered today (link in my signature for ease). Please pay particular attention to the guidelines linked from that document regarding the BBS specifically.

Closing.

All the best,

-HG

Arch Linux

#1 2011-10-21 21:57:50

Clock set to the wrong time at boot

#2 2011-10-22 01:19:21

Re: Clock set to the wrong time at boot

#3 2011-10-22 16:38:19

Re: Clock set to the wrong time at boot

#4 2011-10-22 17:36:24

Re: Clock set to the wrong time at boot

#5 2011-10-22 18:55:06

Re: Clock set to the wrong time at boot

#6 2011-10-22 20:46:03

Re: Clock set to the wrong time at boot

#7 2011-10-23 16:24:20

Re: Clock set to the wrong time at boot

#8 2011-10-25 12:05:29

Re: Clock set to the wrong time at boot

#9 2011-10-25 13:09:15

Re: Clock set to the wrong time at boot

#10 2011-10-25 14:30:43

Re: Clock set to the wrong time at boot

#11 2011-10-26 02:30:29

Re: Clock set to the wrong time at boot

#12 2011-10-26 03:31:41

Re: Clock set to the wrong time at boot

#13 2011-11-02 07:41:09

Re: Clock set to the wrong time at boot

#14 2011-11-06 20:58:16

Re: Clock set to the wrong time at boot

#15 2011-11-06 21:02:24

Re: Clock set to the wrong time at boot

#16 2011-11-09 02:45:37

Re: Clock set to the wrong time at boot

#17 2011-11-09 10:06:30

Re: Clock set to the wrong time at boot

#18 2011-12-12 18:37:42

Re: Clock set to the wrong time at boot

#19 2011-12-12 20:10:25

Re: Clock set to the wrong time at boot

#20 2011-12-13 10:40:13

Re: Clock set to the wrong time at boot

#21 2022-03-13 19:44:55

Re: Clock set to the wrong time at boot

#22 2022-03-13 19:51:45

Re: Clock set to the wrong time at boot

Board footer