Apparently the reason my computer has been taking 2 minutes to boot was a faulty network mount

  • @lntl@lemmy.ml
    6•1 year ago

    this is interesting! if i had a two minute boot time, I’d look for ways to figure out what’s going on.

    i remember init messages used to be printed to the console, but nowadays all i get is Manjaro branding. anyone know how to get my console messages back from systemd?

    • qazOP
      3•1 year ago

      Thanks for the article, I’ve already spotted a few utilities that can come in useful. I’ve heard a lot of criticism about systemd too, but never really actively used it myself until a few weeks ago. I actually quite like it from what I’ve seen so far.

    • qazOP
      4•1 year ago

      No, there currently isn’t

      And it’s not as easy to add actually. Note that systemd only keeps units loaded as long as they are referenced by something else that is loaded, are running, have failed, or have a job queued. That means if a service is terminated at shutdown there’s a very good chance it is GC’ed away pretty quickly. Now, while systemd keeps timestamping info around for services that tell us how long a service was running, took to start or took to shut down all that info is lost the instant the unit is GC’ed away…

      Source

    • MelllvarEnglish
      1•1 year ago

      Sysinternals Process Monitor can do boot logging.

    • qazOP
      2•1 year ago

      You can use the Windows Performance Recorder to capture the boot time and then use Windows Performance Analyzer to view the results. It should also be able to show the results as a timeline.

  • @miss_brainfart@lemmy.ml
    13•1 year ago

    It tells me that my system boots in 7 seconds. That’s pretty cool, considering that it’s installed on a plain old sata SSD.

    POST, however…

  • @passepartout@feddit.de
    113•1 year ago

    You can use systemd-analyze blame if you want raw numbers:

    This command prints a list of all running units, ordered by the time they took to initialize. This information may be used to optimize boot-up times.

    Good way to see if your systemd also waits 2 minutes for a network connection which already exists but it can’t see it because systemd doesn’t do the networking (lxc containers on proxmox in my case) lol.

    Also see systemd-analyze.

    • @FrostyPolicy@suppo.fi
      8•1 year ago

      systemd also waits 2 minutes for a network connection which already exists but it can’t see it because systemd doesn’t do the networking

      Any way to speed this up? On my system in every boot it waits for network for 30s.

      • @passepartout@feddit.de
        1•1 year ago

        In my case i masked the service because like i said, inside the lxc container there is no networking to do, it’s done on the host (proxmox). Note that disabling the service in my case was not enough since it could be invoked by other services, and then you would have to wait again.

        See this for further info and maybe arguments why you shouldn’t do it.

    • Random Dent
      1•1 year ago

      My main offender is something called updatedb.service, whatever that is.

  • @gayhitler420@lemm.ee
    26•1 year ago

    I wrote a long-ish comment in another thread explaining why lots of people don’t like systemd.

    Stuff like this is why people do like systemd.

    The massive, un unixy and complex tools allow for very powerful and somewhat knowledge agnostic approaches to all sorts of problems.

    One of the nicest things about systemds toolset is that it allows a person who relies on finding the problem and googling it to resolve thing much faster than their alternative, learn what’s going on and figure it out.

    I don’t mean that as a pejorative, plenty of computer work is maintenance as opposed to engineering and there’s nothing wrong with that.