why ubuntu18 boot so slow












0














1. I use systemd-analyze
Then show:



Startup finished in 5.230s (kernel) + 41.936s (userspace) = 47.167s
graphical.target reached after 41.449s in userspace


2. Use systemd-analyze blame
Then show :



15.778s systemd-journal-flush.service
13.473s snapd.service
12.787s dev-sdb3.device
11.612s networkd-dispatcher.service
9.636s udisks2.service
8.236s networking.service
7.422s ModemManager.service
7.382s accounts-daemon.service
7.295s apparmor.service
6.211s NetworkManager-wait-online.service
6.078s dev-loop5.device
5.674s grub-common.service
5.256s dev-loop3.device
5.036s NetworkManager.service
4.668s dev-loop6.device
4.612s avahi-daemon.service
4.611s systemd-logind.service
4.593s dev-loop4.device
4.571s pppd-dns.service
4.569s rsyslog.service
4.531s gpu-manager.service
4.413s dev-loop0.device
4.406s dev-loop2.device
4.028s dev-loop1.device
3.224s wpa_supplicant.service
2.854s thermald.service
2.802s snapd.socket
2.742s systemd-tmpfiles-setup.service
2.649s systemd-udevd.service
2.489s polkit.service
2.197s user@121.service
2.147s gdm.service
1.839s bluetooth.service
1.637s keyboard-setup.service
1.567s systemd-modules-load.service
1.566s upower.service
1.518s apport.service
1.441s systemd-rfkill.service
1.114s fwupd.service
868ms dns-clean.service


3. Use systemd-analyze critical-chain



Then show:



 graphical.target @41.449s  
└─multi-user.target @41.449s
└─kerneloops.service @41.075s +373ms
└─network-online.target @41.006s
└─NetworkManager-wait-online.service @34.794s +6.211s
└─NetworkManager.service @29.757s +5.036s
└─dbus.service @25.532s
└─basic.target @25.142s
└─sockets.target @25.142s
└─snapd.socket @22.339s +2.802s
└─sysinit.target @22.240s
└─apparmor.service @14.945s +7.295s
└─local-fs.target @14.942s
└─run-user-121.mount @39.642s
└─local-fs-pre.target @3.743s
└─keyboard-setup.service @2.106s +1.637s
└─systemd-journald.socket @2.104s
└─system.slice @2.104s
└─-.slice @2.090s


How to resolve it?










share|improve this question









New contributor




singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • What are the specifications of your system? This determines the start-up time. For instance, I have a laptop with a slow hard disk and a desktop machine with a fast SSD. The laptop takes 60s to boot into Lubuntu and the desktop machine only 15s.
    – NZD
    2 days ago










  • laptop i7 128ssd 1T sata, nvidia 1050TI 16GB ram.
    – singking cho
    2 days ago






  • 5




    Possible duplicate of Ubuntu 18.04 is slow to boot, 53 seconds to reach multi-user target
    – Hamza Saeed
    2 days ago










  • Is ubuntu installed to the ssd or to the hdd? If it's on the hdd, the boot time is pretty normal
    – pim
    2 days ago
















0














1. I use systemd-analyze
Then show:



Startup finished in 5.230s (kernel) + 41.936s (userspace) = 47.167s
graphical.target reached after 41.449s in userspace


2. Use systemd-analyze blame
Then show :



15.778s systemd-journal-flush.service
13.473s snapd.service
12.787s dev-sdb3.device
11.612s networkd-dispatcher.service
9.636s udisks2.service
8.236s networking.service
7.422s ModemManager.service
7.382s accounts-daemon.service
7.295s apparmor.service
6.211s NetworkManager-wait-online.service
6.078s dev-loop5.device
5.674s grub-common.service
5.256s dev-loop3.device
5.036s NetworkManager.service
4.668s dev-loop6.device
4.612s avahi-daemon.service
4.611s systemd-logind.service
4.593s dev-loop4.device
4.571s pppd-dns.service
4.569s rsyslog.service
4.531s gpu-manager.service
4.413s dev-loop0.device
4.406s dev-loop2.device
4.028s dev-loop1.device
3.224s wpa_supplicant.service
2.854s thermald.service
2.802s snapd.socket
2.742s systemd-tmpfiles-setup.service
2.649s systemd-udevd.service
2.489s polkit.service
2.197s user@121.service
2.147s gdm.service
1.839s bluetooth.service
1.637s keyboard-setup.service
1.567s systemd-modules-load.service
1.566s upower.service
1.518s apport.service
1.441s systemd-rfkill.service
1.114s fwupd.service
868ms dns-clean.service


3. Use systemd-analyze critical-chain



Then show:



 graphical.target @41.449s  
└─multi-user.target @41.449s
└─kerneloops.service @41.075s +373ms
└─network-online.target @41.006s
└─NetworkManager-wait-online.service @34.794s +6.211s
└─NetworkManager.service @29.757s +5.036s
└─dbus.service @25.532s
└─basic.target @25.142s
└─sockets.target @25.142s
└─snapd.socket @22.339s +2.802s
└─sysinit.target @22.240s
└─apparmor.service @14.945s +7.295s
└─local-fs.target @14.942s
└─run-user-121.mount @39.642s
└─local-fs-pre.target @3.743s
└─keyboard-setup.service @2.106s +1.637s
└─systemd-journald.socket @2.104s
└─system.slice @2.104s
└─-.slice @2.090s


How to resolve it?










share|improve this question









New contributor




singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • What are the specifications of your system? This determines the start-up time. For instance, I have a laptop with a slow hard disk and a desktop machine with a fast SSD. The laptop takes 60s to boot into Lubuntu and the desktop machine only 15s.
    – NZD
    2 days ago










  • laptop i7 128ssd 1T sata, nvidia 1050TI 16GB ram.
    – singking cho
    2 days ago






  • 5




    Possible duplicate of Ubuntu 18.04 is slow to boot, 53 seconds to reach multi-user target
    – Hamza Saeed
    2 days ago










  • Is ubuntu installed to the ssd or to the hdd? If it's on the hdd, the boot time is pretty normal
    – pim
    2 days ago














0












0








0


1





1. I use systemd-analyze
Then show:



Startup finished in 5.230s (kernel) + 41.936s (userspace) = 47.167s
graphical.target reached after 41.449s in userspace


2. Use systemd-analyze blame
Then show :



15.778s systemd-journal-flush.service
13.473s snapd.service
12.787s dev-sdb3.device
11.612s networkd-dispatcher.service
9.636s udisks2.service
8.236s networking.service
7.422s ModemManager.service
7.382s accounts-daemon.service
7.295s apparmor.service
6.211s NetworkManager-wait-online.service
6.078s dev-loop5.device
5.674s grub-common.service
5.256s dev-loop3.device
5.036s NetworkManager.service
4.668s dev-loop6.device
4.612s avahi-daemon.service
4.611s systemd-logind.service
4.593s dev-loop4.device
4.571s pppd-dns.service
4.569s rsyslog.service
4.531s gpu-manager.service
4.413s dev-loop0.device
4.406s dev-loop2.device
4.028s dev-loop1.device
3.224s wpa_supplicant.service
2.854s thermald.service
2.802s snapd.socket
2.742s systemd-tmpfiles-setup.service
2.649s systemd-udevd.service
2.489s polkit.service
2.197s user@121.service
2.147s gdm.service
1.839s bluetooth.service
1.637s keyboard-setup.service
1.567s systemd-modules-load.service
1.566s upower.service
1.518s apport.service
1.441s systemd-rfkill.service
1.114s fwupd.service
868ms dns-clean.service


3. Use systemd-analyze critical-chain



Then show:



 graphical.target @41.449s  
└─multi-user.target @41.449s
└─kerneloops.service @41.075s +373ms
└─network-online.target @41.006s
└─NetworkManager-wait-online.service @34.794s +6.211s
└─NetworkManager.service @29.757s +5.036s
└─dbus.service @25.532s
└─basic.target @25.142s
└─sockets.target @25.142s
└─snapd.socket @22.339s +2.802s
└─sysinit.target @22.240s
└─apparmor.service @14.945s +7.295s
└─local-fs.target @14.942s
└─run-user-121.mount @39.642s
└─local-fs-pre.target @3.743s
└─keyboard-setup.service @2.106s +1.637s
└─systemd-journald.socket @2.104s
└─system.slice @2.104s
└─-.slice @2.090s


How to resolve it?










share|improve this question









New contributor




singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











1. I use systemd-analyze
Then show:



Startup finished in 5.230s (kernel) + 41.936s (userspace) = 47.167s
graphical.target reached after 41.449s in userspace


2. Use systemd-analyze blame
Then show :



15.778s systemd-journal-flush.service
13.473s snapd.service
12.787s dev-sdb3.device
11.612s networkd-dispatcher.service
9.636s udisks2.service
8.236s networking.service
7.422s ModemManager.service
7.382s accounts-daemon.service
7.295s apparmor.service
6.211s NetworkManager-wait-online.service
6.078s dev-loop5.device
5.674s grub-common.service
5.256s dev-loop3.device
5.036s NetworkManager.service
4.668s dev-loop6.device
4.612s avahi-daemon.service
4.611s systemd-logind.service
4.593s dev-loop4.device
4.571s pppd-dns.service
4.569s rsyslog.service
4.531s gpu-manager.service
4.413s dev-loop0.device
4.406s dev-loop2.device
4.028s dev-loop1.device
3.224s wpa_supplicant.service
2.854s thermald.service
2.802s snapd.socket
2.742s systemd-tmpfiles-setup.service
2.649s systemd-udevd.service
2.489s polkit.service
2.197s user@121.service
2.147s gdm.service
1.839s bluetooth.service
1.637s keyboard-setup.service
1.567s systemd-modules-load.service
1.566s upower.service
1.518s apport.service
1.441s systemd-rfkill.service
1.114s fwupd.service
868ms dns-clean.service


3. Use systemd-analyze critical-chain



Then show:



 graphical.target @41.449s  
└─multi-user.target @41.449s
└─kerneloops.service @41.075s +373ms
└─network-online.target @41.006s
└─NetworkManager-wait-online.service @34.794s +6.211s
└─NetworkManager.service @29.757s +5.036s
└─dbus.service @25.532s
└─basic.target @25.142s
└─sockets.target @25.142s
└─snapd.socket @22.339s +2.802s
└─sysinit.target @22.240s
└─apparmor.service @14.945s +7.295s
└─local-fs.target @14.942s
└─run-user-121.mount @39.642s
└─local-fs-pre.target @3.743s
└─keyboard-setup.service @2.106s +1.637s
└─systemd-journald.socket @2.104s
└─system.slice @2.104s
└─-.slice @2.090s


How to resolve it?







boot-time






share|improve this question









New contributor




singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 days ago









karel

57.5k12128146




57.5k12128146






New contributor




singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









singking chosingking cho

11




11




New contributor




singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






singking cho is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • What are the specifications of your system? This determines the start-up time. For instance, I have a laptop with a slow hard disk and a desktop machine with a fast SSD. The laptop takes 60s to boot into Lubuntu and the desktop machine only 15s.
    – NZD
    2 days ago










  • laptop i7 128ssd 1T sata, nvidia 1050TI 16GB ram.
    – singking cho
    2 days ago






  • 5




    Possible duplicate of Ubuntu 18.04 is slow to boot, 53 seconds to reach multi-user target
    – Hamza Saeed
    2 days ago










  • Is ubuntu installed to the ssd or to the hdd? If it's on the hdd, the boot time is pretty normal
    – pim
    2 days ago


















  • What are the specifications of your system? This determines the start-up time. For instance, I have a laptop with a slow hard disk and a desktop machine with a fast SSD. The laptop takes 60s to boot into Lubuntu and the desktop machine only 15s.
    – NZD
    2 days ago










  • laptop i7 128ssd 1T sata, nvidia 1050TI 16GB ram.
    – singking cho
    2 days ago






  • 5




    Possible duplicate of Ubuntu 18.04 is slow to boot, 53 seconds to reach multi-user target
    – Hamza Saeed
    2 days ago










  • Is ubuntu installed to the ssd or to the hdd? If it's on the hdd, the boot time is pretty normal
    – pim
    2 days ago
















What are the specifications of your system? This determines the start-up time. For instance, I have a laptop with a slow hard disk and a desktop machine with a fast SSD. The laptop takes 60s to boot into Lubuntu and the desktop machine only 15s.
– NZD
2 days ago




What are the specifications of your system? This determines the start-up time. For instance, I have a laptop with a slow hard disk and a desktop machine with a fast SSD. The laptop takes 60s to boot into Lubuntu and the desktop machine only 15s.
– NZD
2 days ago












laptop i7 128ssd 1T sata, nvidia 1050TI 16GB ram.
– singking cho
2 days ago




laptop i7 128ssd 1T sata, nvidia 1050TI 16GB ram.
– singking cho
2 days ago




5




5




Possible duplicate of Ubuntu 18.04 is slow to boot, 53 seconds to reach multi-user target
– Hamza Saeed
2 days ago




Possible duplicate of Ubuntu 18.04 is slow to boot, 53 seconds to reach multi-user target
– Hamza Saeed
2 days ago












Is ubuntu installed to the ssd or to the hdd? If it's on the hdd, the boot time is pretty normal
– pim
2 days ago




Is ubuntu installed to the ssd or to the hdd? If it's on the hdd, the boot time is pretty normal
– pim
2 days ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






singking cho is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107081%2fwhy-ubuntu18-boot-so-slow%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








singking cho is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















singking cho is a new contributor. Be nice, and check out our Code of Conduct.













singking cho is a new contributor. Be nice, and check out our Code of Conduct.












singking cho is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107081%2fwhy-ubuntu18-boot-so-slow%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

第一次世界大戦

Touch on Surface Book