Very slow load on Ubuntu 18.04
I am completely new to Linux so apologies in advance!
I recently installed Ubuntu 18.04 on a wiped machine and everything seems to work well except that it takes about 2 mins to boot.
Here are some details that might be useful for diagnostics (judging by other posts I've seen on similar issues).
The output of "systemd-analyze" is
Startup finished in 1min 43.839s (kernel) + 7.763s (userspace) = 1min 51.603s
graphical.target reached after 7.758s in userspace
The output of "sudo blkid" is
/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/sda: PTUUID="8f39e0f9" PTTYPE="dos"
/dev/sdb5: UUID="92b37aee-3acf-447e-b15e-2fbb8a83e9a7" TYPE="ext4" PARTUUID="7ff18de1-05"
/dev/sdb6: UUID="21d2706c-8400-44f6-ad90-79d2dfb6384f" TYPE="swap" PARTUUID="7ff18de1-06"
(the sda is an older hard-drive (not SSD) that I want to just use for backing up some files).
The content of "/etc/fstab" is
UUID=92b37aee-3acf-447e-b15e-2fbb8a83e9a7 / ext4 errors=remount-ro 0 1
UUID=21d2706c-8400-44f6-ad90-79d2dfb6384f none swap sw 0 0
Hope this helps you diagnose my problem and suggest some things to try! Many thanks!
EDIT. In response to request here is the output of "systemd-analyze blame"
6.345s NetworkManager-wait-online.service
4.481s plymouth-quit-wait.service
834ms fwupd.service
639ms dev-sdb5.device
591ms ufw.service
459ms udisks2.service
448ms NetworkManager.service
442ms plymouth-start.service
395ms networkd-dispatcher.service
392ms snapd.service
294ms accounts-daemon.service
284ms dev-loop0.device
268ms ModemManager.service
264ms apparmor.service
256ms dev-loop2.device
243ms dev-loop3.device
238ms dev-loop1.device
213ms systemd-logind.service
197ms dev-loop4.device
191ms snap-gnomex2dcalculator-180.mount
181ms dev-loop5.device
170ms systemd-timesyncd.service
166ms systemd-udevd.service
It goes on but they're all very small times (should I still list them?)
boot 18.04
asked Aug 12 '18 at 19:49
user350031user350031
1112
|
show 5 more comments
I am completely new to Linux so apologies in advance!
I recently installed Ubuntu 18.04 on a wiped machine and everything seems to work well except that it takes about 2 mins to boot.
Here are some details that might be useful for diagnostics (judging by other posts I've seen on similar issues).
The output of "systemd-analyze" is
Startup finished in 1min 43.839s (kernel) + 7.763s (userspace) = 1min 51.603s
graphical.target reached after 7.758s in userspace
The output of "sudo blkid" is
/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/sda: PTUUID="8f39e0f9" PTTYPE="dos"
/dev/sdb5: UUID="92b37aee-3acf-447e-b15e-2fbb8a83e9a7" TYPE="ext4" PARTUUID="7ff18de1-05"
/dev/sdb6: UUID="21d2706c-8400-44f6-ad90-79d2dfb6384f" TYPE="swap" PARTUUID="7ff18de1-06"
(the sda is an older hard-drive (not SSD) that I want to just use for backing up some files).
The content of "/etc/fstab" is
UUID=92b37aee-3acf-447e-b15e-2fbb8a83e9a7 / ext4 errors=remount-ro 0 1
UUID=21d2706c-8400-44f6-ad90-79d2dfb6384f none swap sw 0 0
Hope this helps you diagnose my problem and suggest some things to try! Many thanks!
EDIT. In response to request here is the output of "systemd-analyze blame"
6.345s NetworkManager-wait-online.service
4.481s plymouth-quit-wait.service
834ms fwupd.service
639ms dev-sdb5.device
591ms ufw.service
459ms udisks2.service
448ms NetworkManager.service
442ms plymouth-start.service
395ms networkd-dispatcher.service
392ms snapd.service
294ms accounts-daemon.service
284ms dev-loop0.device
268ms ModemManager.service
264ms apparmor.service
256ms dev-loop2.device
243ms dev-loop3.device
238ms dev-loop1.device
213ms systemd-logind.service
197ms dev-loop4.device
191ms snap-gnomex2dcalculator-180.mount
181ms dev-loop5.device
170ms systemd-timesyncd.service
166ms systemd-udevd.service
It goes on but they're all very small times (should I still list them?)
boot 18.04
asked Aug 12 '18 at 19:49
user350031user350031
1112
Please add output ofsystemd-analyze blameto the question. If you see many/dev/loopdevices, read this answer.
– N0rbert
Aug 12 '18 at 19:54
Added systemd-analyze blame output
– user350031
Aug 12 '18 at 19:59
I do not see anything critical here.
– N0rbert
Aug 12 '18 at 20:00
But why is the "kernel" taking over 90s during boot? Is that normal?
– user350031
Aug 12 '18 at 20:01
I have the same question about the kernel, you are right. But userspace loaded fasty. For kernel you can try to investigate logs for errors (journalctl --dmesg,/var/log/syslog,/var/log/kern.log,/var/log/boot.log).
– N0rbert
Aug 12 '18 at 20:07
|
show 5 more comments
I am completely new to Linux so apologies in advance!
I recently installed Ubuntu 18.04 on a wiped machine and everything seems to work well except that it takes about 2 mins to boot.
Here are some details that might be useful for diagnostics (judging by other posts I've seen on similar issues).
The output of "systemd-analyze" is
Startup finished in 1min 43.839s (kernel) + 7.763s (userspace) = 1min 51.603s
graphical.target reached after 7.758s in userspace
The output of "sudo blkid" is
/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/sda: PTUUID="8f39e0f9" PTTYPE="dos"
/dev/sdb5: UUID="92b37aee-3acf-447e-b15e-2fbb8a83e9a7" TYPE="ext4" PARTUUID="7ff18de1-05"
/dev/sdb6: UUID="21d2706c-8400-44f6-ad90-79d2dfb6384f" TYPE="swap" PARTUUID="7ff18de1-06"
(the sda is an older hard-drive (not SSD) that I want to just use for backing up some files).
The content of "/etc/fstab" is
UUID=92b37aee-3acf-447e-b15e-2fbb8a83e9a7 / ext4 errors=remount-ro 0 1
UUID=21d2706c-8400-44f6-ad90-79d2dfb6384f none swap sw 0 0
Hope this helps you diagnose my problem and suggest some things to try! Many thanks!
EDIT. In response to request here is the output of "systemd-analyze blame"
6.345s NetworkManager-wait-online.service
4.481s plymouth-quit-wait.service
834ms fwupd.service
639ms dev-sdb5.device
591ms ufw.service
459ms udisks2.service
448ms NetworkManager.service
442ms plymouth-start.service
395ms networkd-dispatcher.service
392ms snapd.service
294ms accounts-daemon.service
284ms dev-loop0.device
268ms ModemManager.service
264ms apparmor.service
256ms dev-loop2.device
243ms dev-loop3.device
238ms dev-loop1.device
213ms systemd-logind.service
197ms dev-loop4.device
191ms snap-gnomex2dcalculator-180.mount
181ms dev-loop5.device
170ms systemd-timesyncd.service
166ms systemd-udevd.service
It goes on but they're all very small times (should I still list them?)
boot 18.04
asked Aug 12 '18 at 19:49
user350031user350031
1112
I am completely new to Linux so apologies in advance!
I recently installed Ubuntu 18.04 on a wiped machine and everything seems to work well except that it takes about 2 mins to boot.
Here are some details that might be useful for diagnostics (judging by other posts I've seen on similar issues).
The output of "systemd-analyze" is
Startup finished in 1min 43.839s (kernel) + 7.763s (userspace) = 1min 51.603s
graphical.target reached after 7.758s in userspace
The output of "sudo blkid" is
/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/sda: PTUUID="8f39e0f9" PTTYPE="dos"
/dev/sdb5: UUID="92b37aee-3acf-447e-b15e-2fbb8a83e9a7" TYPE="ext4" PARTUUID="7ff18de1-05"
/dev/sdb6: UUID="21d2706c-8400-44f6-ad90-79d2dfb6384f" TYPE="swap" PARTUUID="7ff18de1-06"
(the sda is an older hard-drive (not SSD) that I want to just use for backing up some files).
The content of "/etc/fstab" is
UUID=92b37aee-3acf-447e-b15e-2fbb8a83e9a7 / ext4 errors=remount-ro 0 1
UUID=21d2706c-8400-44f6-ad90-79d2dfb6384f none swap sw 0 0
Hope this helps you diagnose my problem and suggest some things to try! Many thanks!
EDIT. In response to request here is the output of "systemd-analyze blame"
6.345s NetworkManager-wait-online.service
4.481s plymouth-quit-wait.service
834ms fwupd.service
639ms dev-sdb5.device
591ms ufw.service
459ms udisks2.service
448ms NetworkManager.service
442ms plymouth-start.service
395ms networkd-dispatcher.service
392ms snapd.service
294ms accounts-daemon.service
284ms dev-loop0.device
268ms ModemManager.service
264ms apparmor.service
256ms dev-loop2.device
243ms dev-loop3.device
238ms dev-loop1.device
213ms systemd-logind.service
197ms dev-loop4.device
191ms snap-gnomex2dcalculator-180.mount
181ms dev-loop5.device
170ms systemd-timesyncd.service
166ms systemd-udevd.service
It goes on but they're all very small times (should I still list them?)
boot 18.04
boot 18.04
asked Aug 12 '18 at 19:49
user350031user350031
1112
asked Aug 12 '18 at 19:49
user350031user350031
1112
edited Aug 12 '18 at 19:58
user350031
asked Aug 12 '18 at 19:49
user350031user350031
1112
asked Aug 12 '18 at 19:49
user350031user350031
1112
asked Aug 12 '18 at 19:49
user350031user350031
1112
1112
Please add output ofsystemd-analyze blameto the question. If you see many/dev/loopdevices, read this answer.
– N0rbert
Aug 12 '18 at 19:54
Added systemd-analyze blame output
– user350031
Aug 12 '18 at 19:59
I do not see anything critical here.
– N0rbert
Aug 12 '18 at 20:00
But why is the "kernel" taking over 90s during boot? Is that normal?
– user350031
Aug 12 '18 at 20:01
I have the same question about the kernel, you are right. But userspace loaded fasty. For kernel you can try to investigate logs for errors (journalctl --dmesg,/var/log/syslog,/var/log/kern.log,/var/log/boot.log).
– N0rbert
Aug 12 '18 at 20:07
|
show 5 more comments
Please add output ofsystemd-analyze blameto the question. If you see many/dev/loopdevices, read this answer.
– N0rbert
Aug 12 '18 at 19:54
Added systemd-analyze blame output
– user350031
Aug 12 '18 at 19:59
I do not see anything critical here.
– N0rbert
Aug 12 '18 at 20:00
But why is the "kernel" taking over 90s during boot? Is that normal?
– user350031
Aug 12 '18 at 20:01
I have the same question about the kernel, you are right. But userspace loaded fasty. For kernel you can try to investigate logs for errors (journalctl --dmesg,/var/log/syslog,/var/log/kern.log,/var/log/boot.log).
– N0rbert
Aug 12 '18 at 20:07
Please add output of
systemd-analyze blame to the question. If you see many /dev/loop devices, read this answer.– N0rbert
Aug 12 '18 at 19:54
Please add output of
systemd-analyze blame to the question. If you see many /dev/loop devices, read this answer.– N0rbert
Aug 12 '18 at 19:54
Added systemd-analyze blame output
– user350031
Aug 12 '18 at 19:59
Added systemd-analyze blame output
– user350031
Aug 12 '18 at 19:59
I do not see anything critical here.
– N0rbert
Aug 12 '18 at 20:00
I do not see anything critical here.
– N0rbert
Aug 12 '18 at 20:00
But why is the "kernel" taking over 90s during boot? Is that normal?
– user350031
Aug 12 '18 at 20:01
But why is the "kernel" taking over 90s during boot? Is that normal?
– user350031
Aug 12 '18 at 20:01
I have the same question about the kernel, you are right. But userspace loaded fasty. For kernel you can try to investigate logs for errors (
journalctl --dmesg, /var/log/syslog, /var/log/kern.log, /var/log/boot.log).– N0rbert
Aug 12 '18 at 20:07
I have the same question about the kernel, you are right. But userspace loaded fasty. For kernel you can try to investigate logs for errors (
journalctl --dmesg, /var/log/syslog, /var/log/kern.log, /var/log/boot.log).– N0rbert
Aug 12 '18 at 20:07
|
show 5 more comments
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1064755%2fvery-slow-load-on-ubuntu-18-04%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
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1064755%2fvery-slow-load-on-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Please add output of
systemd-analyze blameto the question. If you see many/dev/loopdevices, read this answer.– N0rbert
Aug 12 '18 at 19:54
Added systemd-analyze blame output
– user350031
Aug 12 '18 at 19:59
I do not see anything critical here.
– N0rbert
Aug 12 '18 at 20:00
But why is the "kernel" taking over 90s during boot? Is that normal?
– user350031
Aug 12 '18 at 20:01
I have the same question about the kernel, you are right. But userspace loaded fasty. For kernel you can try to investigate logs for errors (
journalctl --dmesg,/var/log/syslog,/var/log/kern.log,/var/log/boot.log).– N0rbert
Aug 12 '18 at 20:07