Slow boot time (Ubuntu 18.04) on SSD
I've come back to Ubuntu; I'm on Dual boot (Windows 10/Ubuntu 18.04) on a SSD with no swap partition.
I have a problem. While Windows boot time is just a matter of 3-5s, Ubuntu takes 30-40s.
I've runsystemd-analyze blame and systemd-analyze critical-chain and this is what I got:
Any idea of what is going on (why these services are taking so much time to run)?
boot 18.04 ssd services systemd
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
asked Jun 25 '18 at 21:27
VentoVento
613
add a comment |
I've come back to Ubuntu; I'm on Dual boot (Windows 10/Ubuntu 18.04) on a SSD with no swap partition.
I have a problem. While Windows boot time is just a matter of 3-5s, Ubuntu takes 30-40s.
I've runsystemd-analyze blame and systemd-analyze critical-chain and this is what I got:
Any idea of what is going on (why these services are taking so much time to run)?
boot 18.04 ssd services systemd
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
asked Jun 25 '18 at 21:27
VentoVento
613
Please don't use images for terminal output. Instead, copy and paste the output into your question, select it with your mouse, and press the{}button in the editor.
– Chai T. Rex
Jun 25 '18 at 22:26
add a comment |
I've come back to Ubuntu; I'm on Dual boot (Windows 10/Ubuntu 18.04) on a SSD with no swap partition.
I have a problem. While Windows boot time is just a matter of 3-5s, Ubuntu takes 30-40s.
I've runsystemd-analyze blame and systemd-analyze critical-chain and this is what I got:
Any idea of what is going on (why these services are taking so much time to run)?
boot 18.04 ssd services systemd
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
asked Jun 25 '18 at 21:27
VentoVento
613
I've come back to Ubuntu; I'm on Dual boot (Windows 10/Ubuntu 18.04) on a SSD with no swap partition.
I have a problem. While Windows boot time is just a matter of 3-5s, Ubuntu takes 30-40s.
I've runsystemd-analyze blame and systemd-analyze critical-chain and this is what I got:
Any idea of what is going on (why these services are taking so much time to run)?
boot 18.04 ssd services systemd
boot 18.04 ssd services systemd
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
asked Jun 25 '18 at 21:27
VentoVento
613
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
asked Jun 25 '18 at 21:27
VentoVento
613
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
edited Jun 26 '18 at 7:16
Stephen Rauch
1,1546716
1,1546716
asked Jun 25 '18 at 21:27
VentoVento
613
asked Jun 25 '18 at 21:27
VentoVento
613
asked Jun 25 '18 at 21:27
VentoVento
613
613
Please don't use images for terminal output. Instead, copy and paste the output into your question, select it with your mouse, and press the{}button in the editor.
– Chai T. Rex
Jun 25 '18 at 22:26
add a comment |
Please don't use images for terminal output. Instead, copy and paste the output into your question, select it with your mouse, and press the{}button in the editor.
– Chai T. Rex
Jun 25 '18 at 22:26
Please don't use images for terminal output. Instead, copy and paste the output into your question, select it with your mouse, and press the
{} button in the editor.– Chai T. Rex
Jun 25 '18 at 22:26
Please don't use images for terminal output. Instead, copy and paste the output into your question, select it with your mouse, and press the
{} button in the editor.– Chai T. Rex
Jun 25 '18 at 22:26
add a comment |
2 Answers
2
active
oldest
votes
I'm going to copy my answer from here, as I believe you might be affected by the same problem I was.
You seem to be affected by this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
The fix
In order to fix it you have to modify located here: /etc/initramfs-tools/conf.d/resume and ensure the value is as follows: RESUME=none.
Ensure you apply your settings sudo update-initramfs -u
After fix improvements
systemd-analyze time
Startup finished in 2.195s (kernel) + 11.663s (userspace) = 13.858s
graphical.target reached after 11.649s in userspace
Before it was around ~50s
References
This answer is also located on the bug page but it is also located here:
- https://askubuntu.com/a/1013935/604711
- https://ubuntuforums.org/showthread.php?t=2390448
answered Jan 13 at 4:02
ZauxstZauxst
663
I have an m.2 hard drive, and this answer, combined with changing my ethernet interface toallow-hotplugbrought my boot time from 45 seconds down to 5.7 seconds.
– Mike
Feb 7 at 8:12
add a comment |
I've seen this manifest on two desktops I manage.
This is a kernel related regression, the launchpad bug is: https://bugs.launchpad.net/ubuntu/+bug/1779827
As a workaround, press keys and/or move the mouse at boot. This will increase the randomness entropy.
Or running the following command to install rng-tools solves the issue for me:
sudo apt install rng-tools
From Arch wiki: The rng-tools is a set of utilities related to random number generation in kernel. This is mainly useful to increase the quantity of entropy in kernel to make /dev/random faster.
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
add a comment |
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%2f1049693%2fslow-boot-time-ubuntu-18-04-on-ssd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'm going to copy my answer from here, as I believe you might be affected by the same problem I was.
You seem to be affected by this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
The fix
In order to fix it you have to modify located here: /etc/initramfs-tools/conf.d/resume and ensure the value is as follows: RESUME=none.
Ensure you apply your settings sudo update-initramfs -u
After fix improvements
systemd-analyze time
Startup finished in 2.195s (kernel) + 11.663s (userspace) = 13.858s
graphical.target reached after 11.649s in userspace
Before it was around ~50s
References
This answer is also located on the bug page but it is also located here:
- https://askubuntu.com/a/1013935/604711
- https://ubuntuforums.org/showthread.php?t=2390448
answered Jan 13 at 4:02
ZauxstZauxst
663
I have an m.2 hard drive, and this answer, combined with changing my ethernet interface toallow-hotplugbrought my boot time from 45 seconds down to 5.7 seconds.
– Mike
Feb 7 at 8:12
add a comment |
I'm going to copy my answer from here, as I believe you might be affected by the same problem I was.
You seem to be affected by this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
The fix
In order to fix it you have to modify located here: /etc/initramfs-tools/conf.d/resume and ensure the value is as follows: RESUME=none.
Ensure you apply your settings sudo update-initramfs -u
After fix improvements
systemd-analyze time
Startup finished in 2.195s (kernel) + 11.663s (userspace) = 13.858s
graphical.target reached after 11.649s in userspace
Before it was around ~50s
References
This answer is also located on the bug page but it is also located here:
- https://askubuntu.com/a/1013935/604711
- https://ubuntuforums.org/showthread.php?t=2390448
answered Jan 13 at 4:02
ZauxstZauxst
663
I have an m.2 hard drive, and this answer, combined with changing my ethernet interface toallow-hotplugbrought my boot time from 45 seconds down to 5.7 seconds.
– Mike
Feb 7 at 8:12
add a comment |
I'm going to copy my answer from here, as I believe you might be affected by the same problem I was.
You seem to be affected by this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
The fix
In order to fix it you have to modify located here: /etc/initramfs-tools/conf.d/resume and ensure the value is as follows: RESUME=none.
Ensure you apply your settings sudo update-initramfs -u
After fix improvements
systemd-analyze time
Startup finished in 2.195s (kernel) + 11.663s (userspace) = 13.858s
graphical.target reached after 11.649s in userspace
Before it was around ~50s
References
This answer is also located on the bug page but it is also located here:
- https://askubuntu.com/a/1013935/604711
- https://ubuntuforums.org/showthread.php?t=2390448
answered Jan 13 at 4:02
ZauxstZauxst
663
I'm going to copy my answer from here, as I believe you might be affected by the same problem I was.
You seem to be affected by this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
The fix
In order to fix it you have to modify located here: /etc/initramfs-tools/conf.d/resume and ensure the value is as follows: RESUME=none.
Ensure you apply your settings sudo update-initramfs -u
After fix improvements
systemd-analyze time
Startup finished in 2.195s (kernel) + 11.663s (userspace) = 13.858s
graphical.target reached after 11.649s in userspace
Before it was around ~50s
References
This answer is also located on the bug page but it is also located here:
- https://askubuntu.com/a/1013935/604711
- https://ubuntuforums.org/showthread.php?t=2390448
answered Jan 13 at 4:02
ZauxstZauxst
663
answered Jan 13 at 4:02
ZauxstZauxst
663
answered Jan 13 at 4:02
ZauxstZauxst
663
answered Jan 13 at 4:02
ZauxstZauxst
663
663
I have an m.2 hard drive, and this answer, combined with changing my ethernet interface toallow-hotplugbrought my boot time from 45 seconds down to 5.7 seconds.
– Mike
Feb 7 at 8:12
add a comment |
I have an m.2 hard drive, and this answer, combined with changing my ethernet interface toallow-hotplugbrought my boot time from 45 seconds down to 5.7 seconds.
– Mike
Feb 7 at 8:12
I have an m.2 hard drive, and this answer, combined with changing my ethernet interface to
allow-hotplug brought my boot time from 45 seconds down to 5.7 seconds.– Mike
Feb 7 at 8:12
I have an m.2 hard drive, and this answer, combined with changing my ethernet interface to
allow-hotplug brought my boot time from 45 seconds down to 5.7 seconds.– Mike
Feb 7 at 8:12
add a comment |
I've seen this manifest on two desktops I manage.
This is a kernel related regression, the launchpad bug is: https://bugs.launchpad.net/ubuntu/+bug/1779827
As a workaround, press keys and/or move the mouse at boot. This will increase the randomness entropy.
Or running the following command to install rng-tools solves the issue for me:
sudo apt install rng-tools
From Arch wiki: The rng-tools is a set of utilities related to random number generation in kernel. This is mainly useful to increase the quantity of entropy in kernel to make /dev/random faster.
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
add a comment |
I've seen this manifest on two desktops I manage.
This is a kernel related regression, the launchpad bug is: https://bugs.launchpad.net/ubuntu/+bug/1779827
As a workaround, press keys and/or move the mouse at boot. This will increase the randomness entropy.
Or running the following command to install rng-tools solves the issue for me:
sudo apt install rng-tools
From Arch wiki: The rng-tools is a set of utilities related to random number generation in kernel. This is mainly useful to increase the quantity of entropy in kernel to make /dev/random faster.
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
add a comment |
I've seen this manifest on two desktops I manage.
This is a kernel related regression, the launchpad bug is: https://bugs.launchpad.net/ubuntu/+bug/1779827
As a workaround, press keys and/or move the mouse at boot. This will increase the randomness entropy.
Or running the following command to install rng-tools solves the issue for me:
sudo apt install rng-tools
From Arch wiki: The rng-tools is a set of utilities related to random number generation in kernel. This is mainly useful to increase the quantity of entropy in kernel to make /dev/random faster.
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
I've seen this manifest on two desktops I manage.
This is a kernel related regression, the launchpad bug is: https://bugs.launchpad.net/ubuntu/+bug/1779827
As a workaround, press keys and/or move the mouse at boot. This will increase the randomness entropy.
Or running the following command to install rng-tools solves the issue for me:
sudo apt install rng-tools
From Arch wiki: The rng-tools is a set of utilities related to random number generation in kernel. This is mainly useful to increase the quantity of entropy in kernel to make /dev/random faster.
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
answered Jul 16 '18 at 20:30
psiphi75psiphi75
354217
354217
add a comment |
add a comment |
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%2f1049693%2fslow-boot-time-ubuntu-18-04-on-ssd%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 don't use images for terminal output. Instead, copy and paste the output into your question, select it with your mouse, and press the
{}button in the editor.– Chai T. Rex
Jun 25 '18 at 22:26