Results 1 to 6 of 6

Thread: Ubuntu 20.04 takes long time to boot

  1. #1
    Join Date
    Nov 2020
    Beans
    3

    Ubuntu 20.04 takes long time to boot

    Hello guys, I'm new using Ubuntu, and I have a problem.
    I did an upgrade from Ubuntu 18.04 to Ubuntu 20.04, but the problem is that Ubuntu takes long time to boot.
    Could you help me, please?


    My computer has 6Gb of Ram Memory, and I've attached some screenshots to show you my laptop's resources.

    Best regards.

  2. #2
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    22,161
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Ubuntu 20.04 takes long time to boot

    A core i5-2450 isn't exactly fast. I have one.

    Also, please don't post images for text output. Just copy/paste the text and post that.

    By default, Ubuntu installs and sets up everything you might want whether you want it or not. You have to decide what you need. We can't do that for you. I see you have a bunch of snaps installed. Those are known to drastically slow booting. Many will have non-snap package versions available which you may want to consider.

    Also, probably want to see the systemd-analyze critical-chain output more than the "blame" output.
    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 @8.925s
    └─multi-user.target @8.924s
      └─postfix.service @8.916s +5ms
        └─postfix@-.service @3.463s +5.451s
          └─basic.target @3.243s
            └─sockets.target @3.243s
              └─snapd.socket @3.241s +1ms
                └─sysinit.target @3.235s
                  └─systemd-timesyncd.service @2.928s +307ms
                    └─systemd-tmpfiles-setup.service @2.692s +233ms
                      └─local-fs.target @2.672s
                        └─run-user-1000.mount @5.010s
                          └─swap.target @2.302s
                            └─dev-vgubuntu\x2dmate-swap_1.swap @2.278s +23ms
                              └─dev-dm\x2d1.device @2.276s
    Here's mind. I disable many things that aren't needed.
    Code:
    $ systemd-analyze blame 
    5.451s postfix@-.service                                    
    2.273s x2goserver.service                                   
    1.998s networkd-dispatcher.service                          
    1.891s snapd.service                                        
    1.724s dev-mapper-vgubuntu\x2d\x2dmate\x2droot.device       
    1.718s accounts-daemon.service                              
    1.705s udisks2.service                                      
    1.457s avahi-daemon.service                                 
    1.173s systemd-logind.service                               
    1.142s thermald.service                                     
    1.096s dev-loop0.device                                     
    1.081s dev-loop2.device                                     
    1.075s dev-loop1.device                                     
    1.001s lightdm.service                                      
     989ms dev-loop4.device                                     
     972ms dev-loop3.device                                     
     969ms plymouth-quit-wait.service
    See all those dev-loop.... lines? Those are snaps, but they don't show up in the critical path, so they don't slow down the actual boot. I'm not sure what accounts-daemon.service does. There was a critical flaw in that a few weeks ago. I have no idea what that actually does and don't think it is needed. Same for thermald. I've masked thermald so it won't run anymore. I know avahi isn't needed, but it is really handy for locating printers on the subnet.

    If you set a static IP address using config files, then network-manager won't be needed and the slowness of NM stuff won't exist. But if you want point-n-click network control, then disabling network manager wouldn't be a good idea.

    If you want a faster system, choose a lighter desktop like XFCE and avoid Gnome3.

  3. #3
    Join Date
    Nov 2020
    Beans
    3

    Re: Ubuntu 20.04 takes long time to boot

    Code:
    carlos@Salmeron:~$ 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 @2min 1.444s
    └─multi-user.target @2min 1.444s
      └─snapd.seeded.service @39.955s +26.322s
        └─snapd.service @41.819s +22.949s
          └─basic.target @38.444s
            └─sockets.target @38.444s
              └─snapd.socket @38.442s +1ms
                └─sysinit.target @38.374s
                  └─swap.target @38.374s
                    └─dev-disk-by\x2duuid-cf5ae7b8\x2d5f15\x2d4eb4\x2d8f72\x2dd8488>
                      └─dev-sda5.device @38.170s
    Last edited by ajgreeny; November 28th, 2020 at 04:26 PM. Reason: Code tags

  4. #4
    Join Date
    Nov 2008
    Location
    Metro Boston
    Beans
    15,494
    Distro
    Kubuntu 20.04 Focal Fossa

    Re: Ubuntu 20.04 takes long time to boot

    Replacing the boot drive with an SSD can greatly improve boot times. Newegg runs sales on SSD drives all the time. I upgraded two laptops with these: https://www.newegg.com/western-digit...82E16820250087
    If you ask for help, do not abandon your request. Please have the courtesy to check for responses and thank the people who helped you.

    Blog · Linode System Administration Guides · Android Apps for Ubuntu Users

  5. #5
    Join Date
    Nov 2020
    Beans
    3

    Re: Improving Ubuntu boot time

    My case
    Code:
    graphical.target @1min 55.888s└─multi-user.target @1min 55.888s
      └─teamviewerd.service @50.917s +12.091s
        └─network-online.target @50.778s
          └─network.target @50.777s
            └─NetworkManager.service @38.379s +12.397s
              └─dbus.service @38.374s
                └─basic.target @38.007s
                  └─sockets.target @38.007s
                    └─uuidd.socket @38.007s
                      └─sysinit.target @37.901s
                        └─swap.target @37.901s
                          └─dev-disk-by\x2duuid-cf5ae7b8\x2d5f15\x2d4eb4\x2d8f72\x2>
                            └─dev-disk-by\x2duuid-cf5ae7b8\x2d5f15\x2d4eb4\x2d8f72\>
    Last edited by ajgreeny; November 28th, 2020 at 04:28 PM. Reason: Code tags

  6. #6
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    22,161
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Improving Ubuntu boot time

    Please use "code tags." https://ubuntuforums.org/misc.php?do=bbcode#code explains how.

    Looks like NetworkManager and teamviewerd are problems that you can avoid.
    a) use a static IP, configured in the netplan config directory - i.e. don't use network manager.
    b) only start teamviewer when you actually need it. Certainly that isn't more than once a month, if not less.
    Last edited by TheFu; November 28th, 2020 at 03:13 PM.

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
  •