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

  • passepartout@feddit.de
    link
    fedilink
    arrow-up
    114
    ·
    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
      8
      ·
      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.