Crng init done linux

Установка Ubuntu застряла при произвольной инициализации crng

Я установил Ubuntu 16.04 только на Lenovo 3g hhd, 4 г оперативной памяти. Все прошло гладко, пока он не застрял в процессе загрузки с «случайным выполнением инициализации crng». Помощь в этом вопросе очень ценится.

5 ответов

Это ошибка ядра, которая может случиться с другим ядром.

«apt-get install rng-tools», работающий от имени пользователя root в терминале, должен работать.

Я столкнулся с той же проблемой, и предложенные здесь исправления не сработали. Это была неработающая ссылка на раздел подкачки на моем USB. Это можно исправить используя update-initramfs -uk all Более подробную информацию можно найти по адресу /questions/298541/ubuntu-1704-medlennaya-zagruzka-na-ssd-s-dvojnoj-zagruzkoj/298544#298544

При загрузке ядро ​​ожидает движения мыши, чтобы инициализировать генератор случайных чисел.

Сообщения ядра при загрузке:

Сообщение о проблеме:

Эта проблема также может быть вызвана объединением несвязанных разделов btrfs в 1 системе и загрузкой с ядром и системой инициализации, которые не знают об этом.

У меня была система с диском для моих данных и еще одна для моей ОС. Оба использовали btrfs, и хотя система работала нормально, я не мог загрузиться с USB-флешки. После (физического) отсоединения диска с данными он нормально загрузился с USB.

В зависимости от того, чего вы хотите достичь и сколько времени вы хотите на это потратить, могут быть предложены несколько решений, если вы находитесь в аналогичной ситуации. От простого к сложному:

• Не загружаться с любого другого носителя (игнорируя проблему)
• Сделайте резервную копию ваших данных дополнительного раздела btrfs, перезаписайте раздел другой файловой системой (например, ext4) и поместите ваши данные обратно в эту новую файловую систему.
• Объедините 2 раздела btrfs в 1 файловую систему. Это может занять много работы, и здесь легко ошибиться. Дважды проверьте последнюю версию документации btrfs, прежде чем сделать это.

Это может произойти после удаления раздела подкачки

Висит перед kernel: random: crng init done может произойти после удаления раздела подкачки.

Если раздел подкачки удален, файл /etc/initramfs-tools/conf.d/resume должен быть либо полностью пустым, либо прочитанным RESUME= , Удалить любой номер UUID. RESUME=NONE не является действительным.

Исходная файловая система RAM требует обновления, чтобы эти изменения вступили в силу:

Источник

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.

5 Answers 5

It’s a kernel bug that can happen with different kernel.

«apt-get install rng-tools» run as root in a terminal should work.

This may happen after deleting the swap partition

Hanging before kernel: random: crng init done may happen after deleting a swap partition.

If a swap partition is deleted, the file /etc/initramfs-tools/conf.d/resume should be either completely empty or read RESUME= . Delete any UUID number. RESUME=NONE is not valid.

The initial RAM filesystem requires updating for these changes to take effect:

At boot, the kernel waits for mouse movements to initialize the random number generator.

Kernel messages on boot:

The problem message:

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

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:

Источник

crng.init blocks boot process without a mouse. #2799

Comments

rin67630 commented Jan 8, 2019 •

Is this the right place for my bug report?
I believe that crng.init belongs to the kernel.
It is supposed to provide some entropy to the random generator from the mouse events.
The Raspberry Pi is frequently used headless e.g. over VNC.

Describe the bug
VNC does not start until a mouse is plugged in.

To reproduce
The behaviour does not happen with a pristine install of 2018-11-13-raspbian-stretch, but has been frequently reported, also with previous versions of Raspbian, on all Raspberry Pi models.

Expected behaviour
The boot process should perform smoothly also without a mouse plugged in.

Actual behaviour
During boot the system hangs after the initialisation of fuse: (etc/logs/messages)
Jan 8 16:12:50 Stretch11 kernel: [ 316.155022] random: crng init done
Jan 8 16:12:50 Stretch11 kernel: [ 316.155036] random: 7 urandom warning(s) missed due to ratelimiting

It can stay at that stage several minutes or forever. As soon as you plug a mouse, it continues.

System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:

• Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
  Bug found on many current models incuding Pi3B+, Pi3A+, PiZeroW
• Which OS and version ( cat /etc/rpi-issue )?
  Raspberry Pi reference 2018-11-13, but also on previous versions.
• Which firmware version ( vcgencmd version )?
  Nov 4 2018 16:31:07, but also on previous versions.
• Which kernel version ( uname -a )?
  Linux Stretch11.2018-3APlus 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
  Logs
  If applicable, add the relevant output from dmesg or similar.
  See Additional context.
  Additional context
  Does not happen on very pristine installs, needs additional software installed (did not yet find which one), but has been frequently reported.
  Does NEVER happen with a mouse connected. Boot process resumes as soon, as a mouse get connected.

System hangs at: (etc/logs/messages)

(found out through plugging the mouse exactly at 16:12:50)

Workaround solution: install haveged.
Then it boots like a charm! Also without a mouse.

Please consider revising that step of the boot process:
The Raspberry Pi is predestined to work headless. Seeking for entropy from a mouse is not purposedly.
I have lost days, until I found the workaround and I am not the only one.
The fora have many similar issues and a lot of users are clueless, fiddling on the wrong gears.

Thank you for considering my issue.

The text was updated successfully, but these errors were encountered:

Источник

Boot delayed for about 90 seconds until ‘random: crng init done’

Affects		Status	Importance	Assigned to	Milestone
​	broadcom-sta (Debian) Edit

Bug Description

Shortened dmesg output, notice the unnaturally long delay before crng init finishes:

[ 8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 8.542239] input: HDA Intel PCH Mic as /devices/ pci0000: 00/0000: 00:1b.0/ sound/card1/ input18
[ 8.542313] input: HDA Intel PCH Line as /devices/ pci0000: 00/0000: 00:1b.0/ sound/card1/ input19
[ 8.542382] input: HDA Intel PCH Dock Line Out as /devices/ pci0000: 00/0000: 00:1b.0/ sound/card1/ input20
[ 8.542449] input: HDA Intel PCH Headphone as /devices/ pci0000: 00/0000: 00:1b.0/ sound/card1/ input21
[ 8.544240] cdc_ether 2-6:2.0 usb0: register ‘cdc_ether’ at usb-0000:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00
[ 8.544271] usbcore: registered new interface driver cdc_ether
[ 8.637660] ieee80211 phy0: Selected rate control algorithm ‘iwl-mvm-rs’
[ 8.654022] input: HP WMI hotkeys as /devices/ virtual/ input/input22
[ 8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0
[ 8.713288] iwlwifi 0000:02:00.0 wlo1: renamed from wlan0
[ 9.804308] input: ST LIS3LV02DL Accelerometer as /devices/ platform/ lis3lv02d/ input/input23
[ 98.327857] random: crng init done
[ 98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 98.330073] Bluetooth: BNEP filters: protocol multicast
[ 98.330077] Bluetooth: BNEP socket layer initialized
[ 98.443281] kauditd_printk_skb: 90 callbacks suppressed
[ 98.492927] IPv6: ADDRCONF( NETDEV_ UP): enp0s25: link is not ready
[ 98.681030] IPv6: ADDRCONF( NETDEV_ UP): enp0s25: link is not ready
[ 98.685672] IPv6: ADDRCONF( NETDEV_ UP): enp0s20u6c2: link is not ready
[ 98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped
[ 98.688384] IPv6: ADDRCONF( NETDEV_ UP): wlo1: link is not ready
[ 98.690915] iwlwifi 0000:02:00.0: L1 Enabled — LTR Enabled

Источник

Crng init done linux

I have been using a PI3B + with a Kingston USB disk for several months to run Jeedom without any problem.

I decide today to update the Pi in update and upgrade. Everything goes perfectly during the installation. Except that restarting is the blocking!

I then connect a screen to see what happens: the log remains stuck on «random: crng init done». No key on the keyboard moves the process forward (only CTRL + ALT + DEL causes the Pi to reboot).

Some useful details:

— I disconnected everything (except the SSD obviously) to avoid a «conflict» with connected elements;
— I waited a long time (> 1h) just in case;
— Everything is well powered on mains, no overheating, etc.

I hope now that you can have an idea to get me out of there because I do not want to reinstall everything when everything worked quite well!

Thank you in advance, I’m counting on you!

Re: random: crng init done

In my experience this is one of the last messages to print out before the login prompt appears (normally.)

In other words this message has nothing to do with your issue.

Attach a screen, boot and see what messages the system prints. It might be busy trying to mount a network resource, checking a filesystem.

Re: random: crng init done

Here is a screenshot of the log.

Re: random: crng init done

from the last thread about this, seems to be a corrupt card thing, possibly a specific download version. Maybe try re-downloading with current Buster (or checking your download against the checksums) and re-flashing?

Источник