Created attachment 998022 [details]
Description of problem:
When system is started fsck is executed on the root partition with the messages shown bellow.
/dev/sdaX: Superblock last write time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set). FIXED.
/dev/sdaX: 329699/4481024 files (1.6% non-contiguous), 4874832/17919744 blocks
Every time the OS is booted, if system uses Local time instead of UTC.
Steps to Reproduce:
1.In system-config-date make sure "System clock uses UTC" is unchecked.
All it does is running fsck on every system boot, therefore, leading to a delay while fsck is scanning (approximately 1 min in my case). If I start system-config-date and mark "System clock uses UTC", the problem is gone.
I've upgraded from 20-21 today and then the problem appeared. I'm dualbooting Fedora and Windows, that's why I had chosen Local time. But it was like that for 3 years and the problem popped up just after the upgrade.
I've attached the boot.log just in case.
The hardware clock is the identical with the system clock (hwclock -c). It is synchronized automatically, though I've tried it manually also (hwclock -w). /etc/adjtime is correct depending on the settings in system-config-date - I mean UTC or LOCAL.
It's not so bad, Windows can be made to live with UTC too, but it used to work before so I decided to post it as a bug.
Thank you for the time spared, in advance.
P.S. I didn't know which component to choose while posting this bug, so I've chosen randomly.
reassigning to systemd
I have the same problem (Fedora 21). In fact, I asked about it in the unofficial Fedora forums:
I've been running some experiments with dracut and it seems simply including /etc/adjtime in the initrd fixes the issue.
dracut --include /etc/adjtime /etc/adjtime --force
This bug seems to be related to #1201978. It's worth noting the Fedora installer detects if Windows seems to be installed in the computer and, in that case, configures the system to use local time.
making an image with dracut, as you have shown above, does the trick! Just tested it on a VM with newly installed F21.
After installation and changing hwclock to localtime, fsck began to scan the system drive every time on bootup.
Running "dracut --include /etc/adjtime /etc/adjtime --force" solved the problem.
Many thanks for your comment Ricardo!
Building an initramfs image for every new kernel is not a permanent solution, though!
dracut should probably include adjtime in the initrd by default in Fedora, but in the mean time you can automate that yourself to avoid rebuilding the initrd all the time. Please correct me if there are better ways. I'm just getting myself acquainted with both Fedora and dracut.
Create /etc/dracut.conf.d/adjtime.conf with the following line:
That should do it.
I don't much about dracut, apart from what it does. I've never used it before. I didn't have time to dig in so far. What you've suggested should work, judging from the dracut.conf man page. I'll try it on the VM.
On my laptop I've switched to UTC.
*** This bug has been marked as a duplicate of bug 1201978 ***
I have this issue. I have asked a question regarding this in Ask Fedora. The post can be found here: https://ask.fedoraproject.org/en/question/66041/fedora-21-is-very-slow-on-startup