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

  • jsdz@lemmy.ml
    link
    fedilink
    arrow-up
    97
    ·
    1 year ago

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

    • astrsk@artemis.camp
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      Combine that with the 20-30 seconds my system takes to do bios memory training on the DDR5 ram and we’re practically back to the “go make some coffee while the system boots up” days 🤦

    • magikmw@lemm.ee
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      I wish to replace it with a yubikey, but I don’t even know if it’s supported.

      • Skeletonek@lemmy.zip
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        It is, I have it set up on my laptop. It’s a bit finicky in how it works and it’s not easy to setup, but it is possible.

        • stifle867@programming.dev
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          Does it work by emulating the keyboard and typing in the password? Or by the encrypted protocol that works using the on device secret?

      • Ullebe1@lemmy.ml
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        1 year ago

        It is supported by systemd to use FIDO2 + pin to decrypt luks partitions with many security keys, including Yubikeys. I use it every day on my laptop.

      • Contend6248@feddit.de
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        You can’t even use a fucking fingerprint scanner while being in the system, that package is borked for months and nobody seem to care to solve it.

        I think using Yubikey at boot time is quite out of reach

  • passepartout@feddit.de
    link
    fedilink
    arrow-up
    94
    ·
    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
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      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
        link
        fedilink
        arrow-up
        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.

    • hare_ware@pawb.social
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      Honestly I laughed when it just spit an SVG in text at me. I was wholly expecting a GUI to appear.

    • stifle867@programming.dev
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      The top/1st line is the first service and it cascaded down as each subsequent service starts. Left to right is time elapsed. Bright red line is time to start that service. Shorter is better.

      Does that help?

    • stifle867@programming.dev
      link
      fedilink
      arrow-up
      8
      ·
      1 year 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.

    • qaz@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      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, and I actually quite like what I’ve seen so far.

  • Pantherina@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year 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)