My Kubuntu 20.04 boot time is taking 4 minutes, which is a lot. For what I browsed I think it could have something to do with partition scanning but I know nothing about that.
Can someone please check what is holding up the process?
Here's the output of journalctl -b: https://pastebin.com/raw/X9ZESMJK
Here's the output of systemd-analyze blame: https://pastebin.com/raw/yMtr89R5
The output of: systemd-analyze:
The output of systemd-analyze critical-chain:
Can someone please check what is holding up the process?
Here's the output of journalctl -b: https://pastebin.com/raw/X9ZESMJK
Here's the output of systemd-analyze blame: https://pastebin.com/raw/yMtr89R5
The output of: systemd-analyze:
Code:
$ systemd-analyze Startup finished in 5.327s (firmware) + 5.848s (loader) + 42.474s (kernel) + 1min 46.569s (userspace) = 2min 40.218s graphical.target reached after 1min 46.528s in userspace
Code:
$ 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 @1min 46.528s └─udisks2.service @1min 34.978s +11.549s └─basic.target @1min 33.815s └─sockets.target @1min 33.815s └─uuidd.socket @1min 33.815s └─sysinit.target @1min 33.727s └─systemd-timesyncd.service @21.984s +430ms └─systemd-tmpfiles-setup.service @21.058s +866ms └─local-fs.target @21.029s └─boot-efi.mount @20.814s +214ms └─systemd-fsck@dev-disk-by\x2duuid-9298\x2d7296.service @18.834s +1.949s └─dev-disk-by\x2duuid-9298\x2d7296.device @18.831s
Comment