Control: tag -1 - moreinfo Control: reassign -1 e2fsprogs Control: forcemerge 767040 -1 Control: severity 767040 serious On Wed, 2015-03-11 at 19:58 +0100, Eduard Bloch wrote: > 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). This is expected. The initramfs already contains that configuration. > Setting the mentioned option in e2fsck.conf does help. OK, so this is a variant on #767040. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo.
Attachment:
signature.asc
Description: This is a digitally signed message part