Ubuntu installation stuck at random crng init done
I have installed Ubuntu 16.04 ony Lenovo 3g hhd, 4 g ram. It all went smoothly until it gets stuck on the boot process with "random crng init done". Help with this issue is greatly appreciated.
16.04
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
add a comment |
I have installed Ubuntu 16.04 ony Lenovo 3g hhd, 4 g ram. It all went smoothly until it gets stuck on the boot process with "random crng init done". Help with this issue is greatly appreciated.
16.04
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
Do you have a SD card plugged in? Try removing it if there is one inserted
– Paul Tanzini
Mar 24 '18 at 22:12
I'm getting this issue on my raspberry pi (arm64) with kernel 4.9.59
– Brady Dean
Mar 25 '18 at 21:43
add a comment |
I have installed Ubuntu 16.04 ony Lenovo 3g hhd, 4 g ram. It all went smoothly until it gets stuck on the boot process with "random crng init done". Help with this issue is greatly appreciated.
16.04
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
I have installed Ubuntu 16.04 ony Lenovo 3g hhd, 4 g ram. It all went smoothly until it gets stuck on the boot process with "random crng init done". Help with this issue is greatly appreciated.
16.04
16.04
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
asked Mar 24 '18 at 18:37
Victor SanchezVictor Sanchez
2612
2612
Do you have a SD card plugged in? Try removing it if there is one inserted
– Paul Tanzini
Mar 24 '18 at 22:12
I'm getting this issue on my raspberry pi (arm64) with kernel 4.9.59
– Brady Dean
Mar 25 '18 at 21:43
add a comment |
Do you have a SD card plugged in? Try removing it if there is one inserted
– Paul Tanzini
Mar 24 '18 at 22:12
I'm getting this issue on my raspberry pi (arm64) with kernel 4.9.59
– Brady Dean
Mar 25 '18 at 21:43
Do you have a SD card plugged in? Try removing it if there is one inserted
– Paul Tanzini
Mar 24 '18 at 22:12
Do you have a SD card plugged in? Try removing it if there is one inserted
– Paul Tanzini
Mar 24 '18 at 22:12
I'm getting this issue on my raspberry pi (arm64) with kernel 4.9.59
– Brady Dean
Mar 25 '18 at 21:43
I'm getting this issue on my raspberry pi (arm64) with kernel 4.9.59
– Brady Dean
Mar 25 '18 at 21:43
add a comment |
4 Answers
4
active
oldest
votes
It's a kernel bug that can happen with different kernel.
"apt-get install rng-tools" run as root in a terminal should work.
answered May 12 '18 at 13:47
Giulio GGiulio G
412
This also helped me on Ubuntu 18.04 when the kernel was getting stuck at "random: crng init done" for 90 sec before boot would continue. I have no idea if the following is really necessary, but after installing rng-tools, I also updated initramfs and grub:sudo update-initramfs -uandsudo update-grub. More info on rng-tools is here: wiki.archlinux.org/index.php/Rng-tools
– MDMower
Jul 8 '18 at 20:42
add a comment |
At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:
sudo dmesg | less
The problem message:
kernel: random: crng init done
The solution:
sudo apt install haveged
sudo systemctl enable haveged
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
What is your basis that the kernel waits for mouse movements to init the random number generator? There are cases where this may not be the cause (non-graphical environments for example where there is no GUI or Mouse interaction) (and I've had this happen twice in the past few months on low-spec servers)
– Thomas Ward♦
Aug 10 '18 at 20:22
add a comment |
I faced the same issue, and the fixes suggested here did not work. It was a broken link to a swap partition on my USB. It can be fixed using update-initramfs -uk all
More details can be found at https://askubuntu.com/a/1084738/881810
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
add a comment |
This issue can also be caused by combining non-related btrfs partitions on 1 system and booting with a kernel and init-system that doesn't know about this.
I had a system with a disk for my data and another one for my OS. Both used btrfs and although the system worked fine, I couldn't boot from a USB-stick. After (physically) detaching the data-disk it booted fine from USB.
Depending on what you want to achieve and how much time you want to spend on it there are multiple solutions available if your are in a similar situation. From easy to hard:
- Don't boot from any other medium (ignoring the problem)
- Backup your data of the extra btrfs-partition, overwrite the partition with another type of filesystem (e.g. ext4) and place your data back on this new filesystem.
- Merge the 2 btrfs partitions into 1 filesystem. This can take a lot of work, and it's easy to make a mistake here. Double-check the newest version of the btrfs docs before you do this.
answered Feb 21 at 0:35
GaroGaro
13
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%2f1018907%2fubuntu-installation-stuck-at-random-crng-init-done%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's a kernel bug that can happen with different kernel.
"apt-get install rng-tools" run as root in a terminal should work.
answered May 12 '18 at 13:47
Giulio GGiulio G
412
This also helped me on Ubuntu 18.04 when the kernel was getting stuck at "random: crng init done" for 90 sec before boot would continue. I have no idea if the following is really necessary, but after installing rng-tools, I also updated initramfs and grub:sudo update-initramfs -uandsudo update-grub. More info on rng-tools is here: wiki.archlinux.org/index.php/Rng-tools
– MDMower
Jul 8 '18 at 20:42
add a comment |
It's a kernel bug that can happen with different kernel.
"apt-get install rng-tools" run as root in a terminal should work.
answered May 12 '18 at 13:47
Giulio GGiulio G
412
This also helped me on Ubuntu 18.04 when the kernel was getting stuck at "random: crng init done" for 90 sec before boot would continue. I have no idea if the following is really necessary, but after installing rng-tools, I also updated initramfs and grub:sudo update-initramfs -uandsudo update-grub. More info on rng-tools is here: wiki.archlinux.org/index.php/Rng-tools
– MDMower
Jul 8 '18 at 20:42
add a comment |
It's a kernel bug that can happen with different kernel.
"apt-get install rng-tools" run as root in a terminal should work.
answered May 12 '18 at 13:47
Giulio GGiulio G
412
It's a kernel bug that can happen with different kernel.
"apt-get install rng-tools" run as root in a terminal should work.
answered May 12 '18 at 13:47
Giulio GGiulio G
412
answered May 12 '18 at 13:47
Giulio GGiulio G
412
answered May 12 '18 at 13:47
Giulio GGiulio G
412
answered May 12 '18 at 13:47
Giulio GGiulio G
412
412
This also helped me on Ubuntu 18.04 when the kernel was getting stuck at "random: crng init done" for 90 sec before boot would continue. I have no idea if the following is really necessary, but after installing rng-tools, I also updated initramfs and grub:sudo update-initramfs -uandsudo update-grub. More info on rng-tools is here: wiki.archlinux.org/index.php/Rng-tools
– MDMower
Jul 8 '18 at 20:42
add a comment |
This also helped me on Ubuntu 18.04 when the kernel was getting stuck at "random: crng init done" for 90 sec before boot would continue. I have no idea if the following is really necessary, but after installing rng-tools, I also updated initramfs and grub:sudo update-initramfs -uandsudo update-grub. More info on rng-tools is here: wiki.archlinux.org/index.php/Rng-tools
– MDMower
Jul 8 '18 at 20:42
This also helped me on Ubuntu 18.04 when the kernel was getting stuck at "random: crng init done" for 90 sec before boot would continue. I have no idea if the following is really necessary, but after installing rng-tools, I also updated initramfs and grub:
sudo update-initramfs -u and sudo update-grub. More info on rng-tools is here: wiki.archlinux.org/index.php/Rng-tools– MDMower
Jul 8 '18 at 20:42
This also helped me on Ubuntu 18.04 when the kernel was getting stuck at "random: crng init done" for 90 sec before boot would continue. I have no idea if the following is really necessary, but after installing rng-tools, I also updated initramfs and grub:
sudo update-initramfs -u and sudo update-grub. More info on rng-tools is here: wiki.archlinux.org/index.php/Rng-tools– MDMower
Jul 8 '18 at 20:42
add a comment |
At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:
sudo dmesg | less
The problem message:
kernel: random: crng init done
The solution:
sudo apt install haveged
sudo systemctl enable haveged
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
What is your basis that the kernel waits for mouse movements to init the random number generator? There are cases where this may not be the cause (non-graphical environments for example where there is no GUI or Mouse interaction) (and I've had this happen twice in the past few months on low-spec servers)
– Thomas Ward♦
Aug 10 '18 at 20:22
add a comment |
At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:
sudo dmesg | less
The problem message:
kernel: random: crng init done
The solution:
sudo apt install haveged
sudo systemctl enable haveged
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
What is your basis that the kernel waits for mouse movements to init the random number generator? There are cases where this may not be the cause (non-graphical environments for example where there is no GUI or Mouse interaction) (and I've had this happen twice in the past few months on low-spec servers)
– Thomas Ward♦
Aug 10 '18 at 20:22
add a comment |
At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:
sudo dmesg | less
The problem message:
kernel: random: crng init done
The solution:
sudo apt install haveged
sudo systemctl enable haveged
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:
sudo dmesg | less
The problem message:
kernel: random: crng init done
The solution:
sudo apt install haveged
sudo systemctl enable haveged
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
edited Aug 10 '18 at 3:27
Stephen Rauch
1,1546716
1,1546716
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
answered Aug 10 '18 at 0:44
virusmxavirusmxa
211
211
What is your basis that the kernel waits for mouse movements to init the random number generator? There are cases where this may not be the cause (non-graphical environments for example where there is no GUI or Mouse interaction) (and I've had this happen twice in the past few months on low-spec servers)
– Thomas Ward♦
Aug 10 '18 at 20:22
add a comment |
What is your basis that the kernel waits for mouse movements to init the random number generator? There are cases where this may not be the cause (non-graphical environments for example where there is no GUI or Mouse interaction) (and I've had this happen twice in the past few months on low-spec servers)
– Thomas Ward♦
Aug 10 '18 at 20:22
What is your basis that the kernel waits for mouse movements to init the random number generator? There are cases where this may not be the cause (non-graphical environments for example where there is no GUI or Mouse interaction) (and I've had this happen twice in the past few months on low-spec servers)
– Thomas Ward♦
Aug 10 '18 at 20:22
What is your basis that the kernel waits for mouse movements to init the random number generator? There are cases where this may not be the cause (non-graphical environments for example where there is no GUI or Mouse interaction) (and I've had this happen twice in the past few months on low-spec servers)
– Thomas Ward♦
Aug 10 '18 at 20:22
add a comment |
I faced the same issue, and the fixes suggested here did not work. It was a broken link to a swap partition on my USB. It can be fixed using update-initramfs -uk all
More details can be found at https://askubuntu.com/a/1084738/881810
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
add a comment |
I faced the same issue, and the fixes suggested here did not work. It was a broken link to a swap partition on my USB. It can be fixed using update-initramfs -uk all
More details can be found at https://askubuntu.com/a/1084738/881810
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
add a comment |
I faced the same issue, and the fixes suggested here did not work. It was a broken link to a swap partition on my USB. It can be fixed using update-initramfs -uk all
More details can be found at https://askubuntu.com/a/1084738/881810
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
I faced the same issue, and the fixes suggested here did not work. It was a broken link to a swap partition on my USB. It can be fixed using update-initramfs -uk all
More details can be found at https://askubuntu.com/a/1084738/881810
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
answered Oct 18 '18 at 3:08
Dushyant MAHADIKDushyant MAHADIK
114
114
add a comment |
add a comment |
This issue can also be caused by combining non-related btrfs partitions on 1 system and booting with a kernel and init-system that doesn't know about this.
I had a system with a disk for my data and another one for my OS. Both used btrfs and although the system worked fine, I couldn't boot from a USB-stick. After (physically) detaching the data-disk it booted fine from USB.
Depending on what you want to achieve and how much time you want to spend on it there are multiple solutions available if your are in a similar situation. From easy to hard:
- Don't boot from any other medium (ignoring the problem)
- Backup your data of the extra btrfs-partition, overwrite the partition with another type of filesystem (e.g. ext4) and place your data back on this new filesystem.
- Merge the 2 btrfs partitions into 1 filesystem. This can take a lot of work, and it's easy to make a mistake here. Double-check the newest version of the btrfs docs before you do this.
answered Feb 21 at 0:35
GaroGaro
13
add a comment |
This issue can also be caused by combining non-related btrfs partitions on 1 system and booting with a kernel and init-system that doesn't know about this.
I had a system with a disk for my data and another one for my OS. Both used btrfs and although the system worked fine, I couldn't boot from a USB-stick. After (physically) detaching the data-disk it booted fine from USB.
Depending on what you want to achieve and how much time you want to spend on it there are multiple solutions available if your are in a similar situation. From easy to hard:
- Don't boot from any other medium (ignoring the problem)
- Backup your data of the extra btrfs-partition, overwrite the partition with another type of filesystem (e.g. ext4) and place your data back on this new filesystem.
- Merge the 2 btrfs partitions into 1 filesystem. This can take a lot of work, and it's easy to make a mistake here. Double-check the newest version of the btrfs docs before you do this.
answered Feb 21 at 0:35
GaroGaro
13
add a comment |
This issue can also be caused by combining non-related btrfs partitions on 1 system and booting with a kernel and init-system that doesn't know about this.
I had a system with a disk for my data and another one for my OS. Both used btrfs and although the system worked fine, I couldn't boot from a USB-stick. After (physically) detaching the data-disk it booted fine from USB.
Depending on what you want to achieve and how much time you want to spend on it there are multiple solutions available if your are in a similar situation. From easy to hard:
- Don't boot from any other medium (ignoring the problem)
- Backup your data of the extra btrfs-partition, overwrite the partition with another type of filesystem (e.g. ext4) and place your data back on this new filesystem.
- Merge the 2 btrfs partitions into 1 filesystem. This can take a lot of work, and it's easy to make a mistake here. Double-check the newest version of the btrfs docs before you do this.
answered Feb 21 at 0:35
GaroGaro
13
This issue can also be caused by combining non-related btrfs partitions on 1 system and booting with a kernel and init-system that doesn't know about this.
I had a system with a disk for my data and another one for my OS. Both used btrfs and although the system worked fine, I couldn't boot from a USB-stick. After (physically) detaching the data-disk it booted fine from USB.
Depending on what you want to achieve and how much time you want to spend on it there are multiple solutions available if your are in a similar situation. From easy to hard:
- Don't boot from any other medium (ignoring the problem)
- Backup your data of the extra btrfs-partition, overwrite the partition with another type of filesystem (e.g. ext4) and place your data back on this new filesystem.
- Merge the 2 btrfs partitions into 1 filesystem. This can take a lot of work, and it's easy to make a mistake here. Double-check the newest version of the btrfs docs before you do this.
answered Feb 21 at 0:35
GaroGaro
13
answered Feb 21 at 0:35
GaroGaro
13
answered Feb 21 at 0:35
GaroGaro
13
answered Feb 21 at 0:35
GaroGaro
13
13
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%2f1018907%2fubuntu-installation-stuck-at-random-crng-init-done%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
Do you have a SD card plugged in? Try removing it if there is one inserted
– Paul Tanzini
Mar 24 '18 at 22:12
I'm getting this issue on my raspberry pi (arm64) with kernel 4.9.59
– Brady Dean
Mar 25 '18 at 21:43