Description of problem: dracut seems to assume that BIOS time is UTC, causing fsck on every boot due to the last check time being in the future in the second fsck run after dracut: https://bugzilla.redhat.com/show_bug.cgi?id=963283#c20
Yes, RTC time can reasonably only be in UTC, since it carries no timezone information. Anything else is broken. That notwithstanding, fsck should not be run twice — so there's a bug here, but not in the time handling.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > Yes, RTC time can reasonably only be in UTC, since it carries no timezone > information. Anything else is broken. Please reconsider this, since this is needed for dual-boot environments. Fedora itselfs supports it with a setting in /etc/adjtime (the third line is LOCAL instead of UTC). Maybe it is enought to just copy /etc/adjtime into the dracut initramfs to address this, if only tools that support it already are used in the dracut initramfs.
Better change your other OS to use UTC! https://www.google.com/search?q=configure+windows+to+use+utc
As I commented on https://bugzilla.redhat.com/show_bug.cgi?id=1198761, it seems simply including /etc/adjtime when creating the initrd fixes the problem. There's no reason the supported option of running the system clock in local time (which is set that way if the installer detects Windows, by the way) will cause the fsck problem, in my humble opinion.
FWIW: There is, as far as I can tell, a bug in e2fsck where even though docs sound like it will ignore a time off by up to 24h, it actually doesn't ignore it at all, and forces a full fsck anyway. I'm trying to get clarification on the list about expected behavior, and will fix that (separate) bug as well. (if fsck is really being run twice, though, I can't explain that one) -Eric
Sorry, I hadn't read the original comments in https://bugzilla.redhat.com/show_bug.cgi?id=963283 So it seems there is the workaround of using broken_system_clock = 1, which is lying because the system clock is actually fine, in local time. You can also include /etc/adjtime in the initrd and the problem stops appearing too, at least for me as I reported in the Fedora forums. Even this could be considered a workaround because the actual problem could be fsck being run twice when it shouldn't. And there's also the way e2fsck fixes the superblock last write time, maybe doing a full check which takes too much time when it shouldn't be doing that. :(
*** Bug 1198761 has been marked as a duplicate of this bug. ***
I have this issue too. Related post in Ask Fedora forum is : https://ask.fedoraproject.org/en/question/66041/fedora-21-is-very-slow-on-startup
There was a time, when dracut included adjtime. But this was reverted http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=d27cd4dfdd51c7f5178c5f4cb8f5bf4668228995 Having adjtime in the initramfs causes bugs like bug 981617