Very slow start up, please help!

English Install/Boot/Login
1

I am running TW on a dual-core amd64 box with 4 GB RAM. Tumbleweed takes quite a long time to start up, compared to Fedora23, Debian 8.4 and Linux Mint 17.3 on the same PC.


systemd-analyze blame

shows:


4min 47.135s purge-kernels.service
         31.257s wicked.service
         10.112s SuSEfirewall2_init.service
          9.064s systemd-udev-settle.service
          8.728s systemd-journal-flush.service
          7.764s dev-sda7.device
          3.332s systemd-journald.service
          3.076s systemd-udevd.service
          2.500s ModemManager.service
          2.072s lvm2-activation-early.service
          1.308s display-manager.service
          1.016s SuSEfirewall2.service
           936ms systemd-tmpfiles-setup-dev.service
           904ms lvm2-activation-net.service
           752ms ntpd.service
           732ms lvm2-activation.service
           708ms polkit.service                                                                                                                
           632ms systemd-tmpfiles-clean.service                                                                                                
           608ms wickedd-dhcp4.service                                                                                                         
           608ms wickedd-dhcp6.service                                                                                                         
           600ms wickedd-auto4.service                                                                                                         
           548ms nscd.service                                                                                                                  
           428ms systemd-udev-trigger.service                                                                                                  
           380ms systemd-rfkill.service                                                                                                        
           372ms upower.service                                                                                                                
           340ms auditd.service                                                                                                                
           328ms systemd-random-seed.service                                                                                                   
           324ms systemd-remount-fs.service                                                                                                    
           304ms avahi-daemon.service                                                                                                          
           292ms systemd-logind.service                                                                                                        
           288ms systemd-fsck-root.service                                                                                                     
           276ms sys-kernel-debug.mount                                                                                                        
           268ms dev-mqueue.mount
           264ms wickedd.service
           240ms wpa_supplicant.service
           228ms alsa-restore.service
           224ms mcelog.service
           224ms rc-local.service
           220ms systemd-fsck@dev-disk-by\x2duuid-2d258bc7\x2df03a\x2d4c5c\x2d8297\x2d78ef63a5bdde.service
           216ms dev-hugepages.mount
           216ms systemd-vconsole-setup.service
           188ms user@475.service
           180ms udisks2.service
           176ms plymouth-read-write.service
           176ms wickedd-nanny.service
           140ms systemd-udev-root-symlink.service
           136ms user@1000.service
           132ms systemd-tmpfiles-setup.service
           100ms kmod-static-nodes.service
            96ms systemd-modules-load.service
            80ms systemd-update-utmp-runlevel.service
            60ms iscsi.service
            44ms plymouth-start.service
            40ms rtkit-daemon.service
            36ms home.mount
            32ms systemd-update-utmp.service
            28ms systemd-user-sessions.service
            20ms dracut-shutdown.service
            12ms sys-fs-fuse-connections.mount
             4ms var-run.mount
             4ms systemd-sysctl.service
lines 23-61/61 (END)

Any service I should remove to shorten start up time? Thanks a lot for your help.

:frowning:

2

Looks like wicked is taking the time it is the Net program for hard-wired connection. Maybe check the settings in Yast-network card. Also maybe try switching to network Manager

3

same problem here. Change to Network manager didn’t solve it.

4

Show
systemd-analyze blame

5

18.281s wicked.service
4.014s esets.service
1.242s postfix.service
1.203s apparmor.service
980ms upower.service
893ms systemd-journal-flush.service
724ms SuSEfirewall2.service
655ms dev-sdb2.device
577ms display-manager.service
474ms SuSEfirewall2_init.service
462ms cups.service
251ms systemd-udevd.service
233ms systemd-fsck@dev-disk-by\x2duuid-01ca7628\x2dc54c\x2d4917\x2db9
231ms ModemManager.service
222ms systemd-tmpfiles-clean.service
174ms systemd-vconsole-setup.service
154ms user@1000.service
122ms home.mount
118ms wpa_supplicant.service
108ms rc-local.service
105ms mcelog.service
102ms user@1001.service
101ms ntpd.service
95ms udisks2.service
84ms user@481.service
80ms systemd-fsck@dev-disk-by\x2duuid-960da388\x2dd835\x2d438f\x2da2
72ms polkit.service

6

That was the startup with wicked. And now with network manager:

9.191s NetworkManager-wait-online.service
4.001s esets.service
1.363s postfix.service
1.236s apparmor.service
1.229s upower.service
803ms SuSEfirewall2.service
717ms dev-sdb2.device
666ms systemd-journal-flush.service
581ms display-manager.service
462ms SuSEfirewall2_init.service
401ms cups.service
249ms ModemManager.service
227ms systemd-udevd.service
221ms systemd-fsck@dev-disk-by\x2duuid-01ca7628\x2dc54c\x2d4917\x2db9
169ms systemd-vconsole-setup.service
160ms user@1000.service
158ms udisks2.service
102ms home.mount
101ms issue-generator.service
90ms avahi-daemon.service
86ms systemd-tmpfiles-setup-dev.service
83ms polkit.service
75ms NetworkManager.service

7

Neither looks all that bad

Here is mine in comparison. Note that my last boot was for a kernel update so ignore first entry


gogalthorp@linux422:~> systemd-analyze blame
         21.541s purge-kernels.service
         15.606s wicked.service
          5.603s fstrim.service
           730ms display-manager.service
           527ms apparmor.service
           525ms dev-sda2.device
           440ms SuSEfirewall2.service
           390ms systemd-journal-flush.service
           280ms postfix.service
           249ms ModemManager.service
           243ms systemd-fsck@dev-disk-by\x2duuid-56d26ae8\x2d356c\x2d41b7\x2d8795\x2d8c85e618fbff.service
           232ms smb.service
           181ms systemd-udevd.service
           176ms SuSEfirewall2_init.service
           142ms nmb.service
           115ms lm_sensors.service
           109ms nscd.service
           105ms systemd-fsck@dev-disk-by\x2duuid-3bd79acb\x2d9f73\x2d411b\x2dacae\x2dd5c1f8debf48.service
           104ms rc-local.service
            98ms vm.mount
            95ms user@1000.service
            63ms ntpd.service
            59ms home.mount
            55ms polkit.service
            55ms avahi-daemon.service
            51ms systemd-udev-trigger.service
            38ms upower.service
            38ms udisks2.service
            33ms iscsi.service
            30ms plymouth-start.service
            27ms user@481.service
            26ms systemd-journald.service
            21ms wickedd-auto4.service
            21ms sys-kernel-debug.mount
            21ms systemd-remount-fs.service
            20ms wickedd-dhcp4.service
            19ms wickedd-dhcp6.service
            18ms systemd-fsck-root.service
            18ms dev-hugepages.mount
            18ms systemd-vconsole-setup.service
            17ms systemd-logind.service
            16ms systemd-tmpfiles-setup-dev.service
            16ms plymouth-read-write.service
            15ms systemd-udev-root-symlink.service
            15ms systemd-sysctl.service
            14ms kmod-static-nodes.service
            13ms systemd-modules-load.service
            12ms dev-disk-by\x2duuid-0c96f85a\x2d98a7\x2d468a\x2d99a0\x2d0ccef905d6c3.swap
            11ms dev-mqueue.mount
            10ms systemd-tmpfiles-setup.service
             9ms systemd-user-sessions.service
             7ms rtkit-daemon.service
             7ms auditd.service
             6ms wickedd-nanny.service
             6ms systemd-random-seed.service
             5ms wickedd.service
             5ms alsa-restore.service
             5ms systemd-update-utmp.service
             4ms systemd-tmpfiles-clean.service
             4ms systemd-update-utmp-runlevel.service
             4ms dracut-shutdown.service
             2ms sys-fs-fuse-connections.mount

On a 6 core AMD 6300 FX CPU and root partition on a SSD

8

Hi
Also look at critical-chain;


systemd-analyze
systemd-analyze critical-chain

With NetworkManager I set the config (/etc/sysconfig/network/config) to blank;


WAIT_FOR_INTERFACES="30"

to

WAIT_FOR_INTERFACES=""

From my experience bootup time is subjective and have found that critical-chain (userspace) is more informative if booting to a desktop. Likewise, if it’s a single boot system, I remove plymouth (Add locks to the plymouth packages so they don’t re-install and rebuild intird) and set the grub menu to 0, don’t probe for another OS and hidden…

My 2007 MacBook 3,1 Core2 Duo with Tumbleweed boots;


systemd-analyze
Startup finished in 2.009s (kernel) + 2.424s (initrd) + 5.425s (userspace) = 9.859s

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 @5.385s
└─multi-user.target @5.385s
  └─cron.service @5.384s
    └─postfix.service @3.135s +2.247s
      └─time-sync.target @3.133s
        └─ntpd.service @2.814s +318ms
          └─network.target @2.803s
            └─NetworkManager.service @2.677s +126ms
              └─SuSEfirewall2_init.service @1.933s +742ms
                └─sysinit.target @1.929s
                  └─sys-fs-fuse-connections.mount @5.136s +34ms
                    └─systemd-modules-load.service @216ms +31ms
                      └─systemd-journald.socket
                        └─-.slice

This HP 255 G4 (AMD Quad Core) openSUSE Leap 42.2 boot info;


systemd-analyze
Startup finished in 5.366s (firmware) + 1.217s (loader) + 4.426s (kernel) + 2.480s (initrd) + 6.679s (userspace) = 20.170s

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 @6.652s
└─multi-user.target @6.652s
  └─SuSEfirewall2.service @2.311s +1.189s
    └─network.target @2.249s
      └─wpa_supplicant.service @3.101s +67ms
        └─basic.target @1.805s
          └─sockets.target @1.805s
            └─dbus.socket @1.805s
              └─sysinit.target @1.805s
                └─sys-fs-fuse-connections.mount @5.485s +24ms
                  └─systemd-modules-load.service @198ms +20ms
                    └─system.slice
                      └─-.slice