After some researching, I think it must be caused by the fact that the hwclock.sh init script gets run very late in the boot process. Priror to S50hwclock.sh, the system clock (or kernel clock) is uninitialized, so fsck-1.40 complains the last mount/write time is in the future.
After some researching, I think it must be caused by the fact that the hwclock.sh init script gets run very late in the boot process. Priror to S50hwclock.sh, the system clock (or kernel clock) is uninitialized, so fsck-1.40 complains the last mount/write time is in the future.