You are not logged in.
- Topics: Active | Unanswered
#1 2020-03-11 21:20:00
- windy
- Member
- Registered: 2013-11-10
- Posts: 58
[Solved] systemd-fsck delays boot despite passno=0
Hi,
after one of the latest updates my system needs additional 90 seconds to boot because of this:
systemd[1]: dev-mapper-home\x2dwindy.device: Job dev-mapper-home\x2dwindy.device/start timed out.
systemd[1]: Timed out waiting for device /dev/mapper/home-windy.
systemd[1]: Dependency failed for /home.
systemd[1]: Dependency failed for Home Manager.
systemd[1]: systemd-homed.service: Job systemd-homed.service/start failed with result 'dependency'.
systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'.
systemd[1]: dev-mapper-home\x2dwindy.device: Job dev-mapper-home\x2dwindy.device/start failed with result 'timeout'.After that, the system boots normally and I can login as usual. My LUKS partition mentioned in the logs is mounted correctly to /dev/mapper/home-windy.
I tried to set passno to 0 in /etc/fstab but the service "systemd-fsck@dev-mapper-home\x2dwindy.service" is still there after a reboot.
# grep mapper /etc/fstab | awk '{ print $4, $5, $6 }'
rw,noatime,noauto 0 0
# systemctl status --full systemd-fsck@dev-mapper-home\x2dwindy.service
systemd-fsck@dev-mapper-homex2dwindy.service - File System Check on /dev/mapper/homex2dwindy
Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-fsck@.service(8)How do I get rid of this unnecessary fsck?
Last edited by windy (2020-03-17 10:22:32)
Offline
#2 2020-03-13 10:54:56
- xerxes_
- Member
- Registered: 2018-04-29
- Posts: 952
Re: [Solved] systemd-fsck delays boot despite passno=0
What file systems do you have (output of command 'findmnt') ?
You can do:
systemctl list-dependencies systemd-fsck@dev-mapper-home\x2dwindy.service
systemctl disable/mask systemd-fsck@dev-mapper-home\x2dwindy.serviceOffline
#3 2020-03-13 20:55:22
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,642
Re: [Solved] systemd-fsck delays boot despite passno=0
Offline
#4 2020-03-14 22:19:12
- windy
- Member
- Registered: 2013-11-10
- Posts: 58
Re: [Solved] systemd-fsck delays boot despite passno=0
What file systems do you have (output of command 'findmnt') ?
A lot. 
Here is the relevant part mentioning /home:
└─/home /dev/mapper/home-windy ext4 rw,noatime
└─/home/windy/Documents/dav https://dav....You can do:
systemctl list-dependencies systemd-fsck@dev-mapper-home\x2dwindy.service systemctl disable/mask systemd-fsck@dev-mapper-home\x2dwindy.service
It seems that my initial analysis was not correct and systemd-fsck is not involved at all. So I still have no clue what causes this behavior.
That is my bugreport.
Offline
#5 2020-03-15 10:49:31
- xerxes_
- Member
- Registered: 2018-04-29
- Posts: 952
Re: [Solved] systemd-fsck delays boot despite passno=0
Print output of commands:
systemd-analyze
systemd-analyze critical-chain
systemd-analyze blameand full 'journalctl -b' output.
Offline
#6 2020-03-15 14:14:18
- windy
- Member
- Registered: 2013-11-10
- Posts: 58
Re: [Solved] systemd-fsck delays boot despite passno=0
Print output of commands:
systemd-analyze systemd-analyze critical-chain systemd-analyze blame
# systemd-analyze
Startup finished in 25.605s (firmware) + 3.904s (loader) + 3.551s (kernel) + 1min 30.928s (userspace) = 2min 3.990s
graphical.target reached after 1min 30.922s in userspace
# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 30.922s
└─multi-user.target @1min 30.922s
└─mariadb.service @1min 30.354s +567ms
└─network.target @1min 30.353s
└─NetworkManager.service @1min 30.297s +55ms
└─dbus.service @1min 30.295s
└─basic.target @1min 30.292s
└─sockets.target @1min 30.292s
└─org.cups.cupsd.socket @1min 30.292s
└─sysinit.target @1min 30.290s
└─systemd-userdbd.service @1min 30.628s +176ms
└─systemd-userdbd.socket @206ms
└─system.slice @190ms
└─-.slice @190ms
# systemd-analyze blame
567ms mariadb.service
553ms lvm2-monitor.service
470ms systemd-random-seed.service
347ms dev-sdd2.device
320ms swapfile.swap
264ms upower.service
227ms udisks2.service
215ms systemd-udevd.service
204ms systemd-journald.service
189ms systemd-journal-flush.service
188ms systemd-logind.service
176ms systemd-userdbd.service
175ms org.cups.cupsd.service
125ms systemd-fsck@dev-disk-by\x2duuid-xxxxxxxx\x2dxxxx\x2dxxxx\x2dxxxx\x2dxxxxxxxxxxxx.service
92ms user@1000.service
83ms lm_sensors.service
74ms user@120.service
73ms accounts-daemon.service
69ms systemd-tmpfiles-setup.service
64ms media-Daten.mount
61ms polkit.service
55ms NetworkManager.service
51ms systemd-udev-trigger.service
41ms avahi-daemon.service
40ms bluetooth.service
35ms efi.mount
31ms modprobe@drm.service
28ms systemd-fsck@dev-disk-by\x2duuid-XXXX\x2dXXXX.service
25ms colord.service
23ms systemd-modules-load.service
23ms alsa-restore.service
21ms gdm.service
18ms ntpd.service
16ms systemd-binfmt.service
15ms home.mount
14ms systemd-tmpfiles-setup-dev.service
14ms watchdog.service
13ms wpa_supplicant.service
13ms systemd-repart.service
9ms hdparm.service
8ms systemd-rfkill.service
8ms systemd-update-utmp.service
8ms dev-hugepages.mount
8ms dev-mqueue.mount
7ms user-runtime-dir@1000.service
7ms sys-kernel-debug.mount
7ms systemd-remount-fs.service
7ms systemd-sysctl.service
7ms sys-kernel-tracing.mount
7ms kmod-static-nodes.service
6ms user-runtime-dir@120.service
5ms systemd-user-sessions.service
5ms rtkit-daemon.service
4ms sys-fs-fuse-connections.mountand full 'journalctl -b' output.
Offline
#7 2020-03-17 10:18:59
- xerxes_
- Member
- Registered: 2018-04-29
- Posts: 952
Re: [Solved] systemd-fsck delays boot despite passno=0
So you are using new thing like 'systemd-homed'. With new things there may be some problems sometimes. I don't use it and don't plan to use it, so I can't help you further, sorry.
Last edited by xerxes_ (2020-03-17 10:19:58)
Offline
#8 2020-03-17 10:22:08
- windy
- Member
- Registered: 2013-11-10
- Posts: 58
Re: [Solved] systemd-fsck delays boot despite passno=0
Well, I did not enable systemd-homed intentionally, it was enabled automatically after the upgrade
I fixed the issue by removing the partition from /etc/fstab and modifying the PAM script.
Offline
#9 2020-03-17 10:35:10
- xerxes_
- Member
- Registered: 2018-04-29
- Posts: 952
Re: [Solved] systemd-fsck delays boot despite passno=0
What did you change in PAM script?
Offline
#10 2020-03-17 10:36:14
- windy
- Member
- Registered: 2013-11-10
- Posts: 58
Re: [Solved] systemd-fsck delays boot despite passno=0
I had to mount /home in an extra command because of the now missing line in fstab.
Offline