Hallo, * Ben Hutchings [Wed, Mar 11 2015, 05:01:58PM]: > Control: tag -1 moreinfo > > On Wed, 2015-03-11 at 11:40 +0100, Eduard Bloch wrote: > > Package: initramfs-tools > > Version: 0.119 > > Severity: important > > > > Just what the topic says. I have encrypted root and plymouth and the > > bios clock runs in local time. And on every boot, fsck scans the > > rootfs in forced mode which takes a while. > > > > This started happening only after dist-upgrading today, and I also > > installed plymouth for other reasons. > > From the NEWS file: > > * If the RTC (real time clock) is set to local time and the local time is > ahead of UTC, e2fsck will print a warning during boot about the time > changing backward (bug #767040). You can disable this by putting the > following lines in /etc/e2fsck.conf: > [options] > broken_system_clock=1 > > I don't know why you would see a forced fsck rather than only a warning. > But does that configuration change work for you? Correct, I don't understand this either. I entered the debug shell (break=mount), configured the encrypted root, run "e2fsck /dev/mapper/xroot" and there was no warning, it just returned. "date" displayed the correct BIOS date with "incorrect" timezone (UTC, not UTC+1). Setting the mentioned option in e2fsck.conf does help. Regards, Eduard. -- <Alfie> Von sid wirds nie ein netinst geben. <hygl> Alfie: darf ich dich damit zitieren, wenn sid stable ist?
Attachment:
signature.asc
Description: Digital signature