• Is anyone havine Slow boot time?

    This really more of a general question, but it seems as of today it takes a good 4-5 minutes to boot to the plasma desktop.
    According to journal log looks closer to 10 minutes but idk

    What it’s doing at while booting just moves one line at a time very slow to start all the devices.
    Programs slow to respond and laggy in general yet the cpu is only at 4% useage

    I didn’t really know where to ask this because I don’t know whats causing it.

    Haven’t done much of anything but updates when I see them.

    https://www.dropbox.com/s/7qvs6rj2z6i3nuz/LOGS 7-4-18.zip?dl=0

  • what DM are you using?

  • systemd-analyze blame

    would be more simple first to get all units and its times it needs to start…

  • % minutes after I thought Everything was done it said Boot up is not yet finished, try later…went outside for six hours didn’t touch it and got this.

    $ systemd-analyze blame
       22min 32.221s updatedb.service
        7min 47.466s man-db.service
             44.879s ModemManager.service
             41.151s lvm2-monitor.service
             38.522s udisks2.service
             35.041s dev-sda2.device
             27.486s systemd-journal-flush.service
             24.126s lightdm.service
             23.437s polkit.service
             21.885s NetworkManager.service
             17.818s avahi-daemon.service
             17.804s systemd-logind.service
             17.570s logrotate.service
             11.715s systemd-udevd.service
             11.713s systemd-tmpfiles-clean.service
             11.647s accounts-daemon.service
              9.580s ufw.service
              9.194s dev-disk-by\x2duuid-cf1205fc\x2d4cea\x2d4af6\x2daffa\x2d7ab35f8cc829.swap
              5.405s boot-efi.mount
              4.992s systemd-modules-load.service
              4.796s upower.service
              4.567s systemd-tmpfiles-setup-dev.service
              3.545s systemd-timesyncd.service
              3.163s systemd-binfmt.service
              3.084s sys-kernel-debug.mount
              2.850s org.cups.cupsd.service
              2.768s dev-hugepages.mount
              2.765s systemd-remount-fs.service
              2.765s dev-mqueue.mount
              2.713s systemd-user-sessions.service
              2.102s systemd-tmpfiles-setup.service
              2.055s systemd-udev-trigger.service
              1.935s proc-sys-fs-binfmt_misc.mount
              1.103s home.mount
               918ms kmod-static-nodes.service
               913ms systemd-journald.service
               889ms [email protected]
               792ms systemd-random-seed.service
               749ms systemd-sysctl.service
               413ms systemd-update-utmp.service
               267ms rtkit-daemon.service
               203ms sys-kernel-config.mount
                46ms tmp.mount

    idky update would try to run at boot…IF that’s what it’s saying?

  • @joekamprad Nice cmd btw…thought you where jokeing with me at first…I kept thinking of the Blame-Thrower from the movie Mystery Men lmao

  • If like me you do not use mlocate or locate to find files then consider uninstalling mlocate, which should get rid of the updatedb.service. That is what I have done.
    Alternatively have look at /etc/updatedb.conf and consider adding more exemptions.
    I’m not sure what the contents are on Antergos since I’ve uninstalled mlocate, but my laptop with lubuntu could benefit from adding .cache and .thumbnails to PRUNE_NAMES.

  • @firespray said in Is anyone havine Slow boot time?:

    22min 32.221s updatedb.service

    this is way to much time… also if you have huge data storage …
    and also most of the rest all over 5 seconds is to much on a machine with a modern CPU …

  • What’s the output of …?

    $ systemd-analyze critical-chain

    I was playing around with sddm last week and had really long boot times before switching back to lightdm.

  • AH I have updates that look important, so here is this, and I’ll do updates then see if system still cranky lol

    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 @2min 6.167s
    └─lightdm.service @1min 40.746s +25.419s
      └─systemd-user-sessions.service @1min 38.944s +1.799s
        └─nss-user-lookup.target @1min 50.618s
  • updates didn’t do much…took forever!!!
    Hard drive just runs forever and is slow as hell.

    could there be bad spots in the drive?
    if so what tools to use to mark bad spots?

    just throwing that in there

  • Thanks @JuanBellas I’ll check that out…but @joekamprad …I know how much you loved what Nvidia did not long ago…any comment/influence on a new Antergos command called

    $ su kde-check-my-sh*t

    and does HD scan, memcheck and stuff n stuff checks everything LMAO

    idk, was just stopping in to check what the rig was doing & how long it was taking to do it…I wouldn’t think the drive is going bad, but something is choking everything right when grub starts…IT would seem as thats when it bogs down.

  • A DuckDuckGo search shows that users have had issues with low entropy, a possible kernel bug, could cause slow boot times. While booting, try moving the mouse around or hitting random keys and see if the boot time improves. There are workarounds for low entropy.

    Personally, I would try ruling out the lightdm.service by disabling it and trying to log in with a tty shell and then starting your DE with


    Verify that your user has an apropos ~/.xinitrc file for your DE before doing so. Or try installing a different DM. No issues here with Lightdm and Xfce in either Antergos or vanilla Arch.

  • thanks @triode13 I’ll consider that, but honestly since it doesn’t reach graphical target till the end of boot, idk what that helps…however, I’m not above trying that, but then again I need my system to work…I really would like to know what tf is going on but pretty peeved right now.
    Don’t get me wrong, I understand free systems and stuff but was lucky enough to to had the chance to get started using Arch as everyday system and understand stuff breaks, but at this point, I’m more likely to just put in a new drive and go from there…but the “need to know whats broke” is pretty strong so idk what I might do.
    Just pissed off right now as I have zero time to do much with system stuff like I used to.
    and that is what’s making me more mad than anything bc I want the time to dedicate to issues but can’t.
    I’m not going to give up though, don’t anyone reading this take anything that way, just don’t know which way I’m headed yet…it’s Friday for me so as long as I can watch /download what I need idc
    Having a trackball for all these years really makes it tempting to throw the mf when sh*t happens lol
    Hopefully some more updates will come out that fixes some things bc I was reading the installer was goofed up, but that might only be for certain peeps, we’ll see.
    I will say the load time got a little faster, I think…

    $ systemd-analyze blame
             55.127s lvm2-monitor.service
             44.316s ModemManager.service
             35.848s systemd-journal-flush.service
             33.453s dev-sda2.device
             31.273s NetworkManager.service
             20.037s polkit.service
             18.617s avahi-daemon.service
             18.037s systemd-logind.service
             13.894s dev-disk-by\x2duuid-cf1205fc\x2d4cea\x2d4af6\x2daffa\x2d7ab35f8cc829.swap
             13.256s lightdm.service
             12.437s systemd-udevd.service
             11.078s ufw.service
              7.319s udisks2.service
              5.849s accounts-daemon.service
              5.646s systemd-modules-load.service
              5.199s systemd-binfmt.service
              4.959s systemd-tmpfiles-setup-dev.service
              3.732s upower.service
              3.590s dev-mqueue.mount
              3.587s systemd-remount-fs.service
              3.586s dev-hugepages.mount
              3.585s sys-kernel-debug.mount
              3.581s proc-sys-fs-binfmt_misc.mount
              3.096s systemd-timesyncd.service
              2.671s systemd-udev-trigger.service
              2.483s org.cups.cupsd.service
              1.839s systemd-random-seed.service
              1.385s systemd-tmpfiles-clean.service
              1.366s systemd-sysctl.service
              1.358s rtkit-daemon.service
               882ms kmod-static-nodes.service
               855ms boot-efi.mount
               849ms [email protected]
               694ms systemd-user-sessions.service
               503ms systemd-journald.service
               414ms home.mount
               378ms systemd-tmpfiles-setup.service
               131ms sys-kernel-config.mount
                65ms systemd-update-utmp.service
                 9ms tmp.mount
    $ 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 @2min 536ms
    └─lightdm.service @1min 47.278s +13.256s
      └─systemd-user-sessions.service @1min 46.581s +694ms
        └─nss-user-lookup.target @1min 51.033s

    I’ll see what happens, BUT any thoughts on ANYTHING to try please mention it! I don’t want to re-install…it’s got to be a hicuup of some sort is all, and that does happen. Hope I wasn’t ranting…wife is talking and irritating me more lol

  • lmao, sry for wining…Just glad it’s the weekend and didn’t expect slow stuff :P

  • btw Yes DuckDuckgo is the way to go!..defund google!..and microsoft lol…alright…going to bed…

    …again, ruff night

  • @firespray do check what smart status say? may you are right and it is caused by bad drive…

    install: smartmontools
    check if smart is enabled: smartctl --info /dev/sda | grep 'SMART support is:'
    run test: sudo smartctl -t long /dev/sda
    check result: sudo smartctl -H /dev/sda

  • journalctl -p 3 -xb errors from journal
    systemctl --failed failed services

  • Fridays arne’t supposed to suck.
    The only thing I did successfully yesterday was manage to
    mow my lawn without loosing a body part lol

    Today was thinking more specifically about the drive. I thought maybe the sata cable was loose. Stuck my hand in the case and got hit by one of my fans and the power flicked off and back on. idk if that happens because of the fan stopping and starting…but turned off power.

    switched sata cable, switched sata ports, pulled out & pushed in the powersupply cable & switched usb ports on my bay device bc I saw some usb errors.

    The thing booted the fastest I’ve ever seen! Even my firefox with 50ish tabs opened really fast lol

    So, loose wires or cables or bad cable, or bad sata port

    $ systemd-analyze blame
              6.748s lvm2-monitor.service
              5.135s dev-sda2.device
              3.250s systemd-journal-flush.service
              2.694s ModemManager.service
              2.673s ufw.service
              2.314s NetworkManager.service
              2.217s systemd-tmpfiles-clean.service
              1.947s systemd-udevd.service
              1.778s udisks2.service
              1.648s avahi-daemon.service
              1.645s systemd-logind.service
              1.166s ldconfig.service
              1.084s upower.service
              1.070s systemd-sysusers.service
               932ms org.cups.cupsd.service
               928ms lightdm.service
               730ms systemd-modules-load.service
               591ms polkit.service
               578ms rtkit-daemon.service
               508ms accounts-daemon.service
               505ms systemd-timesyncd.service
               443ms systemd-tmpfiles-setup-dev.service
               442ms systemd-binfmt.service
               413ms systemd-udev-trigger.service
               406ms dev-mqueue.mount
               402ms systemd-tmpfiles-setup.service
               355ms dev-hugepages.mount
               355ms systemd-remount-fs.service
               354ms kmod-static-nodes.service
               353ms sys-kernel-debug.mount
               322ms boot-efi.mount
               294ms [email protected]
               250ms systemd-sysctl.service
               241ms systemd-random-seed.service
               176ms home.mount
               173ms systemd-journald.service
               168ms systemd-user-sessions.service
               143ms dev-disk-by\x2duuid-cf1205fc\x2d4cea\x2d4af6\x2daffa\x2d7ab35f8cc829.swap
               124ms systemd-update-utmp.service
               123ms systemd-journal-catalog-update.service
                58ms proc-sys-fs-binfmt_misc.mount
                34ms tmp.mount
                29ms systemd-update-done.service
                16ms sys-kernel-config.mount
    $ 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 @13.773s
    └─lightdm.service @12.844s +928ms
      └─systemd-user-sessions.service @12.675s +168ms
        └─nss-user-lookup.target @12.991s

    Those commands are awesome!

    So, as the great Inspector Clouseau would say, “The case has been solv-ed.” lmao

  • Forgot to mention, when it booted and ran

    $ journalctl -p 3 -xb

    It said my kwin composite couldn’t run which ment my Desktop cube wouldn’t work so
    I fixed that by editing .config/kwinrc

    In the section


    set true to false and reboot, Desktop Cube works again.
    Some of this issue must have changed it I guess.

boot319 slow37 havine1 Posts 21Views 2028
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.