0 Members and 1 Guest are viewing this topic.
I will retry v5.8 and/or other distros and see if it changes something.
Ideally, you would use USB3 drive (legit USB3 speeds) in a full speed USB 3 port.
linux ~ systemd-analyze blame4min 41.327s systemd-tmpfiles-clean.service4min 24.085s ua-timer.service2min 40.984s networking.service1min 37.879s gpu-manager.service1min 35.142s blueman-mechanism.service1min 30.997s networkd-dispatcher.service1min 30.235s nmbd.service1min 29.378s polkit.service1min 25.028s avahi-daemon.service1min 24.980s bluetooth.service1min 24.681s thermald.service1min 24.680s systemd-logind.service1min 24.399s wpa_supplicant.service 53.798s resolvconf-pull-resolved.service 48.431s systemd-journald.service 42.951s rsyslog.service 30.083s secureboot-db.service 22.869s lm-sensors.service 20.079s WolfLandBuilder-firstboot.service 19.186s packagekit.service 16.389s update-notifier-download.service 15.435s rc-local.service 14.815s ModemManager.service
graphical.target @4min 28.131s└─multi-user.target @4min 28.131s └─smbd.service @4min 27.181s +949ms └─network-online.target @2min 56.938s └─network.target @2min 56.938s └─NetworkManager.service @1min 51.675s +8.277s └─dbus.service @16.478s └─basic.target @16.421s └─sockets.target @16.421s └─uuidd.socket @16.421s └─sysinit.target @16.182s └─systemd-update-utmp.service @16.107s +5ms └─systemd-tmpfiles-setup.service @15.932s +172ms └─local-fs.target @15.857s └─run-user-990-gvfs.mount @3min 12.451s └─run-user-990.mount @2min 57.107s └─local-fs-pre.target @11.914s └─systemd-tmpfiles-setup-dev.service @11.738s +> └─systemd-sysusers.service @2.849s +8.887s └─systemd-remount-fs.service @2.763s +73ms
linux ~ systemd-analyze blame6min 20.360s networking.service3min 20.178s rc-local.service1min 55.957s gpu-manager.service1min 35.868s nmbd.service1min 33.907s blueman-mechanism.service1min 30.049s smbd.service1min 28.598s networkd-dispatcher.service1min 16.578s systemd-resolved.service1min 10.434s NetworkManager.service 53.107s rsyslog.service 47.916s packagekit.service 45.693s update-notifier-download.service 35.826s bluetooth.service 32.628s secureboot-db.service 32.242s systemd-udev-settle.service 31.989s dev-sda4.device 31.712s cups.service 31.026s dev-loop0.device 29.983s systemd-journal-flush.service 29.139s NetworkManager-wait-online.service 28.943s WolfLandBuilder-firstboot.service 28.567s alsa-restore.service 28.560s casper-md5check.service
linux ~ 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.graphical.target @10min 16.217s└─multi-user.target @10min 16.217s └─plymouth-quit-wait.service @10min 16.216s +1ms └─rc-local.service @6min 56.037s +3min 20.178s └─network-online.target @6min 56.031s └─network.target @6min 56.031s └─wpa_supplicant.service @4min 5.645s +2ms └─dbus.service @1min 10.133s └─basic.target @1min 7.212s └─sockets.target @1min 7.212s └─uuidd.socket @1min 7.212s └─sysinit.target @1min 5.702s └─systemd-journald.service @9min 53.578s +16.198s └─systemd-journald.socket @1.309s └─-.mount @1.298s └─-.slice @1.298s