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

  • jsdz@lemmy.ml
    82·
    3 years ago

    I’m pretty sure the main system startup bottleneck is me typing the disk encryption passphrase.

  • passepartout@feddit.de
    571·
    3 years 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.

    • qaz@lemmy.worldOP
      3·
      3 years 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

    • qaz@lemmy.worldOP
      31·
      3 years 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.

  • Pantherina@feddit.de
    10·
    3 years ago

    My bottleneck at boot is my damn Bios… I am so hyped about flashing Heads on my Thinkpad T430.

    Even the old legacy Lenovo bioses where very fast at startup. The UEFI (with extremely nice secure-boot settings too) of an AMD Acer starts up in like 2 seconds. My old intel Thinkpad T430 needs like 4 seconds.

    And then my Lenovo T495 bullshit UEFI comes. No secure boot configuration at all, I have no idea how to boot from USB sticks, and this thing needs nearly 10 seconds to boot! Linux compared, a full Desktop OS, needs 3 seconds to show SDDM (after the LUKS dialog)

    • Dkarma@lemmy.world
      4·
      3 years ago

      I adore my T530. I could kill a moose with it if it ever stops working. Literally dug it out of a dumpster and saw the i7 sticker and almost shit myself. Honestly I’ve had it for years and never even looked at the bios cuz with an SSD even with encryption enabled on the disk it booted in 30 sec.

      Until I built my latest rig I was doing ai image generation on it with 8gigs of ram.

      • Pantherina@feddit.de
        2·
        3 years ago

        If you have a T530, there is coreboot for it! Dont know if 1vyra.in works, check it.

        Its not the question, if it works, but how it works! Its trustworthy and not extremely outdated proprietary garbage. Actually extremely important to update

  • miss_brainfart@lemmy.ml
    9·
    3 years 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…

  • droidpenguin@lemmy.world
    7·
    3 years ago

    Dang had no idea this was a thing, but this looks very useful! I’ve been meaning to troubleshoot slow startup on one of my servers.

    • stifle867@programming.dev
      7·
      3 years ago

      I know you put bottleneck is quotes but just to explain… apparently this service is simply the splash screen that waits on a ready environment. It doesn’t actually delay anything.

  • lntl@lemmy.ml
    61·
    3 years 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?

    • qaz@lemmy.worldOP
      2·
      3 years 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.