== systemd-analyze
Startup finished in 13.106s (firmware) + 12.456s (loader) + 6.002s (kernel) + 32.583s (userspace) = 1min 4.149s 
kodi.target reached after 32.582s in userspace.
== systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

kodi.target @32.582s
└─kodi.service @31.826s +752ms
  └─kodi-autostart.service @31.486s +192ms
    └─hades-diag.service @30.850s +632ms
      └─graphical.target @30.846s
        └─multi-user.target @30.845s
          └─smbd.service @30.343s +500ms
            └─nmbd.service @28.376s +1.951s
              └─network-online.target @28.362s
                └─kodi-waitonnetwork.service @6.094s +22.267s
                  └─connman.service @6.002s +82ms
                    └─dbus.service @3.983s +2.014s
                      └─basic.target @3.958s
                        └─sockets.target @3.958s
                          └─hades-bdj.socket @3.950s +6ms
                            └─sysinit.target @3.943s
                              └─systemd-udevd.service @3.744s +198ms
                                └─add-entropy.service @2.717s +1.022s
                                  └─systemd-tmpfiles-setup.service @2.410s +300ms
                                    └─local-fs.target @2.403s
                                      └─var-media-[volume-c44483].mount @5.718s
                                        └─dev-nvme0n1p4.device @5.717s +75ms
== systemd-analyze critical-chain kodi.service
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

kodi.service +752ms
└─kodi-autostart.service @31.486s +192ms
  └─hades-diag.service @30.850s +632ms
    └─graphical.target @30.846s
      └─multi-user.target @30.845s
        └─smbd.service @30.343s +500ms
          └─nmbd.service @28.376s +1.951s
            └─network-online.target @28.362s
              └─kodi-waitonnetwork.service @6.094s +22.267s
                └─connman.service @6.002s +82ms
                  └─dbus.service @3.983s +2.014s
                    └─basic.target @3.958s
                      └─sockets.target @3.958s
                        └─hades-bdj.socket @3.950s +6ms
                          └─sysinit.target @3.943s
                            └─systemd-udevd.service @3.744s +198ms
                              └─add-entropy.service @2.717s +1.022s
                                └─systemd-tmpfiles-setup.service @2.410s +300ms
                                  └─local-fs.target @2.403s
                                    └─var-media-[volume-c44483].mount @5.718s
                                      └─dev-nvme0n1p4.device @5.717s +75ms
== systemd-analyze blame
27.071s wait-time-sync.service
22.267s kodi-waitonnetwork.service
 3.414s dev-sda2.device
 3.382s dev-sda1.device
 3.242s dev-loop0.device
 2.333s iptables.service
 2.048s pulseaudio.service
 2.046s connman-vpn.service
 2.014s dbus.service
 1.951s iwd.service
 1.951s nmbd.service
 1.255s samba-config.service
 1.234s systemd-logind.service
 1.118s systemd-hwdb-update.service
 1.022s add-entropy.service
  752ms kodi.service
  632ms hades-diag.service
  605ms rpcbind.service
  534ms userconfig.service
  532ms systemd-udev-trigger.service
  522ms usercache.service
  500ms smbd.service
  499ms bluetooth.service
  460ms swap.service
  417ms envconfig.service
  409ms openssl-config.service
  369ms systemd-update-utmp.service
  368ms systemd-journalctl.socket
  300ms systemd-tmpfiles-setup.service
  287ms systemd-journal-catalog-update.service
  261ms systemd-hostnamed.service
  249ms systemd-journald.service
  248ms udevil-mount-ro@-dev-nvme0n1p1.service
  230ms udevil-mount-ro@-dev-nvme0n1p4.service
  211ms tz-data.service
  204ms systemd-journal-flush.service
  198ms systemd-udevd.service
  196ms storage-log.service
  192ms kodi-autostart.service
  187ms dev-mqueue.mount
  186ms sys-kernel-debug.mount
  184ms sys-kernel-tracing.mount
  183ms systemd-tmpfiles-setup-dev-early.service
  181ms var.mount
  178ms kmod-static-nodes.service
  176ms machine-id.service
  174ms sys-kernel-config.mount
  172ms modprobe@fuse.service
  167ms show-version.service
  160ms systemd-modules-load.service
  157ms systemd-udev-load-credentials.service
  153ms network-base.service
  139ms sshd.service
  139ms nvidia-drm-wait.service
  136ms cpufreq.service
  134ms dev-nvme0n1p1.device
  133ms cron.service
  129ms systemd-userdbd.service
  126ms hades-menu-once.service
  117ms sys-fs-fuse-connections.mount
   82ms connman.service
   79ms kodi-cleanlogs.service
   79ms systemd-timesyncd-setup.service
   75ms dev-nvme0n1p4.device
   61ms systemd-sysctl.service
   58ms systemd-tmpfiles-setup-dev.service
   45ms ledfix.service
   38ms tmp.mount
   15ms systemd-storage-fs.socket
   12ms hades-bdj-net.socket
    9ms var-log.mount
    7ms rpcbind.socket
    6ms hades-bdj.socket
    4ms systemd-sysext.socket
    2ms systemd-mute-console.socket
    1ms systemd-ask-password.socket
    1ms systemd-logind-varlink.socket
    1ms systemd-storage-block.socket
    1ms systemd-creds.socket
    1ms systemd-factory-reset.socket
  175us systemd-journald-dev-log.socket
  136us dbus.socket
  111us systemd-userdbd.socket
   95us lircd.socket
   63us systemd-udevd-varlink.socket
   60us systemd-journald.socket
   36us systemd-hostnamed.socket
   26us systemd-udevd-kernel.socket
== systemctl list-jobs (what the start still waits for)
No jobs running.
