Debian hangs at boot with "random: crng init done"?

patrick295767 · 09-07-2017, 02:40 PM

Hello, I have a debian machine that hangs giving at boot:
"random: crng init done"

It seems that it is an issue that may occur. Would you eventually know in which solving solution I might look at?

Pitty for more info and report, I finally had to reinstall this server. Hopefully this interesting issue comes again once more.

Best regards

frankbell · 09-07-2017, 09:36 PM

According to this article from the Arch Wiki, the error means

Quote:

the system has long reached its default boot target before the kernel gathered enough entropy to initialize the pool. Due to systemd requiring entropy at an early stage, it may happen though that the pool is depleted in the boot process without further kernel warnings.

I have no idea how to fix it. A web search for the error message turns up little but nothing that seems explicity to help.

What version of Debian and what is the kernel version as well the computer's specs? This information may help others who look at this thread.

jondaley · 11-26-2017, 08:41 AM

This thread is the number 1 hit in google for that log message. In my case, the power had been yanked on the machine, and so had an unclean shutdown.

The next step that should happen within seconds of that message is to mount the filesystem, so it makes sense there is a delay there, though I would have expected a fsck sort of message showing that it was checking the filesystem.

After 10 minutes (on a 500GB LSI RAID1 drive) it completed the boot like nothing happened.

I rebooted again, and it booted like normal. Whew.

giis · 12-24-2017, 08:48 AM

@patrick295767, Have you found a solution for this? I'm seeing the same message now with User mode Linux.

tteigue · 12-27-2017, 10:50 AM

Same issue here. Running Centos7 VM on Ovirt. Added a new disk to a server that has been running with no issues, went to reboot and this is where I now get hung...

random: crng init done (Sits there for hours)

Went ahead and removed the new drive thinking that may be the issue but I still continue to see the same message during boot up.

Thanks,
Tommie

weinerwad3000 · 01-07-2018, 07:09 PM

I hope this helps someone. I was having this problem and it turned out it was my SD card. After removing the SD card it booted normal