Results 1 to 3 of 3

Thread: Slow boot help needed

  1. #1
    Join Date
    May 2018
    Beans
    3

    Slow boot help needed

    Hi, I am new to Ubuntu. I have installed Ubuntu 4 times but every time i get slow boot while startup i learned some commands which shows the problem but i don't know what to do next. Please help me. this are all details that can help.

    I have only Ubuntu so during installation i have selected something else and manually partitioned my 1TB hard disk. I have partitioned disk by following https://askubuntu.com/questions/3432...g-installation guide.

    My partition are as follow -->

    Name Size Type of Partition Location of Partition Use As Mount Point
    EFI
    /dev/sda1
    536 MB Primary Beginning of space EFI system
    Swap Space
    /dev/sda2
    20 GB Primary Beginning of space Swap Area
    Partition 3
    /dev/sda3
    50 GB Logical Beginning of space Ext4 / (root)
    Partition 4
    /dev/sda4
    2 GB Logical Beginning of space Ext4 /boot
    Partition 5
    /dev/sda5
    12 GB Logical Beginning of space Ext4 /var
    Partition 6
    /dev/sda6
    12 GB Logical Beginning of space Ext4 /tmp
    Partition 7
    /dev/sda7
    900 GB Logical Beginning of space Ext4 /home
    Free Space
    /dev/sda
    4 GB

    After running "systemd-analyze" -->

    Code:
    Startup finished in 4.854s (firmware) + 4.174s (loader) + 4.555s (kernel) + 48.579s (userspace) = 1min 2.163s
    graphical.target reached after 48.464s in userspace
    and after running "systemd-analyze blame" -->

    Code:
    27.105s plymouth-start.service
             13.431s plymouth-read-write.service
             11.924s plymouth-quit-wait.service
             10.468s NetworkManager-wait-online.service
              7.046s dev-sda3.device
              6.744s systemd-journal-flush.service
              5.974s systemd-rfkill.service
              5.784s systemd-backlight@backlight:intel_backlight.service
              5.554s home.mount
              5.342s snap-gnome\x2dcalculator-154.mount
              5.285s snap-gnome\x2dlogs-25.mount
              4.965s ModemManager.service
              4.887s snap-gnome\x2dsystem\x2dmonitor-39.mount
              4.732s snapd.service
              4.691s snap-gnome\x2dsystem\x2dmonitor-36.mount
              4.659s snap-canonical\x2dlivepatch-39.mount
              4.439s snap-gnome\x2dcharacters-69.mount
              4.380s snap-core-4486.mount
              4.360s udisks2.service
              4.350s snap-gnome\x2dlogs-31.mount
              4.290s snap-gnome\x2dcharacters-86.mount
              4.250s snap-gnome\x2d3\x2d26\x2d1604-59.mount
              4.217s snap-gnome\x2d3\x2d26\x2d1604-64.mount
              4.199s snap-core-4571.mount
              4.159s NetworkManager.service
              4.143s snap-gnome\x2dcalculator-167.mount
              3.950s accounts-daemon.service
              3.583s apparmor.service
              3.431s networkd-dispatcher.service
              2.415s systemd-fsck@dev-disk-by\x2duuid-92ce21be\x2d0ee9\x2d475a\x2dad
              2.091s grub-common.service
              2.061s systemd-fsck@dev-disk-by\x2duuid-4e777e4a\x2dc890\x2d4c09\x2dbe
              2.044s dev-loop10.device
              1.996s dev-loop8.device
              1.958s dev-loop9.device
              1.911s wpa_supplicant.service
              1.902s dev-loop11.device
              1.650s thermald.service
              1.615s systemd-fsck@dev-disk-by\x2duuid-45AE\x2dAE7F.service
              1.603s systemd-fsck@dev-disk-by\x2duuid-2f5dcd51\x2d81da\x2d42d6\x2d8f
              1.597s dev-loop3.device
              1.575s dev-loop0.device
              1.540s polkit.service
              1.491s dev-loop6.device
              1.406s dev-loop4.device
              1.360s systemd-fsck@dev-disk-by\x2duuid-918cbf63\x2d7418\x2d4780\x2d9f
              1.359s speech-dispatcher.service
              1.296s bluetooth.service
              1.280s lvm2-monitor.service
              1.252s dev-loop7.device
              1.216s dev-loop5.device
              1.191s rsyslog.service
              1.108s fwupd.service
              1.067s keyboard-setup.service
              1.021s dev-loop2.device
               904ms dev-loop12.device
               831ms dev-loop1.device
               823ms avahi-daemon.service
               818ms systemd-logind.service
               813ms pppd-dns.service
               808ms gpu-manager.service
               741ms tmp.mount
               697ms alsa-restore.service
               670ms systemd-sysctl.service
               659ms systemd-modules-load.service
               654ms systemd-udevd.service
               613ms apport.service
               606ms systemd-remount-fs.service
               586ms systemd-tmpfiles-setup.service
               572ms packagekit.service
               537ms dev-mqueue.mount
               536ms dev-hugepages.mount
               534ms sys-kernel-debug.mount
               522ms dns-clean.service
               483ms systemd-tmpfiles-setup-dev.service
               390ms var.mount
               387ms systemd-timesyncd.service
               367ms colord.service
               344ms systemd-resolved.service
               267ms kmod-static-nodes.service
               266ms gdm.service
               260ms user@120.service
               220ms boot.mount
               217ms upower.service
               217ms networking.service
               216ms boot-efi.mount
               213ms console-setup.service
               201ms snapd.seeded.service
               177ms systemd-update-utmp.service
               172ms systemd-random-seed.service
               157ms bolt.service
               142ms kerneloops.service
               122ms dev-disk-by\x2duuid-a2d9decd\x2dde65\x2d4d63\x2d9e29\x2d58dcc03
               117ms systemd-user-sessions.service
               115ms systemd-udev-trigger.service
               108ms setvtrgb.service
                84ms blk-availability.service
                79ms systemd-journald.service
                75ms ufw.service
                56ms user@1000.service
                28ms rtkit-daemon.service
                15ms systemd-update-utmp-runlevel.service
                 8ms ureadahead-stop.service
                 2ms sys-fs-fuse-connections.mount
                 2ms sys-kernel-config.mount
               808us snapd.socket
    lines 84-106/106 (END)
    [1]+  Stopped                 systemd-analyze blame
    and after running "systemd-analyze critical-chain"

    Code:
    The time after the unit is active or started is printed after the "@" character.
    The time the unit takes to start is printed after the "+" character.
    
    graphical.target @48.464s
    └─multi-user.target @48.464s
      └─kerneloops.service @46.937s +142ms
        └─network-online.target @46.886s
          └─NetworkManager-wait-online.service @36.418s +10.468s
            └─NetworkManager.service @32.257s +4.159s
              └─dbus.service @31.482s
                └─basic.target @31.472s
                  └─sockets.target @31.472s
                    └─snapd.socket @31.470s +808us
                      └─sysinit.target @31.429s
                        └─cryptsetup.target @31.153s
                          └─systemd-ask-password-wall.path @2.637s
                            └─-.mount @2.635s
                              └─system.slice @2.637s
                                └─-.slice @2.635s
    after running "sudo blkid"

    Code:
    /dev/loop0: TYPE="squashfs"
    /dev/loop1: TYPE="squashfs"
    /dev/loop2: TYPE="squashfs"
    /dev/loop3: TYPE="squashfs"
    /dev/loop4: TYPE="squashfs"
    /dev/loop5: TYPE="squashfs"
    /dev/loop6: TYPE="squashfs"
    /dev/loop7: TYPE="squashfs"
    /dev/sda1: UUID="45AE-AE7F" TYPE="vfat" PARTUUID="8290266c-b7b9-485f-8ff7-523d5f2a5ec5"
    /dev/sda2: UUID="a2d9decd-de65-4d63-9e29-58dcc03a58bc" TYPE="swap" PARTUUID="69911122-bf4a-4b73-ac7e-e626314c7974"
    /dev/sda3: UUID="3b3668ad-8088-4572-b297-679b81652f5c" TYPE="ext4" PARTUUID="8ebc233b-c431-449a-8800-d17f0ea2c2dc"
    /dev/sda4: UUID="918cbf63-7418-4780-9f04-06f47fb69779" TYPE="ext4" PARTUUID="ae11acfd-17bc-47bd-be3a-415bfab35899"
    /dev/sda5: UUID="4e777e4a-c890-4c09-be1e-39388461b330" TYPE="ext4" PARTUUID="abefd938-0912-4724-ae71-3ee214f7b77b"
    /dev/sda6: UUID="2f5dcd51-81da-42d6-8fa1-6ea6bd0df0bf" TYPE="ext4" PARTUUID="edd8c8cc-d226-46b1-9b3f-55b467182ea0"
    /dev/sda7: UUID="92ce21be-0ee9-475a-ad7b-ccd6d06934db" TYPE="ext4" PARTUUID="5981f509-60ae-4ba6-b102-2a2c11a6d6c9"
    /dev/loop8: TYPE="squashfs"
    /dev/loop9: TYPE="squashfs"
    /dev/loop10: TYPE="squashfs"
    /dev/loop11: TYPE="squashfs"
    /dev/loop12: TYPE="squashfs"
    /dev/loop13: TYPE="squashfs"
    After running "lsblk" -->
    Code:
      NAME   MAJ:MIN  RM   SIZE         RO       TYPE     MOUNTPOINT
    loop0    7:0                0      12.2M        1          loop       /snap/gnome-characters/69
    loop1    7:1                0      86.6M        1          loop       /snap/core/4650
    loop2    7:2                0      21M           1          loop       /snap/gnome-logs/25
    loop3    7:3                0      3.3M          1          loop      /snap/gnome-system-monitor/36
    loop4    7:4                0    1.6M             1          loop      /snap/gnome-calculator/154
    loop5    7:5                0     140M          1          loop         /snap/gnome-3-26-1604/59
    loop6    7:6                0     86.6M        1           loop         /snap/core/4486
    loop7    7:7                0   2.3M            1           loop          /snap/gnome-calculator/167
    loop8    7:8                0    139.5M      1           loop         /snap/gnome-3-26-1604/64
    loop9    7:9                0      3.7M         1           loop        /snap/gnome-system-monitor/39
    loop10   7:10             0     13M           1          loop           /snap/gnome-characters/86
    loop11   7:11             0    4.9M           1          loop             /snap/canonical-livepatch/39
    loop12   7:12            0     21.6M         1           loop           /snap/gnome-logs/31
    loop13   7:13            0     86.6M           1           loop            /snap/core/4571
    sda           8:0              0    931.5G       0              disk 
    ├─sda1   8:1               0   571M           0             part           /boot/efi
    ├─sda2   8:2              0    18.6G           0            part             [SWAP]
    ├─sda3   8:3               0    46.6G         0            part                  /
    ├─sda4   8:4               0     1.9G          0            part              /boot
    ├─sda5   8:5              0    11.2G          0             part                 /var
    ├─sda6   8:6              0   11.2G           0            part               /tmp
    └─sda7   8:7              0    838.2G        0            part            /home
    sr0     11:0                   1  1024M         0             rom


    my disk image is attached with this thread. also i am runnig on 8 GB RAM and i have only Ubuntu running on laptop no other OS. Hope all of this information helps please help me to overcome this problem.
    Attached Images Attached Images
    Last edited by priyankkjain; May 23rd, 2018 at 06:35 AM.

  2. #2
    Join Date
    Jun 2006
    Location
    Nux Jam
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Slow boot help needed

    'journalctl -b' can teach you about some issues: bright line = warning, red line = error

    if 'ureadahead' is installed, then purge it (it cause more trouble than benefits) (sudo apt-get purge ureadahead)

  3. #3
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Slow boot help needed

    I appreciate all the effort formatting the post above, but just using code tags and showing the exact command/output is sufficient. No fancy formatting.

    For the disk partition data, the output from df -hT would be preferred (and much easier to post). We ***like*** text.

    On spinning HDDs, it is possible for improper layout alignment to reduce disk performance significantly. It matters on SSDs too, but not nearly as much.
    https://www.ibm.com/developerworks/l...-sector-disks/
    https://ubuntuforums.org/showthread.php?t=1889531

    BTW, your partition layout seems overly complex. Some good ideas implemented, but some seems to be based on old information that doesn't apply.
    I think the swap is 4-5x too large too. For a desktop, 4.1G for swap is the best answer for low memory systems AND systems with 32G of RAM (and everything in between), assuming you don't hibernate (and really nobody should hibernate if they care at all about security). The goal for swap is to provide feedback as system RAM gets low. The system should slow down some, enough that the users "feel it". Systems that have more swap are useful for shared resources like VM hosts if you don't like your customers much. IMHO.
    Last edited by TheFu; May 22nd, 2018 at 03:22 PM.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •