Well if the boot fails because the root device is not found, then you're getting stuck in the initrd, right?
Which means systemd has not been started - it's not in our initrd, unless you're experimenting with dracut? And, udev (nor the rules I mentioned above) is not responsible for *creating* the device. It just sets up the symlinks in /dev. So I would be looking closer at the kernel or initramfs-tools. Are there any messages in dmesg or so about failing to create dm nodes, or something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2102236 Title: plucky/s390x (with root disk on dm?) does not come up after kernel update + reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2102236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
