Hi, On 29-11-15 01:28, Michael Biebl wrote:
Does the problem go away if you use "systemctl mask systemd-fsckd.service systemd-fsckd.socket"
Yes, it does. Using this I got to see the following while booting, which wasn't visible before:
A start job is running... for sda1 (1min23 / no limit) (alternating between sda1 and sda6). Apparently, after 20 minutes this was done: $ systemd-analyze blame 20min 15.763s systemd-fsck@dev-sda1.service 20min 15.088s systemd-fsck@dev-sda6.service And it really finished: $ sudo tune2fs -l /dev/sda6 tune2fs 1.42.13 (17-May-2015) [.... cutting out irrelevant parts ...] Filesystem volume name: <none> Filesystem UUID: 98fcb0eb-44f7-4aae-8fef-0eabeab3ef6a Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Filesystem created: Fri Jun 20 20:29:56 2008 Last mount time: Tue Dec 1 23:13:30 2015 Last write time: Tue Dec 1 23:13:30 2015 Mount count: 1 Maximum mount count: 120 Last checked: Tue Dec 1 22:53:15 2015 Check interval: 15552000 (6 months) Next check after: Sun May 29 23:53:15 2016 and: $ sudo tune2fs -l /dev/sda1 tune2fs 1.42.13 (17-May-2015) [.... cutting out irrelevant parts ...] Filesystem volume name: <none> Last mounted on: / Filesystem UUID: 12635a70-3def-4b39-bc78-1ee0ad29a2d2 Filesystem created: Fri Jun 20 20:29:39 2008 Last mount time: Tue Jun 9 20:56:46 2015 Last write time: Tue Dec 1 23:13:30 2015 Mount count: 0 Maximum mount count: 80 Last checked: Fri Nov 6 18:40:06 2015 Check interval: 15552000 (6 months) Next check after: Wed May 4 19:40:06 2016 So, apparently the problem is in systemd-fsck? -- Grtjs, Manuel PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ ) PPS: Visit my homepage at http://manuel.msxnet.org/