Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

[Michael Biebl]

Am 18.05.2016 um 23:35 schrieb Michael Biebl:
> fsck.ext[234] should no longer run an fsck because of that.
> Which version of e2fsprogs have you installed?
> 
> What are the contents of /etc/adjtime?


See also /usr/share/doc/initramfs-tools/NEWS.Debian.gz

initramfs-tools (0.119) unstable; urgency=medium

  * The initramfs will now run fsck on the root filesystem before
    mounting it.  If the chosen init program is systemd and there is a
    separate /usr filesystem, it will also fsck and mount /usr.
  * If /usr is a separate filesystem on a RAID device and the INITRDSTART
    setting in /etc/default/mdadm is not 'all', you will need to change it
    to include that device.
  * If /usr is a separate filesystem on an LVM logical volume, and the
    line for /usr in /etc/fstab specifies the device by UUID or LABEL,
    you must change this line to specify the device using the format
    /dev/mapper/VG-LV or /dev/VG/LV.
  * It is no longer possible to bind-mount the /usr filesystem.
  * 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
    [As of e2fsprogs version 1.42.13 this message is informational, and
     no configuration change is required.]

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160518/1119525a/attachment-0002.sig>