• Yet another very slow boot topic.


    Hi, been using Antergos for about 2 years now, and finally decided to investigate this issue. The time until I get to use the desktop has been going up for some months now. Any help would be appreciated because I’ve read all the other topics and I still don’t know what to do.

    [[email protected] ~]$ systemd-analyze blame
        8min 53.798s man-db.service
        1min 32.116s updatedb.service
              9.380s systemd-journal-flush.service
              9.067s lvm2-monitor.service
              8.790s nmb.service
              8.067s ModemManager.service
              7.714s dev-sdc3.device
              6.799s samba.service
              4.961s polkit.service
              3.743s systemd-udevd.service
              2.707s upower.service
              2.666s udisks2.service
              1.845s lightdm.service
              1.827s accounts-daemon.service
              1.704s NetworkManager.service
              1.473s avahi-daemon.service
              1.466s systemd-logind.service
              1.463s alsa-restore.service
              1.205s systemd-tmpfiles-setup-dev.service
              1.178s org.cups.cupsd.service
               885ms systemd-timesyncd.service
               845ms wpa_supplicant.service
               835ms logrotate.service
               774ms smb.service
               550ms systemd-tmpfiles-setup.service
               533ms colord.service
               490ms systemd-journald.service
               457ms systemd-modules-load.service
               298ms boot-efi.mount
               292ms dev-disk-by\x2duuid-8bc22439\x2db9d8\x2d46bd\x2da700\x2da50a41>
               290ms systemd-udev-trigger.service
               233ms systemd-random-seed.service
               176ms haveged.service
               172ms systemd-binfmt.service
               167ms systemd-sysctl.service
               131ms sys-kernel-debug.mount
               130ms dev-hugepages.mount
               120ms kmod-static-nodes.service
               111ms [email protected]
               107ms [email protected]:acpi_video0.service
                93ms systemd-update-utmp.service
                91ms boot.mount
                43ms systemd-user-sessions.service
                43ms systemd-tmpfiles-clean.service
                40ms systemd-remount-fs.service
                29ms rtkit-daemon.service
                13ms [email protected]
                 7ms tmp.mount
                 5ms sys-fs-fuse-connections.mount
                 5ms dev-mqueue.mount
                 4ms proc-sys-fs-binfmt_misc.mount
                 3ms sys-kernel-config.mount
    
    [[email protected] ~]$ systemd-analyze
    Startup finished in 10.362s (firmware) + 5.770s (loader) + 3.547s (kernel) + 25.224s (userspace) = 44.904s 
    graphical.target reached after 25.224s in userspace
    [[email protected] ~]$ 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 @25.224s
    └─multi-user.target @25.224s
      └─smb.service @24.449s +774ms
        └─nmb.service @15.656s +8.790s
          └─network-online.target @15.582s
            └─network.target @15.582s
              └─NetworkManager.service @13.876s +1.704s
                └─dbus.service @13.867s
                  └─basic.target @13.866s
                    └─sockets.target @13.866s
                      └─org.cups.cupsd.socket @13.866s
                        └─sysinit.target @13.816s
                          └─systemd-timesyncd.service @12.930s +885ms
                            └─systemd-tmpfiles-setup.service @12.342s +550ms
                              └─systemd-journal-flush.service @2.961s +9.380s
                                └─systemd-journald.service @2.469s +490ms
                                  └─systemd-journald-dev-log.socket @2.467s
                                    └─system.slice @2.010s
                                      └─-.slice @2.010s
    
    

    It was slow before, but it was much slower since I installed samba.

    TIA

  • @Morrison

    man systemd.timer
    

    You might want to try changing how the timers start at files
    /usr/lib/systemd/system/man-db.timer
    /usr/lib/systemd/system/updatedb.timer

    Under [Timer] you could add definition:

    RandomizedDelaySec=20min
    

    Note that I haven’t tested this, but the manual page should tell you more.

  • also, updatedb is part of mlocate , mandb stil have if you do in terminal sudo mandb ,atleast to build up would it not be faster at boot later on.

    myself i dont have mlocate anymore :) but both are the longest in boot time as manual saids would be the thing indeed

  • @manuel Great, so now I know what man-db and updatedb are, and they were scheduled to run every 12h. That means that the second boot is much faster because those services don’t run the second time. I modified the files as you said, I believe to prevent the HDD from choking at boot, and lets hope the next first boot will be much faster.

    Is it possible to further improve boot time? This are the new logs that don’t run the named services:

    [[email protected] ~]$ systemd-analyze blame
              9.455s systemd-journal-flush.service
              9.082s nmb.service
              8.919s lvm2-monitor.service
              7.655s dev-sdc3.device
              7.579s ModemManager.service
              7.166s samba.service
              4.211s polkit.service
              3.585s systemd-udevd.service
              2.400s lightdm.service
              2.286s upower.service
              1.824s NetworkManager.service
              1.691s udisks2.service
              1.396s systemd-logind.service
              1.387s avahi-daemon.service
              1.173s systemd-tmpfiles-setup-dev.service
              1.073s smb.service
              1.045s org.cups.cupsd.service
               768ms systemd-timesyncd.service
               688ms accounts-daemon.service
               645ms wpa_supplicant.service
               574ms colord.service
               539ms systemd-random-seed.service
               456ms systemd-journald.service
               424ms systemd-tmpfiles-setup.service
               379ms systemd-modules-load.service
               350ms systemd-udev-trigger.service
               335ms systemd-binfmt.service
               272ms boot-efi.mount
               261ms dev-disk-by\x2duuid-8bc22439\x2db9d8\x2d46bd\x2da700\x2da50a41>
               210ms haveged.service
               195ms systemd-sysctl.service
               151ms boot.mount
               125ms kmod-static-nodes.service
               125ms dev-hugepages.mount
               123ms sys-kernel-debug.mount
               107ms tmp.mount
                92ms [email protected]
                84ms [email protected]:acpi_video0.service
                82ms systemd-update-utmp.service
                53ms rtkit-daemon.service
                49ms systemd-remount-fs.service
                38ms systemd-user-sessions.service
                21ms dev-mqueue.mount
                13ms [email protected]
                13ms alsa-restore.service
                 6ms sys-fs-fuse-connections.mount
                 2ms sys-kernel-config.mount
                 2ms proc-sys-fs-binfmt_misc.mount
    
    [[email protected]ergos ~]$ 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 @25.732s
    └─multi-user.target @25.731s
      └─smb.service @24.657s +1.073s
        └─nmb.service @15.572s +9.082s
          └─network-online.target @15.478s
            └─network.target @15.478s
              └─NetworkManager.service @13.653s +1.824s
                └─dbus.service @13.644s
                  └─basic.target @13.640s
                    └─paths.target @13.640s
                      └─org.cups.cupsd.path @13.639s
                        └─sysinit.target @13.590s
                          └─systemd-timesyncd.service @12.821s +768ms
                            └─systemd-tmpfiles-setup.service @12.369s +424ms
                              └─systemd-journal-flush.service @2.911s +9.455s
                                └─systemd-journald.service @2.453s +456ms
                                  └─systemd-journald-audit.socket @2.451s
                                    └─system.slice @2.019s
                                      └─-.slice @2.019s
    
    

    TIA

  • @Morrison
    Depends.
    Based on the “blame” times I guess you have a HDD and not SSD drive? If so, then I’d recommend changing to SSD, that will boost your machine quite a lot, and not just the boot time.

    And often having more RAM (how much RAM do you have now?) helps if you are using “heavy” programs (but may not help much at boot).

  • @manuel OK, thank you.

boot320 slow37 topic7 Posts 6Views 105
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.