Optimize boot

Good morning my friends,

I switched one of my Notebooks to openSUSE Tumleweed but the boot time is not fast enough for me or atleast I want to optimize it.
Normally I boot around 30s - 35s.
I already disabled a few services but I didn’t got any real boost from it. I do need NetworkManager and VMware, disabling it is no option for me.

ursamajor@OpenSuseUrsamajor:~> systemd-analyze
Startup finished in 4.838s (firmware) + 3.508s (loader) + 1.152s (kernel) + 5.239s (initrd) + 32.303s (userspace) = 47.041s
ursamajor@OpenSuseUrsamajor:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @32.293s
└─multi-user.target @32.293s
  └─vmware.service @26.730s +5.562s
    └─network-online.target @26.729s
      └─network.target @26.727s
        └─NetworkManager.service @15.579s +3.401s
          └─basic.target @15.577s
            └─sockets.target @15.567s
              └─iscsid.socket @15.557s
                └─sysinit.target @15.526s
                  └─sys-fs-fuse-connections.mount @27.898s +3ms
                    └─systemd-modules-load.service @2.785s +175ms

ursamajor@OpenSuseUrsamajor:~> systemd-analyze blame         
          12.504s dev-sda3.device
          9.848s systemd-journald.service
          7.865s systemd-udev-settle.service
          7.735s NetworkManager-wait-online.service
          5.562s vmware.service
          3.401s NetworkManager.service
          3.327s display-manager.service
          3.136s vmware-USBArbitrator.service
          2.567s alsa-restore.service
          2.546s rc-local.service
          2.470s wpa_supplicant.service
          1.878s systemd-udevd.service
          1.468s systemd-journal-flush.service
          1.302s systemd-backlight@backlight:intel_backlight.service
          1.186s systemd-vconsole-setup.service
          1.024s polkit.service
           802ms accounts-daemon.service
           797ms boot-efi.mount
           773ms upower.service
           657ms systemd-tmpfiles-setup-dev.service
           638ms systemd-fsck-root.service
           614ms sys-kernel-debug.mount
           577ms dev-mqueue.mount
           576ms dev-hugepages.mount
           380ms lvm2-activation-early.service
           348ms systemd-sysctl.service
           336ms lvm2-activation-net.service
           336ms systemd-udev-trigger.service
           331ms systemd-logind.service
           326ms iscsi.service
           263ms udisks2.service
           241ms systemd-udev-root-symlink.service
           239ms user@478.service
           228ms systemd-random-seed.service
           210ms kmod-static-nodes.service
           209ms lvm2-activation.service
           175ms systemd-modules-load.service
           173ms systemd-tmpfiles-setup.service
           163ms systemd-user-sessions.service
           161ms systemd-remount-fs.service
           135ms dev-disk-by\x2duuid-1597657e\x2dec17\x2d4046\x2d9bb7\x2d5d20baf60f
            96ms systemd-rfkill@rfkill0.service
            91ms systemd-rfkill@rfkill1.service
            64ms rtkit-daemon.service
            42ms systemd-update-utmp.service
            35ms user@1000.service
             6ms systemd-update-utmp-runlevel.service
             3ms sys-fs-fuse-connections.mount

Last but not least the plot.svg

Looks like /sys/fs/fuse/connection waits for something for 25 seconds. Not sure what it is; do you have it in /etc/fstab?

Output of /etc/fstab.

UUID=1597657e-ec17-4046-9bb7-5d20baf60f60 swap                 swap       defaults              0 0UUID=aee42340-3506-401e-b2ab-861e186459d5 /                    ext4       acl,user_xattr        1 1
UUID=EFC4-A109       /boot/efi            vfat       umask=0002,utf8=true  0 0

That are the only partition on my hdd, no separate /home partition.

One of the first things you explain is that youuse Tumbleweed.
Why didn’t you post in the Tumbleweed, Evergreen and PreRelease/Beta, subforum?

Well I tought that it would relate to general optimization of the boot process, if I placed the thread wrong I apologies for this missplacement.

Booting without plugged in Ethernet.

systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @22.152s
└─multi-user.target @22.152s
  └─vmware.service @17.639s +4.512s
    └─network-online.target @17.638s
      └─network.target @17.637s
        └─NetworkManager.service @10.238s +1.908s
          └─basic.target @9.388s
            └─sockets.target @9.386s
              └─pcscd.socket @9.386s
                └─sysinit.target @9.385s
                  └─sys-fs-fuse-connections.mount @18.420s +3ms
                    └─systemd-modules-load.service @3.081s +425ms

The thing is that you might think that it is version independent, but imagine what the people browsing these threads might think. Most of the people browsing this subforums are not Tumbleweed users themselves. Thus they will not feel entitled to aner anything. Where OTOH, in the Tumblweed subforum there might be Tummbleweed users just looking if they can halep other Tumbleweed users and not looking elsewhere.

In short, it is not about if you thinking it is version independent (might be, but are you very, very sure, you better prove it then by testing it on e.g. 13.2 and mentioning that), but where you will find the most potential helpers with knowledge about your environment.

There is no need to apologize, it is about your own best chances to get help.

(BTW, when you want it moved, ask here and I will execute that.)

I fully understand you and you are right it should be moved. So please move this thread to the appropriate subforum.

A user on reddit mentioned that my system basically waits for the network to come up for it to launch vmware services and other services. The last time I used this setup on this machine it did not take that long to boot (we already got the wrong subforum thing covered :p).
I dont use normally VMware but I am forced to use it now also I need my plugged in Ethernet for frequently used streaming purposes.

Will be moved to Tumbleweed and is CLOSED for the moment.

Move from Instal/Boot/Login and open again.

Actually, no.

The fuse item starts at time 27.898

The time after the unit is active or started is printed after the “@” character.

But only takes 3 milliseconds to load

The time the unit takes to start is printed after the “+” character.


I never said it took 25 seconds to load. I said it waited 25 seconds before starting to load at least if we can trust critical-chain output. But I now suspect that it lies. On my system right now critical-chain shows

                  └─local-fs.target @17.825s
                    └─run-user-501-gvfs.mount @1min 9.708s
                      └─local-fs-pre.target @4.798s

which is pure nonsense because /run/user/501/gvfs is mounted after I logged in, which is way after local-fs.target has finished.