Really slow boot time

Discussion in 'Newbie Questions' started by Dayan, May 1, 2020.

  1. Dayan

    Dayan Thread Starter
    Expand Collapse
    New Member

    May 1, 2020
    Likes Received:
    Can anyone find what is wrong with my eOS?
    here's my log

    $cat /etc/fstab
    # /etc/fstab: static file system information.
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    # <file system> <mount point> <type> <options> <dump> <pass>
    # / was on /dev/sda7 during installation
    UUID=af4409cb-96ff-438d-81d2-7e8aaf1aad8f / ext4 errors=remount-ro 0 1
    # /boot was on /dev/sda5 during installation
    UUID=e35ecb0f-efab-405b-9e01-e35e519f664b /boot ext4 defaults 0 2
    # swap was on /dev/sda6 during installation
    UUID=acece8c5-a706-447f-b060-d7f7c2fddaba none swap sw 0 0

    /dev/sda3 /media/mpoint ntfs-3g default 0 0

    $sudo systemd-analyze blame

    8.669s dev-sda6.device
    8.127s media-mpoint.mount
    5.781s lvm2-monitor.service
    5.614s snapd.service
    4.569s keyboard-setup.service
    4.494s apt-daily.service
    2.603s networkd-dispatcher.service
    1.749s udisks2.service
    1.344s grub-common.service
    1.192s systemd-udevd.service
    1.121s accounts-daemon.service
    903ms systemd-modules-load.service
    858ms zram-config.service
    774ms NetworkManager.service
    703ms ModemManager.service
    662ms snap-core-9066.mount
    639ms snap-core-8935.mount
    639ms systemd-tmpfiles-setup-dev.service
    634ms plymouth-start.service
    589ms snap-core18-1705.mount
    573ms dev-loop6.device
    561ms gpu-manager.service
    509ms dev-loop3.device
    459ms systemd-fsck@dev-disk-by\x2duuid- e35ecb0f\x2defab\x2d405b\x2d9e01\x2de35e519f664b.service
    435ms systemd-rfkill.service
    421ms dev-loop5.device
    419ms speech-dispatcher.service
    410ms thermald.service
    390ms dev-loop4.device
    387ms systemd-backlight@backlight:intel_backlight.service
    385ms kerneloops.service
    380ms alsa-restore.service
    371ms pppd-dns.service
    366ms rsyslog.service
    336ms apparmor.service
    335ms lightdm.service
  2. adwilson99

    Expand Collapse
    Well-Known Member

    May 2, 2020
    Likes Received:
    I think long boot times are normally, something failing to load and timing out or, just simply loading too much.
    try running dmesg after boot and see if there are any errors or timeouts.

Share This Page