I just finished fixing my bootloader after migrating my install over to a new ssd and hard drive (I had mistakenly tried to install GRUB). Everything seems to be working now, but my boot is taking over a minute and a half, and I can't figure out why. Here're the outputs of some commands:
Code:systemd-analyze time Startup finished in 17.576s (firmware) + 481ms (loader) + 4.865s (kernel) + 1min 33.629s (userspace) = 1min 56.552s graphical.target reached after 1min 33.614s in userspaceThat output repeats one and a half times, for some reason. And, lastly:Code:systemd-analyze blame 3.006s plymouth-quit-wait.service 1.823s NetworkManager-wait-online.service 456ms accounts-daemon.service 442ms systemd-logind.service 346ms system76-power.service 324ms networkd-dispatcher.service 297ms fwupd.service 275ms udisks2.service 260ms vmware-USBArbitrator.service 256ms dev-sdb2.device 240ms home.mount 175ms polkit.service 171ms avahi-daemon.service 170ms bluetooth.service 166ms NetworkManager.service 151ms switcheroo-control.service 148ms thermald.service 145ms wpa_supplicant.service 125ms gdm.service 123ms gpu-manager.service 115ms lvm2-monitor.service 112ms ModemManager.service 105ms user@1000.service 101ms apparmor.service 98ms upower.service 93ms systemd-udevd.service 81ms systemd-journal-flush.service 80ms rsyslog.service 74ms systemd-resolved.service 68ms dev-disk-by\x2duuid-8336a597\x2de014\x2d47aa\x2d980b\x2dd7ead594b5ee.swap 64ms systemd-timesyncd.service 64ms systemd-udev-trigger.service 61ms colord.service 57ms systemd-journald.service 57ms apport.service 53ms binfmt-support.service 47ms proc-sys-fs-binfmt_misc.mount 44ms keyboard-setup.service 40ms e2scrub_reap.service 36ms vmware.service 29ms networking.service 26ms systemd-modules-load.service 26ms geoclue.service 22ms packagekit.service 21ms systemd-tmpfiles-setup.service 20ms boot-efi.mount 16ms plymouth-start.service 15ms grub-common.service 14ms systemd-remount-fs.service 13ms setvtrgb.service 13ms systemd-sysusers.service 12ms resolvconf-pull-resolved.service 11ms plymouth-read-write.service
From my primitive understanding of the critical-chain output, the system appears to be doing nothing for 90 seconds between apparmor.service and sysinit.target. Does anyone have an idea of what could be going on here? Any help would be appreciated. Thanks!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 33.614s └─multi-user.target @1min 33.614s └─plymouth-quit-wait.service @1min 30.607s +3.006s └─systemd-user-sessions.service @1min 30.601s +4ms └─network.target @1min 30.599s └─NetworkManager.service @1min 30.433s +166ms └─dbus.service @1min 30.430s └─basic.target @1min 30.422s └─sockets.target @1min 30.422s └─uuidd.socket @1min 30.422s └─sysinit.target @1min 30.419s └─apparmor.service @892ms +101ms └─local-fs.target @892ms └─home.mount @651ms +240ms └─dev-sda1.device @651ms
Adv Reply
Bookmarks