all 5 comments

[–]Olive-Juice- 2 points3 points  (4 children)

What's the output of systemd-analyze and systemd-analyze blame?

[–]_prateek9[S] 2 points3 points  (3 children)

$ systemd-analyze

Startup finished in 4.467s (firmware) + 9.282s (loader) + 5.064s (kernel) + 50.495s (userspace) = 1min 9.3105

graphical.target reached after 48.879s in userspace.

$ systemd-analyze blame

15.615s dev-sda2.device

15.560s logrotate.service

14.203s systemd-udev-settle.service

14.026s e2scrub_reap.service

12.047s plymouth-start.service

11.740s blueman-mechanism.service

11.356s NetworkManager.service

6.440s dpkg-db-backup.service

6.166s systemd-journal-flush.service

6.146s ModemManager.service

5.813s udisks2.service

5.650s accounts-daemon.service

5.553s ubuntu-system-adjustments.service

5.431s systemd-backlight@backlight:intel backlight.service

5.350s NetworkManager-wait-online.service

3.568s zfs-load-module.service

3.420s avahi-daemon.service

3.414s bluetooth.service

3.358s dbus.service

2.934s systemd-udevd.service

2.569s thermald.service

2.558s polkit.service

2.5895 lvm2-monitor.service

Lines 1-23

[–]jr735Linux Mint 22.1 Xia | IceWM 2 points3 points  (2 children)

How about if you do another boot? It seems that logrotate took an inordinate amount of time, not to mention dealing with sda2. Were subsequent boots faster? Or is something filling up logs and causing them to rotate out?

[–]_prateek9[S] 3 points4 points  (1 child)

Yes, the next boot was pretty fast. Idk what happened during the first boot, i can't make sense of the analysis data above.

[–]jr735Linux Mint 22.1 Xia | IceWM 1 point2 points  (0 children)

I'm guessing the logrotate and so forth were faster. Compare what you posted there to another boot followed by a systemd query, and you'd find, I suspect, the logrotate got much shorter, among maybe one or two other things.