Results 1 to 5 of 5

Thread: Why is OpenSUSE Tumbleweed taking ages to boot?

  1. #1

    Default Why is OpenSUSE Tumbleweed taking ages to boot?

    Hi all,
    recently installed openSUSE and I can say I am loving it! However I noticed that it is taking anywhere from 2-4 mins to boot. The first time I booted it after installation it took seconds (should note this is on an ssd) but now it seems to be taking forever. I havent done anyting but install steam and nvidia drivers and a few other programs. Here is the first 3 lines of my systemd-analyze blame output
    Text
    2min 3.902s btrfsmaintenance-refresh.service
    2min 2.166s chrony-wait.service
    1min 59s plymouth-quit-wait.service

    I have no clue what these services are and why they are taking so long, please someone help!

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,564

    Default Re: Why is OpenSUSE Tumbleweed taking ages to boot?

    If you inspect /etc/fstab, is btrfs present anywhere? If not:
    Code:
     sudo zypper rm btrfs*
    may be all you need to do. You seem to be describing https://bugzilla.opensuse.org/show_bug.cgi?id=1124823
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  3. #3
    Join Date
    Apr 2016
    Location
    North America
    Posts
    452

    Default Re: Why is OpenSUSE Tumbleweed taking ages to boot?

    Quote Originally Posted by rjerham04 View Post
    I have no clue what these services are...
    You can use

    Code:
    systemctl cat chrony-wait.service
    which will give you some information, and the relevant "man page".

  4. #4
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    885

    Default Re: Why is OpenSUSE Tumbleweed taking ages to boot?

    Quote Originally Posted by rjerham04 View Post
    Hi all,
    recently installed openSUSE and I can say I am loving it! However I noticed that it is taking anywhere from 2-4 mins to boot. The first time I booted it after installation it took seconds (should note this is on an ssd) but now it seems to be taking forever. I havent done anyting but install steam and nvidia drivers and a few other programs. Here is the first 3 lines of my systemd-analyze blame output
    Text
    2min 3.902s btrfsmaintenance-refresh.service
    2min 2.166s chrony-wait.service
    1min 59s plymouth-quit-wait.service

    I have no clue what these services are and why they are taking so long, please someone help!
    My system has:
    Code:
    erlangen:~ # systemd-analyze blame|head
        4min 14.403s fstrim.service
        1min 46.299s mlocate.service
             25.745s backup-albums.service
             12.977s backup-rpmdb.service
              3.799s systemd-networkd-wait-online.service
              2.848s display-manager.service
              2.424s plymouth-quit-wait.service
              1.348s systemd-logind.service
               656ms apparmor.service
               622ms mcelog.service
    erlangen:~ #
    The above doesn't matter. What really matters:

    Code:
    erlangen:~ # 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 @8.429s
    └─display-manager.service @5.580s +2.848s
      └─apache2.service @5.484s +95ms
        └─remote-fs.target @5.483s
          └─iscsi.service @5.477s +5ms
            └─network-online.target @5.474s
              └─systemd-networkd-wait-online.service @1.673s +3.799s
                └─systemd-networkd.service @1.178s +494ms
                  └─network-pre.target @1.177s
                    └─firewalld.service @897ms +279ms
                      └─dbus.service @895ms
                        └─basic.target @889ms
                          └─paths.target @889ms
                            └─cups.path @839ms
                              └─sysinit.target @837ms
                                └─apparmor.service @179ms +656ms
                                  └─systemd-journald.socket
                                    └─-.mount
                                      └─system.slice
                                        └─-.slice
    erlangen:~ #
    The times include the wait for network configuration.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  5. #5
    Join Date
    Mar 2019
    Location
    mtl.qc.ca
    Posts
    118

    Default Re: Why is OpenSUSE Tumbleweed taking ages to boot?

    When the machine stalls, click escape to get supplementary information from the splash screen.

    Maybe a stop job is running?
    Ryzen 2700U FHD Lenovo ThinkPad E585

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •