Clock problem vs. filesystem problem

[m6aUdS]

Hello!

I got kind of a stupid problem. My clock is f*cked up (it advances 4 hours each time I reboot). I did not care so I left it that way for a couple of days. Got tired of it, set it back to normal, and on the next reboot, the computer whined that last mount time was in the future.

It told me to run fsck with a command prompt, which worked. But on the next reboot, the boot jammed on the fedora logo. I do Shift+F1 to see where it hanged, and it was when trying to mount my /home/username with the same error. But this time I was not given any command prompt to run fsck.

The only way I found to get in my filesystem was to advance my BIOS clock a couple of days.

Any ideas How I can get things back to normal?

[Seve]

Boot up and leave your BIOS date where it is.

Once the OS is up, disable UTC and enable NTP for your OS clock.

No idea which DE you are using. Gnome/KDE/???

I think the following should work to change from UTC to NTP

From a terminal

system-config-date

exit and then from a terminal logged in as root

# chkconfig ntpd on
# ntpdate pool.ntp.org
# service ntpd start

Reboot, set your BIOS clock to the current date and time and see what happens.

[m6aUdS]

Thank you, I will try that and post the result here!

[lightman47]

This also happens on dual-boot machines with Windows - and UTC is selected in Fedora during install. Windows keeps setting the time back (or forward, or whatever). If you dual-boot: no UTC.