Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum

<SOLVED> Sparky boot time 4 minutes!

Started by Erwin, October 13, 2020, 04:42:20 PM

Previous topic - Next topic


So I have finally installed Sparky after several issues and it runs.
However there is still a problem, boot time.
From the moment GRUB start until the login it takes 4 minutes, I have no idea what is the causin problem.
Can anybody tell me where to look first?  ::)


sudo systemd-analyze
sudo systemd-analyze blame
Quote from: forum rulesWhen an issue has been resolved for you, please edit the original post to include <SOLVED> in the title. This provides a good indicator for users with a similar problem to check out the thread
Want to chat? Join #sparkylinux at [url="//"][/url]


Quote from: lami07 on October 13, 2020, 05:45:24 PM
sudo systemd-analyze
sudo systemd-analyze blame
sudo systemd-analyze
Startup finished in 37.990s (kernel) + 1min 47.177s (userspace) = 2min 25.168s reached after 1min 47.127s in userspace

sudo systemd-analyze blame
13.609s udisks2.service                     
7.367s systemd-udev-settle.service         
6.207s ModemManager.service               
5.721s dev-sda1.device                     
5.552s NetworkManager-wait-online.service 
5.480s accounts-daemon.service             
5.139s polkit.service                     
5.008s apparmor.service                   
4.682s e2scrub_reap.service               
4.456s avahi-daemon.service               
4.414s NetworkManager.service             
4.315s rtkit-daemon.service               
4.305s wpa_supplicant.service             
4.289s systemd-logind.service             
4.194s loadcpufreq.service                 
4.165s exim4.service                       
2.769s upower.service                     
2.437s ntp.service                         
2.369s systemd-journal-flush.service       
2.327s systemd-udevd.service               
2.252s rsyslog.service                     
2.060s systemd-journald.service           
1.617s keyboard-setup.service       


Some more info since udisk2.service take a long time:

systemd-analyze critical-chain udisks2.service
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.

udisks2.service +13.609s
└─ @1min 32.815s
  └─ @1min 32.815s
    └─uuidd.socket @1min 32.815s
      └─ @1min 32.775s
        └─systemd-udev-settle.service @3.975s +7.367s
          └─systemd-udev-trigger.service @3.078s +878ms
            └─systemd-udevd-kernel.socket @2.613s
              └─system.slice @1.908s
                └─-.slice @1.908s


Installed Linux Lite and everything works smooth.
Sorry Sparky, still some work to do!


Well for the future, you can still learn how to mark up code  via the # button to improve readability.   That will aid you in wherever you go in linux forums.
Search forum for "More info easier via inxi"    If requested -  no inxi, no help for you by  me.

View the most recent posts on the forum