It could be related that ext4 was in a bad state and systemd was not able to use it then upstart executed fsck to fix it and now I can again use systemd.
# /var/log/syslog.4.gz $ zgrep -h "fsck" /var/log/*.gz Jun 8 08:43:06 mbp kernel: [1788385.038996] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Jun 8 10:48:10 mbp systemd-fsck[971]: /dev/sda5: clean, 448286/17760256 files, 35731755/71025664 blocks Jun 8 10:48:10 mbp kernel: [ 4.748519] systemd[1]: Listening on fsck to fsckd communication Socket. Jun 8 10:48:10 mbp kernel: [ 4.750175] systemd[1]: Starting fsck to fsckd communication Socket. Jun 8 11:08:54 mbp systemd-fsck[943]: /dev/sda5: clean, 447436/17760256 files, 35695088/71025664 blocks Jun 8 11:08:54 mbp kernel: [ 3.809333] systemd[1]: Listening on fsck to fsckd communication Socket. Jun 8 11:08:54 mbp kernel: [ 3.809392] systemd[1]: Starting fsck to fsckd communication Socket. Jun 8 11:11:50 mbp systemd-fsck[946]: /dev/sda5: clean, 447438/17760256 files, 35715637/71025664 blocks Jun 8 11:11:50 mbp kernel: [ 3.736279] systemd[1]: Listening on fsck to fsckd communication Socket. Jun 8 11:11:50 mbp kernel: [ 3.737878] systemd[1]: Starting fsck to fsckd communication Socket. zgrep -h systemd /var/log/syslog.4.gz > systemd-2015-06-08.log ** Attachment added: "systemd-2015-06-08.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+attachment/4413674/+files/systemd-2015-06-08.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463023 Title: systemd Timed out waiting for device swap and file system check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
