This was not enough on my system, fsck exited with signal 13 after 60s anyway. This worked for me:
# systemctl mask systemd-fsckd.service systemd-fsckd.socket At next boot, fsck ran for some minutes and then completed successfully. Note that `systemctl disable` did not work because these units are static. I don't have plymouth installed, I don't know if that's relevant. systemd version 226-4 On Thu, 24 Sep 2015 12:23:16 -0500 Allen Webb <verta...@gmail.com> wrote: > I can confirm that this fix works on my system. > > On 09/24/2015 11:32 AM, Michael Biebl wrote: > > Am 24.09.2015 um 17:46 schrieb hannu....@pp.inet.fi: > >> This works for me: > >> > >> copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system > >> > >> edit /etc/systemd/system/systemd-fsckd.service, add TimeoutStartSec under [Service] > >> > >> [Service] > >> TimeoutStartSec=60min > > Hm, good point. We should probably disable the Timeout completely like > > in systemd-fsck-root.service and systemd-fsck@.service by setting > > > > > > TimeoutStartSec=0 > > > > The default is 90s, and an fsck for a large disk can certainly take > > longer for ext3.
