[Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

willbprogz227 · 2019-11-28 01:46:04

After many months away, I just installed Ascii 2.1 on a fairly standard five-year-old HP tower. No matter which init system I chose during installation (sysvinit or openrc) Devuan never completes boot, but gets stuck and never recovers from "Waiting for /dev to be fully populated".

(Don't worry about the 'Can't evaluate _CRS...' message, that shows up on any distro I try, and it doesn't cause problems on them)

Here is the inxi output from my Debian install:

System:    Host: debian Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 TWR v: N/A serial: MXL50610ZJ 
           Mobo: Hewlett-Packard model: 18E4 serial: MXL50610ZJ UEFI: Hewlett-Packard v: L01 v02.71 date: 05/09/2017 
CPU:       Topology: Quad Core model: Intel Core i7-4770 bits: 64 type: MT MCP L2 cache: 8192 KiB 
           Speed: 3392 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 3392 2: 3394 3: 3393 4: 3394 5: 3393 6: 3398 7: 3398 
           8: 3397 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel 
           Device-2: Advanced Micro Devices [AMD/ATI] Baffin [Radeon RX 460] driver: amdgpu v: kernel 
           Display: server: X.Org 1.20.4 driver: amdgpu,ati,modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz 
           OpenGL: renderer: Radeon RX 560 Series (POLARIS11 DRM 3.27.0 4.19.0-6-amd64 LLVM 7.0.1) v: 4.5 Mesa 18.3.6 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel 
           Device-3: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Ethernet I217-LM driver: e1000e 
           IF: eno1 state: up speed: 100 Mbps duplex: full mac: 40:a8:f0:56:33:63 
Drives:    Local Storage: total: 1.25 TiB used: 136.64 GiB (10.7%) 
           ID-1: /dev/sda model: SPCC Solid State Disk size: 238.47 GiB 
           ID-2: /dev/sdb vendor: Western Digital model: WDS100T2B0A size: 931.51 GiB 
           ID-3: /dev/sdc vendor: PNY model: CS1311 120GB SSD size: 111.79 GiB 
Partition: ID-1: / size: 23.71 GiB used: 5.50 GiB (23.2%) fs: ext4 dev: /dev/sdb2 
           ID-2: /home size: 886.32 GiB used: 131.13 GiB (14.8%) fs: ext4 dev: /dev/sdb4 
           ID-3: swap-1 size: 5.59 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb3 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: amdgpu temp: 20 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1059 
Info:      Processes: 224 Uptime: 1m Memory: 15.56 GiB used: 510.0 MiB (3.2%) Shell: bash inxi: 3.0.32

Anyone have suggestions on what to tinker with to get this going?

Thanks

Last edited by willbprogz227 (2019-11-28 02:08:56)

pAtchSavage87 · 2019-11-28 02:03:42

It's not a solution per se, but from your debian install, can you enable verbose boot messages and try again? Should show you the device where you get hung up, which would be useful information as far as getting started goes.

IIRC you can do this by changing/commenting out the existing value of GRUB_CMDLINE_LINUX_DEFAULT, replacing it with GRUB_CMDLINE_LINUX_DEFAULT="" in /etc/default/grub, then running update-grub.

willbprogz227 · 2019-11-28 02:05:28

I found the problem, by accident, by attempting to boot into recovery mode. With the more verbose startup messages, I saw that the system was getting stuck on initializing my video card. This is not a very good failure mode, though. I believe on Debian it gives you a brief message at startup to install the proper video firmware and then keeps booting after that.

I chrooted into the Devuan install and installed firmware-amd-graphics then tried to boot into Devuan again and it worked! Yay! Hopefully this helps others if they have another Linux partition and can chroot in to fix the problem.

Thanks!

willbprogz227 · 2019-11-28 02:06:41

pAtchSavage87 wrote:

It's not a solution per se, but from your debian install, can you enable verbose boot messages and try again? Should show you the device where you get hung up, which would be useful information as far as getting started goes.
IIRC you can do this by changing/commenting out the existing value of GRUB_CMDLINE_LINUX_DEFAULT, replacing it with GRUB_CMDLINE_LINUX_DEFAULT="" in /etc/default/grub, then running update-grub.

Thanks so much! I did this by accident, so it helped solve the problem. I really appreciate your help!

willbprogz227 · 2019-11-28 21:02:46

I'd like to file a bug report about this, but I'm uncertain if I should file against udev or eudev. Any suggestions?

fsmithred · 2019-11-29 03:48:19

File the bug report against eudev.

willbprogz227 · 2019-11-29 04:30:17

fsmithred wrote:

File the bug report against eudev.

Thank you

The officially official Devuan Forum!

#1 2019-11-28 01:46:04

[Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

#2 2019-11-28 02:03:42

Re: [Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

#3 2019-11-28 02:05:28

Re: [Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

#4 2019-11-28 02:06:41

Re: [Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

#5 2019-11-28 21:02:46

Re: [Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

#6 2019-11-29 03:48:19

Re: [Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

#7 2019-11-29 04:30:17

Re: [Resolved] Boot hangs at 'Waiting for /dev to be fully populated'

Board footer