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

Hi, On 23-05-16 20:04, Manuel Bilderbeek wrote: 3. My BIOS told me at boot today that no RTC clock time was set. I guess my RTC battery is dead. Will replace it. Replaced it last night. Then booted again and set the hwclock. Then booted Debian, no fsck, as I still have the e2fsck.conf in

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

Hi, After a few days, reporting here what's going on now... 1. I haven't seen an fsck of my HDD's ever since I added that e2fsck.conf file 2. When booting, I do get a message that superblock timestamps of my SSD (/dev/sdf1) are too far in the future and I get a very quick fsck of the SDD. It

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

On Thu, 19 May 2016 23:31:29 +0200 Manuel Bilderbeek wrote: > Hi, > > On 19-05-16 23:04, Michael Biebl wrote: > >> Looks like I need to have systemd-timesync run *before* systemd-fsck!? > > > > If your hwclock drifts that much, maybe > > /etc/e2fsck.conf: > >

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

Hi, On 19-05-16 23:04, Michael Biebl wrote: Looks like I need to have systemd-timesync run *before* systemd-fsck!? If your hwclock drifts that much, maybe /etc/e2fsck.conf: [options] broken_system_clock=1 (as referenced in my earlier reply) is an option. Can you try that?

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

Am 19.05.2016 um 21:30 schrieb Manuel Bilderbeek: > > -- Logs begin at ma 2028-05-22 12:37:10 CEST, end at do 2016-05-19 > 21:22:23 CEST. -- > > Looks like I need to have systemd-timesync run *before* systemd-fsck!? If your hwclock drifts that much, maybe /etc/e2fsck.conf: [options]

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

Hi, Thanks for taking interest in this annoying problem. Today I again got an fsck at boot... On 18-05-16 23:35, Michael Biebl wrote: fsck.ext[234] should no longer run an fsck because of that. Which version of e2fsprogs have you installed? Should be latest in testing: ii e2fsprogs

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

Manuel Bilderbeek [2016-05-18 23:06 +0200]: > The whole thing reminds me of bug #755722. But that says that > systemd-timesyncd > does write to the hwclock apparently not? timesyncd does *not* write to the hw clock directly. The kernel has done that by itself now every 11 minutes for a fair

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

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;

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

Am 18.05.2016 um 23:06 schrieb Manuel Bilderbeek: > Package: systemd > Version: 229-5 > Severity: important > > Dear Maintainer, > > Before I start: I'm doing a daily dist-upgrade in testing. > > Since about a week I'm getting fsck's every other boot. I see this when > booting: > > (notice