A fix until the init scripts work correctly:
>From http://lwn.net/Articles/264498/
---quote---
From: Theodore Tso
Date: Tue, 8 Jan 2008 13:15:25 -0500
...
Newer e2fsprogs display a better message, and you can set an
/etc/e2fsck.conf setting:
[options]
buggy_init_scripts = 1
That will fix the this issue. The problem you are facing is that you
have your hardware clock set to ticking localtime, instead of GMT.
...
The problem on the Linux side is that some distributions, and Ubuntu
is the worse offender, but probably not the only one, do not correctly
set the system clock before they run fsck. And if you live east of
GMT, such that your localtime offset is positive instead of negative,
then time can appear to go backwards and e2fsck can't trust the last
superblock check time. Old versions of e2fsprogs display a funny
large time interval due to an integer overflow bug; that's since been
fixed. (This bug doesn't support people in the US, because of our
time zone offset, but it tends to affect people in Europe who are
dual-booting with Windows and hance have their hardware clock tick
localtime.)
...
---end quote---
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
