0

Here is the result of the command systemd-analyze:

Startup finished in 5.359s (kernel) + 1min 55.199s (userspace) = 2min 559ms
graphical.target reached after 1min 53.510s in userspace

Please Let me know how could I lessen this time. I had recently(a week before) installed ubuntu 20.04 and had shifted from windows to Linux.

The output of systemd-analyze blame is

1min 15.371s plymouth-quit-wait.service
     21.162s dev-sda5.device
     20.968s snapd.service
     18.507s networkd-dispatcher.service
     16.409s NetworkManager-wait-online.service
     14.704s udisks2.service
     14.419s systemd-journal-flush.service
     13.434s dev-loop15.device
     13.030s dev-loop13.device
     13.015s dev-loop14.device
     12.317s dev-loop4.device
     12.310s dev-loop10.device
     11.607s dev-loop11.device
     11.528s dev-loop12.device
     11.273s dev-loop8.device
     11.231s dev-loop9.device
     10.697s dev-loop7.device
     10.413s accounts-daemon.service
      9.316s dev-loop2.device
      9.212s dev-loop1.device
      8.789s dev-loop6.device
      8.433s dev-loop5.device
      8.088s dev-loop3.device
      7.922s dev-loop0.device
      7.854s avahi-daemon.service
      7.841s bluetooth.service
      7.798s NetworkManager.service
      7.439s polkit.service
      7.152s systemd-resolved.service
      6.830s switcheroo-control.service
      6.797s thermald.service
      6.770s systemd-logind.service
      6.769s wpa_supplicant.service
      6.123s apport-autoreport.service
      4.622s ModemManager.service
      4.310s fwupd.service
      4.028s apport.service
      3.938s gpu-manager.service
      3.834s grub-common.service
      3.408s rsyslog.service
      3.040s systemd-udevd.service
      2.802s e2scrub_reap.service
      2.794s upower.service
      2.506s systemd-journald.service
      2.329s gdm.service
      1.977s systemd-timesyncd.service
      1.685s apparmor.service
      1.652s tlp.service
      1.646s grub-initrd-fallback.service
      1.309s systemd-sysctl.service
      1.153s systemd-tmpfiles-setup.service
       935ms systemd-modules-load.service
       931ms snapd.apparmor.service
       918ms lm-sensors.service
       834ms systemd-random-seed.service
       814ms geoclue.service
       803ms snap-canonical\x2dlivepatch-95.mount
       798ms snap-core-9436.mount
       795ms snap-core18-1705.mount
       761ms systemd-udev-trigger.service
       758ms snap-core18-1754.mount
       680ms snap-gnome\x2d3\x2d28\x2d1804-128.mount
       656ms user@1000.service
       649ms swapfile.swap
       642ms pppd-dns.service
       612ms snap-gnome\x2d3\x2d34\x2d1804-24.mount
       604ms keyboard-setup.service
       560ms snap-gnome\x2d3\x2d34\x2d1804-36.mount
       557ms systemd-sysusers.service
       518ms snap-gtk\x2dcommon\x2dthemes-1506.mount
       471ms snap-mpg123\x2dcm-21.mount
       459ms systemd-tmpfiles-setup-dev.service
       452ms snap-snap\x2dstore-433.mount
       427ms snap-snap\x2dstore-467.mount
       417ms plymouth-start.service
       381ms modprobe@drm.service
       381ms kerneloops.service
       376ms snap-snapd-7264.mount
       365ms hddtemp.service
       361ms snap-snapd-8140.mount
       315ms colord.service
       291ms dev-hugepages.mount
       288ms dev-mqueue.mount
       288ms systemd-tmpfiles-clean.service
       284ms sys-kernel-debug.mount
       281ms sys-kernel-tracing.mount
       277ms ufw.service
       265ms snapd.seeded.service
       264ms kmod-static-nodes.service
       238ms openvpn.service
       237ms snap-vlc-1700.mount
       233ms console-setup.service
       230ms snap-standard\x2dnotes-10.mount
       195ms systemd-user-sessions.service
       182ms systemd-backlight@backlight:radeon_bl0.service
       176ms snap-stellarium\x2ddaily-152.mount
       159ms systemd-fsck@dev-disk-by\x2duuid-016D\x2d2379.service
       158ms systemd-remount-fs.service
       134ms plymouth-read-write.service
       116ms user-runtime-dir@1000.service
       114ms systemd-backlight@backlight:acpi_video0.service
       110ms systemd-update-utmp.service
        77ms setvtrgb.service
        68ms rtkit-daemon.service
        65ms boot-efi.mount
        45ms systemd-update-utmp-runlevel.service
        43ms alsa-restore.service
        25ms sys-fs-fuse-connections.mount
        14ms sys-kernel-config.mount
         6ms snapd.socket

These are the images of the command systemd-analyze plot > ~/SystemdAnalyzePlot.svg:

https://i.stack.imgur.com/EXcC1.png

https://i.stack.imgur.com/ZnUKY.png

result of systemd-analyze critical-chain

graphical.target @1min 22.613s
└─multi-user.target @1min 22.611s
  └─snapd.seeded.service @49.338s +210ms
    └─snapd.service @27.294s +22.036s
      └─basic.target @26.230s
        └─sockets.target @26.230s
          └─snapd.socket @26.219s +10ms
            └─sysinit.target @25.902s
              └─systemd-timesyncd.service @23.836s +2.065s
                └─systemd-tmpfiles-setup.service @23.116s +660ms
                  └─local-fs.target @23.087s
                    └─run-snapd-ns-canonical\x2dlivepatch.mnt.mount @43.350s
                      └─run-snapd-ns.mount @39.627s
                        └─local-fs-pre.target @5.484s
                          └─systemd-tmpfiles-setup-dev.service @5.120s +363ms
                            └─systemd-sysusers.service @4.604s +513ms
                              └─systemd-remount-fs.service @4.137s +191ms
                                └─systemd-journald.socket @3.897s
                                  └─-.mount @3.866s
                                    └─system.slice @3.866s
                                      └─-.slice @3.866s
6
  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Mitch
    Jul 6 '20 at 17:08
  • Take a look at journalctl -b 0 _PID=1 -p 1..4
    – abu_bua
    Jul 6 '20 at 18:54
  • Print systemd-analyze critical-chain
    – abu_bua
    Jul 6 '20 at 20:32
  • @Nmath It was installed to an internal SSD and yes I have formatted it.
    – Achal
    Jul 7 '20 at 3:28
  • Check the log of plyouth-wait : sudo systemctl status plymouth-quit-wait.service
    – abu_bua
    Jul 7 '20 at 12:02
0
  1. sudo nano /etc/default/grub
  2. Find this line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  3. Change to GRUB_CMDLINE_LINUX_DEFAULT="quiet"
  4. sudo update-grub

Reboot

2
  • I had did this but this doesn't work. It remains the same.
    – Achal
    Jul 6 '20 at 15:27
  • Try this too please: GRUB_CMDLINE_LINUX_DEFAULT="noplymouth video=SVIDEO-1:d" Jul 6 '20 at 15:29
0

Lets first check your file system for errors.

To check the file system on your Ubuntu partition... boot to the GRUB menu > choose Advanced Options > choose Recovery mode > choose Root access and fsck -f /dev/sda5

repeat the fsck command if there were errors > type reboot

3
  • This is a Q&A site. Do not post different "answers" on the same question. You should post a single answer, eventually after having resolved it using the comments (for short clarifications) or the chat function (for extended conversations).
    – vanadium
    Jul 6 '20 at 16:58
  • My apology @vanadium Jul 6 '20 at 17:08
  • You're welcome! You could move the content of this question and combine this with your other answer. You can always notify the OP with a comment @ArijitChatterjee
    – vanadium
    Jul 6 '20 at 18:11
-1

Try running boot repair this fixes most boot problems automatically here is a link to how to install it and what it does https://help.ubuntu.com/community/Boot-Repair

2
  • What is "boot repair"? Elaborate please.
    – FedKad
    Jul 6 '20 at 18:37
  • @nochintator Consider editing this comment into your answer
    – Parto
    Jul 7 '20 at 14:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.