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.
-- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
