Ubuntu 18.04 : delay during boot - waiting for resume device - message : random: crng init

Bug #1767782 reported by DLCBurggraaff
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Xubuntu 18.04 : delay during boot

[ 3.155746] sd 5:0:0:1: [sde] Attached SCSI removable disk
[ 32.221209] random: crng init done

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
CurrentDesktop: XFCE
Date: Sun Apr 29 12:14:19 2018
DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda11 ro
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda11 ro
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: H110M-HDS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
DLCBurggraaff (burdi) wrote :
Revision history for this message
DLCBurggraaff (burdi) wrote :

I already saw this symptom with the betas.

Revision history for this message
DLCBurggraaff (burdi) wrote :

I already saw this symptom with the betas, but did not report it then because it was mentioned in the pertinent releasenotes -- for as far as I remember, that is.
:D

Revision history for this message
DLCBurggraaff (burdi) wrote :

Hmm, I found #1685794 ...

Revision history for this message
DLCBurggraaff (burdi) wrote :

As I reported in #1685794 installing cryptsetup{,-bin} resolved my problem.
:D

Revision history for this message
DLCBurggraaff (burdi) wrote :

Cheered too son: after a few reboots the problem is back.
:(

Revision history for this message
DLCBurggraaff (burdi) wrote :

... too soon ...

Revision history for this message
DLCBurggraaff (burdi) wrote :

I have a strong suspicion that the delay at boot is caused by the swap and/or root partition(s) being re-initialized and therefore getting a new UUID ...
:D

Revision history for this message
DLCBurggraaff (burdi) wrote :

For a correct understanding: this re-initializing of the root and swap partitions is the verification step of my backup procedure -- and my restore procedure of course.
:D

Revision history for this message
DLCBurggraaff (burdi) wrote :

Or is it simply waiting on /dev/random ?
:D

Revision history for this message
DLCBurggraaff (burdi) wrote :

SOLVED !!! As per https://askubuntu.com/questions/1029598/xubuntu-18-04-kernel-takes-long-to-boot/1029993 :

During boot messages it would say that it timed out waiting for resume device *). Check in /etc/initramfs-tools/conf.d/resume if there is UUID in it like RESUME=some-uuid remove uuid and replace with "none" to be RESUME=none. After that run sudo update-initramfs -u and it should be good to go.

*) This message scrolls by so fast that it is impossible to read it in its entirety and is not included in the /var/log/messages.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

DLCBurggraaff,

Can you please reword to bug title to match your findings?

Changed in plymouth (Ubuntu):
status: New → Incomplete
DLCBurggraaff (burdi)
summary: - Xubuntu 18.04 : delay during boot - random: crng init
+ Xubuntu 18.04 : delay during boot - waiting for resume device - message
+ : random: crng init
Changed in plymouth (Ubuntu):
status: Incomplete → New
Revision history for this message
Mihal Zemsky (mzemsk) wrote : Re: Xubuntu 18.04 : delay during boot - waiting for resume device - message : random: crng init
Download full text (3.5 KiB)

I have the same problem with "crng init done".
My Ubuntu 18 server is running under MS server 2016 Hyper-v virtualization solution.
I tried to download last image of Ubuntu via torrent and installed second VM, but no luck, an error still here.

Maybe my information would be helpful for problem resolving.

root@maindb-master:/home/pa# uname -r
4.15.0-33-generic

root@maindb-master:/home/pa# systemd-analyze
Startup finished in 3min 40.384s (kernel) + 9.377s (userspace) = 3min 49.761s
graphical.target reached after 7.150s in userspace

[ 3.959777] hid 0006:045E:0621.0001: input: <UNKNOWN> HID v0.01 Mouse [Microsoft Vmbus HID-compliant Mouse] on
[ 3.961890] hv_utils: Heartbeat IC version 3.0
[ 3.964587] hv_utils: Shutdown IC version 3.0
[ 3.966292] hv_utils: TimeSync IC version 4.0
[ 3.968791] hv_utils: VSS IC version 5.0
[ 4.204137] psmouse serio1: trackpoint: failed to get extended button data, assuming 3 buttons
[ 8.497068] psmouse serio1: trackpoint: IBM TrackPoint firmware: 0x01, buttons: 3/3
[ 8.505665] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/input/input3
[ 8.509469] input: AT Translated Set 2 keyboard as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/d34b2567-b9b6-42b9-8778-0a4ec0b955bf/serio2/inp$
[ 16.428110] random: crng init done
[ 16.428115] random: 7 urandom warning(s) missed due to ratelimiting
[ 221.416066] raid6: sse2x1 gen() 3405 MB/s
[ 221.464076] raid6: sse2x1 xor() 1938 MB/s
[ 221.512035] raid6: sse2x2 gen() 3323 MB/s
[ 221.562630] raid6: sse2x2 xor() 2522 MB/s
[ 221.612035] raid6: sse2x4 gen() 4944 MB/s

root@maindb-master:/home/pa# systemd-analyze blame
         2.270s cloud-init-local.service
          1.564s cloud-init.service
          1.203s cloud-config.service
          1.201s dev-sda2.device
          1.066s apparmor.service
          1.013s cloud-final.service
           852ms networkd-dispatcher.service
           691ms accounts-daemon.service
           677ms snapd.service
           607ms grub-common.service
           571ms lxd-containers.service
           520ms iscsid.service
           510ms ebtables.service
           502ms systemd-journal-flush.service
           355ms apport.service
           316ms thermald.service
           304ms keyboard-setup.service
           279ms systemd-logind.service
           269ms systemd-udev-trigger.service
           267ms systemd-timesyncd.service
           253ms systemd-modules-load.service
           236ms snap-core-4486.mount
           210ms systemd-resolved.service
           204ms ufw.service
           201ms rsyslog.service
           196ms sys-kernel-debug.mount
           193ms systemd-remount-fs.service
           193ms dev-mqueue.mount
           181ms polkit.service
           180ms ssh.service
           159ms user@1000.service
           154ms lvm2-monitor.service
           137ms setvtrgb.service
           136ms console-setup.service
           133ms plymouth-read-write.service
           129ms systemd-journald.service
           123ms blk-availability.service
           118ms systemd-sysctl.service
           116ms systemd-user-sessions.service

And there a...

Read more...

Revision history for this message
Mihal Zemsky (mzemsk) wrote :

I tried to install last kernel (4.18.0 from 20180812) but without luck. Problem still here.

Revision history for this message
DLCBurggraaff (burdi) wrote :

What about applying the first answer in the link in post #11 ?
:D

Revision history for this message
Mihal Zemsky (mzemsk) wrote :

File /etc/initramfs-tools/conf.d/resume is empty.
Also I tried to install cryptsetup, the answer was "cryptsetup is already last version".
I've tried every advice in my previous post (there are links at the end of my message)

I moved VM to other Hyper-V machine and problem resolved!!! I don't know how but it works without any delay.
First server configuration (VM start delay):
http://i68.tinypic.com/2hf2kd2.jpg
Second server configuration (no start delay):
http://i63.tinypic.com/21cyw4x.png

Any thoughts?

Revision history for this message
Mihal Zemsky (mzemsk) wrote :

Debian 9 x64 with 4.9.0.8 kernel have no delay at all (while running on hyper-v machine)!

description: updated
tags: added: performance
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1685794, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

summary: - Xubuntu 18.04 : delay during boot - waiting for resume device - message
- : random: crng init
+ Ubuntu 18.04 : delay during boot - waiting for resume device - message :
+ random: crng init
Changed in linux (Ubuntu):
status: New → Confirmed
Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.