I looked at date and hwclock settings. Both were way off what is today:
root@edison:~# hwclock --localtime
Sat Jan 1 00:02:28 2000 0.000000 seconds
root@edison:~# date
Thu Oct 9 09:25:18 UTC 2014
Then, I sat the current date and time
root@edison:~# date --set "2014-11-29 10:46"
Sat Nov 29 10:46:00 UTC 2014
root@edison:~# date
Sat Nov 29 10:46:03 UTC 2014
...and rebooted the Edison without disconnecting the power supply (# reboot):
edison login: root
[ 15.510324] systemd-fsck[231]: /dev/mmcblk0p10: Superblock last write time (Sat Nov 29 10:46:29 2014,
[ 15.579363] systemd-fsck[231]: now = Thu Oct 9 09:22:37 2014) is in the future.
[ 15.581123] systemd-fsck[231]: /dev/mmcblk0p10: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
[ 15.582675] systemd-fsck[231]: (i.e., without -a or -p options)
root@edison:~# date
Thu Oct 9 09:22:51 UTC 2014
root@edison:~# hwclock --localtime
Sat Jan 1 00:01:01 2000 0.000000 seconds
root@edison:~#
As you can see, the date has been reset to the old value (Thu Oct 9 09:22:51 UTC 2014).
And it keeps ranting that from the system's point of view, something happened "in the future". Then, it pretends to fix it which kinda fails:
edison login: root
[ 37.422874] systemd-fsck[231]: /dev/mmcblk0p10: Superblock last mount time is in the future.
[ 37.425737] systemd-fsck[231]: (by less than a day, probably due to the hardware clock being incorrectly set) FIXED.
[ 37.428131] systemd-fsck[231]: /dev/mmcblk0p10: Superblock last write time is in the future.
[ 37.431007] systemd-fsck[231]: (by less than a day, probably due to the hardware clock being incorrectly set). FIXED.
[ 37.433668] systemd-fsck[231]: /dev/mmcblk0p10: clean, 16/152608 files, 26870/610299 blocks
root@edison:~#
Sorry for so many listing. I tried to describe the problem as precise as possible ;-)