Boot Failure: Failed to start Create Static Device Nodes in /dev

[Ralf_E_aus_W]

Hi, folks!

I’m having trouble with my gaming PC running openSuse slowroll. I was trying to solve a problem with autologin when suddenly my PC did not but at all:

Using recovery mode I did check the mentioned journalctl status. But I’m no Linux pro and started using openSuse a few weeks ago trying to replace Windows with Linux on my gaming PC.

I installed openSuse slowroll about two weeks ago and besides this error it worked fine. I installed some updates on that day but I’m sure it booted fine at least once afterwards - except the autologin still not working.

Do you have any advice how to fix this? Any hints will be greatly appreciated!

[Ralf_E_aus_W]

[arvidjaar]

Boot any live image, provide output of lsblk -f -o +partuuid. Not as image, rather as preformatted text.

[ektus]

I’ve had similar symptoms recently with tumbleweed. The error message “waiting for disk” was not indicative of a hardware failure, but of some configuration glitch. My solution can be found in Boot stuck after tumbleweed upgrade: start task is running for disk - #19

[Ralf_E_aus_W]

NAME        FSTYPE   FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS     PARTUUID
loop0       squashfs 4.0                                                                              
loop1       squashfs 4.0                                                                              
loop2       squashfs 4.0                                                     0   100% /mounts/mp_0000 
loop3       squashfs 4.0                                                     0   100% /mounts/mp_0001 
loop4       squashfs 4.0                                                     0   100% /mounts/mp_0002 
loop5       squashfs 4.0                                                     0   100% /parts/mp_0000  
sda                                                                                                   
├─sda1      exfat    1.0   Ventoy 4E21-0000                                                           943774fc-01
│ └─ventoy                                                                                            
└─sda2                                                                                                
zram0                                                                                                 
nvme0n1                                                                                               
├─nvme0n1p1 vfat     FAT32        A6F1-573B                                                           5d6f224a-1fb5-4a4a-a755-da9c8df757ee
├─nvme0n1p2                                                                                           c077d3af-83d9-40b9-b738-993761d57488
├─nvme0n1p3 ntfs           System 18BAF222BAF1FBD6                      139.2G    30% /mnt            95845ea5-b235-4c37-935f-024e2b456dee
├─nvme0n1p4 ntfs                  763407F43407B5E1                                                    466499a8-6b08-4e20-b686-e94269416d0c
├─nvme0n1p5 btrfs                 9e867d45-ddb1-4dc7-8b5b-242305c10238                                d2cfe257-01b1-48cb-b89a-0f05c5f12754
└─nvme0n1p6 swap     1            4f40672f-33bc-4be2-bf2d-281471c54b68                                d7cc6559-b298-44db-b5d3-7e4f69713965

As you can see it is a dual boot system with Windows 11.
BTW: I already checked the ssd - no errors found.

[ektus]

Did you check /etc/nsswitch.conf already? In my case, the order of arguments did matter and led to very similar problems. The system would boot only in rescue mode, group information would be unavailable and I got lots of errors during boot. If it’s not the case for you, check the very first error (not warning, those may be plenty) in journalctl and go from there.

[Ralf_E_aus_W]

I have just checked it right now - and it worked! Thank you so much!

I already stumbled upon that thread before I started this one but because the OP had encrypted drives unlike me and because I did not understand much of the technical stuff it didn’t occur to me that your solution could be of any help in my case.

Solution:
I started my openSuse in recovery mode, entered my password and then edited the file /etc/nsswitch.conf:

nano /etc/nsswitch.conf

search for

group: [SUCCESS=merge] compat systemd

and change it into

group: compat [SUCCESS=merge] systemd

save the changes and

reboot

Done!
Thanks a lot!

The question that remains is: how did this happen?

[ektus]

You’re welcome

I suspect some update, either something altering the config file or some program that interprets said file. Probably the latter, as IIRC in my case that file hadn’t been altered for months prior to the error happening.