[EN] (solved) systemd-fsck hangs

[tuxic]

O.K.! Reinstalled with UUID, new fstab:

Code: [Select]

proc      /proc   proc   defaults   0   0
/swapfile   swap   swap   defaults   0   0
UUID="b2a2abf2-95a2-46b2-ae17-ab26015257c0"   /   ext4   defaults,noatime   0   1

and as result without ntfs-config installed:

Code: [Select]

root@sid-box:/home/tuxic# blkid -c /dev/null -o list
device     fs_type label    mount point    UUID
-------------------------------------------------------------------------------
/dev/sda1  ext2             (not mounted)  6067123f-9b75-4851-95b8-13ec54e40b18
/dev/sda2  ext4             (not mounted)  989a68dd-0b56-4769-ad56-58231befa019
/dev/sda4  ext4             (not mounted)  afc265fe-2b63-41a0-ad59-80d89a8dea69
/dev/sda5  ext4             /              b2a2abf2-95a2-46b2-ae17-ab26015257c0
/dev/sdb1  ntfs    Storage  (not mounted)  6876C3BE5BDF1565
/dev/sdc1  ntfs    Back-Up  (not mounted)  4CE077F63265B98C
/dev/sdc2  swap             (not mounted)  321355cd-0908-4b71-87a7-d5602526a308
and latest result:

Code: [Select]

tuxic@sid-box:~$ systemd-analyze blame
         31.734s systemd-udev-settle.service
           760ms systemd-modules-load.service
           130ms nfs-common.service
           103ms keyboard-setup.service
            95ms console-setup.service
            88ms gpm.service
            86ms ModemManager.service
            80ms loadcpufreq.service
            59ms networking.service
            58ms bootlogs.service
            51ms preload.service
            48ms systemd-fsck-root.service
            44ms lvm2-activation.service
            43ms lvm2-activation-early.service
            36ms systemd-logind.service
            32ms live-config.service
            30ms lm-sensors.service
            28ms systemd-udev-trigger.service
            24ms alsa-restore.service
            24ms rpcbind.service
            24ms console-kit-log-system-start.service
            23ms ifplugd.service
            23ms hddtemp.service
            22ms motd.service
            22ms irqbalance.service
            22ms console-kit-daemon.service
            22ms acpi-support.service
            20ms polkitd.service
            19ms cpufrequtils.service
            18ms smartmontools.service
            17ms kbd.service
            17ms sysstat.service
            16ms systemd-tmpfiles-setup-dev.service
            15ms hdparm.service
            15ms dev-mqueue.mount
            14ms sys-kernel-debug.mount
            13ms dev-hugepages.mount
            12ms ifup@eth0.service
            11ms pppd-dns.service
            10ms systemd-journal-flush.service
             9ms dns-clean.service
             8ms keymap.service
             8ms systemd-tmpfiles-setup.service
             7ms systemd-sysctl.service
             6ms rc-local.service
             6ms live-tools.service
             6ms live.service
             6ms upower.service
             5ms systemd-user-sessions.service
             5ms run-user.mount
             5ms systemd-remount-fs.service
             4ms udev-finish.service
             4ms resolvconf.service
             3ms systemd-update-utmp-runlevel.service
             3ms run-lock.mount
             2ms systemd-random-seed-load.service
             2ms systemd-udevd.service
             2ms swapfile.swap

[dibl]

OK, now edit /etc/fstab and remove the quote marks, so it looks like this:

Code: [Select]

UUID=b2a2abf2-95a2-46b2-ae17-ab26015257c0   /   ext4   defaults,noatime   0   1

[tuxic]

fstab:

Code: [Select]

proc /proc proc defaults 0 0
/swapfile swap swap defaults 0 0
UUID=b2a2abf2-95a2-46b2-ae17-ab26015257c0 / ext4 defaults,noatime 0 1

then:

Code: [Select]

tuxic@sid-box:~$ systemd-analyze blame
         31.759s systemd-udev-settle.service
           767ms systemd-modules-load.service
           119ms keyboard-setup.service
           109ms nfs-common.service
            96ms console-setup.service
            88ms ModemManager.service
            87ms loadcpufreq.service
            77ms udisks2.service
            74ms lvm2-activation-early.service
            73ms gpm.service
            62ms networking.service
            60ms bootlogs.service
            51ms preload.service
            46ms systemd-fsck-root.service
            39ms systemd-logind.service
            33ms lvm2-activation.service
            31ms live-config.service
            30ms systemd-udev-trigger.service
            27ms irqbalance.service
            23ms rpcbind.service
            23ms alsa-restore.service
            23ms console-kit-daemon.service
            22ms console-kit-log-system-start.service
            20ms ifplugd.service
            20ms hddtemp.service
            19ms acpi-support.service
            19ms motd.service
            18ms polkitd.service
            18ms hdparm.service
            17ms smartmontools.service
            17ms dev-mqueue.mount
            16ms sys-kernel-debug.mount
            15ms dev-hugepages.mount
            15ms sysstat.service
            14ms cpufrequtils.service
            14ms kbd.service
            13ms lm-sensors.service
            13ms systemd-tmpfiles-setup-dev.service
            11ms ifup@eth0.service
            10ms pppd-dns.service
             9ms systemd-sysctl.service
             9ms dns-clean.service
             8ms keymap.service
             7ms upower.service
             7ms rc-local.service
             6ms systemd-user-sessions.service
             6ms live.service
             5ms systemd-tmpfiles-setup.service
             4ms systemd-remount-fs.service
             4ms swapfile.swap
             4ms resolvconf.service
             4ms live-tools.service
             4ms systemd-random-seed-load.service
             3ms systemd-update-utmp-runlevel.service
             3ms systemd-journal-flush.service
             3ms systemd-udevd.service
             3ms udev-finish.service
             2ms run-user.mount
             1ms run-lock.mount

[der_bud]

As you still have that /swapfile-line in your fstab, please assure that a file called swapfile really exists in your root directory on /dev/sda5.

Also we know yet that something udev-related might happen, so please have a look at the journal again with ' journalctl -b | grep udev ' as well as ' journalctl -b | grep swap ' and ' journalctl -b | grep mount '

Do you have any special rules configured in /etc/udev/rules.d/ ?

Your systemd-analyze blame shows some lvm- and nfs-related stuff which seems not to be reflected in your fstab and blkid outputs. So if you do not use either of them, you might apt-get purge packages related to lvm2 and/or nfs.

[tuxic]

First:

Code: [Select]

tuxic@sid-box:~$ journalctl -b | grep udev
Jul 16 05:45:22 sid-box systemd-udevd[115]: starting version 204
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Kernel Socket.
Jul 16 05:45:22 sid-box systemd[1]: Listening on udev Kernel Socket.
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Control Socket.
Jul 16 05:45:22 sid-box systemd[1]: Listening on udev Control Socket.
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Coldplug all Devices...
Jul 16 05:45:22 sid-box systemd-udevd[267]: starting version 204
Jul 16 05:45:22 sid-box systemd[1]: Starting udev Kernel Device Manager...
Jul 16 05:45:54 sid-box systemd[1]: Started udev Wait for Complete Device Initialization.

and:

Code: [Select]


tuxic@sid-box:~$ journalctl -b | grep mount
Jul 16 05:45:22 sid-box kernel: EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
Jul 16 05:45:22 sid-box systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Jul 16 05:45:22 sid-box systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Jul 16 05:45:22 sid-box systemd[1]: Starting Remount Root and Kernel File Systems...
Jul 16 05:45:22 sid-box kernel: EXT4-fs (sda5): re-mounted. Opts: (null)
Jul 16 05:45:22 sid-box systemd[1]: Started Remount Root and Kernel File Systems.


[tuxic]

Sorry but I forgot:

Code: [Select]

tuxic@sid-box:~$ journalctl -b | grep swap
Jul 16 05:45:22 sid-box systemd[1]: Activating swap /swapfile...
Jul 16 05:45:22 sid-box swapon[361]: swapon: /swapfile: stat failed: No such file or directory
Jul 16 05:45:22 sid-box systemd[1]: swapfile.swap swap process exited, code=exited status=255
Jul 16 05:45:22 sid-box systemd[1]: Failed to activate swap /swapfile.
Jul 16 05:45:22 sid-box systemd[1]: Unit swapfile.swap entered failed state.

[tuxic]

Already purged everything related to nfs and lvm2

[tuxic]

I think we're in the right direction! Latest reboot:

Code: [Select]

tuxic@sid-box:~$ systemd-analyze blame
           777ms systemd-modules-load.service
           383ms networking.service
           170ms console-setup.service
           153ms rpcbind.service
           100ms keyboard-setup.service
            95ms loadcpufreq.service
            94ms ModemManager.service
            85ms udisks2.service
            78ms bootlogs.service
            71ms gpm.service
            56ms preload.service
            53ms ntp.service
            44ms systemd-fsck-root.service
            44ms systemd-logind.service
            41ms kbd.service
            29ms systemd-udev-trigger.service
            28ms live-config.service
            26ms alsa-restore.service
            25ms console-kit-log-system-start.service
            25ms irqbalance.service
            23ms ifplugd.service
            20ms systemd-journal-flush.service
            19ms cpufrequtils.service
            19ms hddtemp.service
            18ms motd.service
            18ms acpi-support.service
            18ms systemd-tmpfiles-setup-dev.service
            17ms polkitd.service
            16ms smartmontools.service
            16ms console-kit-daemon.service
            15ms hdparm.service
            15ms dev-mqueue.mount
            14ms sys-kernel-debug.mount
            13ms sysstat.service
            13ms dev-hugepages.mount
            13ms resolvconf.service
            12ms dns-clean.service
            12ms lm-sensors.service
            12ms upower.service
            10ms systemd-tmpfiles-setup.service
            10ms pppd-dns.service
             8ms keymap.service
             8ms systemd-remount-fs.service
             7ms systemd-sysctl.service
             6ms rc-local.service
             6ms live.service
             6ms live-tools.service
             6ms systemd-udevd.service
             6ms systemd-user-sessions.service
             5ms ifup@eth0.service
             5ms swapfile.swap
             5ms systemd-random-seed-load.service
             3ms systemd-update-utmp-runlevel.service
             2ms udev-finish.service
             2ms run-user.mount
             1ms run-lock.mount

I'll reboot agains and see how it goes...

[tuxic]

I think that something related to nfs or lvm2 was conflicting with my booth because now it melts like butter in a sunny day!

Code: [Select]


tuxic@sid-box:~$ systemd-analyze blame
           778ms systemd-modules-load.service
           570ms console-setup.service
           556ms networking.service
           107ms keyboard-setup.service
           101ms udisks2.service
            94ms loadcpufreq.service
            94ms ModemManager.service
            89ms gpm.service
            78ms bootlogs.service
            55ms ntp.service
            51ms systemd-fsck-root.service
            44ms systemd-logind.service
            41ms alsa-restore.service
            36ms kbd.service
            33ms console-kit-log-system-start.service
            29ms live-config.service
            28ms systemd-udev-trigger.service
            27ms ifplugd.service
            27ms preload.service
            24ms rpcbind.service
            23ms console-kit-daemon.service
            23ms hddtemp.service
            22ms acpi-support.service
            22ms motd.service
            22ms irqbalance.service
            21ms polkitd.service
            17ms dns-clean.service
            17ms smartmontools.service
            16ms dev-mqueue.mount
            16ms ifup@eth0.service
            16ms lm-sensors.service
            15ms systemd-tmpfiles-setup.service
            15ms sys-kernel-debug.mount
            15ms systemd-tmpfiles-setup-dev.service
            15ms dev-hugepages.mount
            14ms sysstat.service
            14ms cpufrequtils.service
            14ms systemd-journal-flush.service
            13ms hdparm.service
            12ms pppd-dns.service
            10ms upower.service
             9ms rc-local.service
             9ms swapfile.swap
             9ms systemd-sysctl.service
             9ms systemd-random-seed-load.service
             8ms keymap.service
             8ms systemd-user-sessions.service
             7ms resolvconf.service
             7ms live-tools.service
             6ms live.service
             4ms systemd-remount-fs.service
             4ms systemd-update-utmp-runlevel.service
             3ms run-user.mount
             3ms run-lock.mount
             3ms systemd-udevd.service
             2ms udev-finish.service


Thanks for your pacience!
@dibl; @agaida; @der_bud; @piper; @GoingEasy9

[tuxic]

I'll wait a day or two to see how it goes to mark it solved.

[dibl]

That looks much better.  But I would still expect to find a systemd-udev-settle.service process on the list -- does it no longer show at all?

[tuxic]

Now with ntfs-config installed:

Code: [Select]

tuxic@sid-box:~$ systemd-analyze blame
           768ms systemd-modules-load.service
           706ms media-Storage.mount
           249ms media-Back_Up.mount
           106ms keyboard-setup.service
           101ms udisks2.service
            99ms ModemManager.service
            96ms console-setup.service
            96ms loadcpufreq.service
            92ms systemd-fsck-root.service
            79ms gpm.service
            74ms bootlogs.service
            65ms networking.service
            57ms preload.service
            53ms ntp.service
            50ms systemd-logind.service
            36ms rpcbind.service
            34ms live-config.service
            34ms irqbalance.service
            31ms systemd-udev-trigger.service
            29ms systemd-tmpfiles-clean.service
            28ms console-kit-daemon.service
            22ms hdparm.service
            21ms alsa-restore.service
            20ms console-kit-log-system-start.service
            19ms dev-mqueue.mount
            19ms polkitd.service
            18ms ifplugd.service
            18ms sys-kernel-debug.mount
            17ms dev-hugepages.mount
            17ms hddtemp.service
            16ms motd.service
            16ms acpi-support.service
            15ms ifup@eth0.service
            14ms dns-clean.service
            14ms lm-sensors.service
            14ms cpufrequtils.service
            14ms smartmontools.service
            13ms kbd.service
            12ms upower.service
            11ms sysstat.service
            11ms live.service
            11ms live-tools.service
            11ms systemd-journal-flush.service
            10ms systemd-tmpfiles-setup-dev.service
            10ms systemd-tmpfiles-setup.service
             8ms systemd-sysctl.service
             8ms keymap.service
             8ms systemd-remount-fs.service
             6ms pppd-dns.service
             6ms resolvconf.service
             5ms rc-local.service
             4ms systemd-user-sessions.service
             3ms systemd-udevd.service
             3ms systemd-update-utmp-runlevel.service
             3ms systemd-random-seed-load.service
             2ms swapfile.swap
             2ms udev-finish.service
             1ms run-user.mount
             1ms run-lock.mount

@dibl - I don't see it. Is it essential?

[tuxic]

Shedding some light:


http://0pointer.de/blog/projects/blame-game.html


Extract:

Knowing what we know now we can go and disable udev-settle.service[/size] for the next boots: since neither LVM, RAID nor Multipath is used we can mask the services in question and thus speed up our boot a little:

I'm in the learning process...

[dibl]

Cool -- I didn't know it was safe to do that.

I'm in the learning process...

Yeah, I know -- I've never gotten out of it, either.   

[der_bud]

That looks much better.  But I would still expect to find a systemd-udev-settle.service process on the list -- does it no longer show at all?

I don't see no trace of udev-settle on a system without lvm/raid/mdadm/whatever, so that seems to be okay.

tuxic, from your post with 'journalctl -b | grep swap' it seems you have not configured swap properly. So either set up the swapfile you mention in fstab according to http://www.cyberciti.biz/faq/linux-add-a-swap-file-howto/ (for example), or better use the swap-partition you already have according to your blkid:

...
/dev/sdc2  swap             (not mounted)  321355cd-0908-4b71-87a7-d5602526a308
...