What are the contents of those rules? The names are very cryptic and give me no indication of whether they are relevant here or not.
Maybe a red herring, but... This is reminding me about https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2044104. Are those rules generated/managed/whatever by chzdev? Because udev's initramfs hook specifically ignores those when copying rules into the initramfs: $ cat debian/extra/initramfs-tools/hooks/udev ...SNIP... # See if chzdev can filter out generated rules, per LP: #2044104 ZDEV_FILTERING=0 if [ -e /usr/sbin/chzdev ] && \ dpkg --compare-versions "$(dpkg-query -f '${Version}' -W s390-tools 2> /dev/null)" '>=' '2.33.0'; then ZDEV_FILTERING=1 fi # now copy all custom udev rules which don't have an equivalent in /usr/lib (e. g. # 70-persistent-net.rules or similar); They might contain network names or # other bits which are relevant for the initramfs. for rules in /etc/udev/rules.d/*.rules; do if [ ! -e "$rules" ]; then continue fi # Skip rules generated by chzdev as they are handled by its own hook. # See LP: #2044104 if [ $ZDEV_FILTERING -eq 1 ] && /usr/sbin/chzdev --is-owner "$rules"; then continue; fi if [ ! -e "/usr/lib/${rules#/etc/}" ]; then cp -p "$rules" "$DESTDIR/usr/lib/udev/rules.d/" fi done ...SNIP... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2102236 Title: plucky/s390x (with root disk on dm?) does not come up after kernel update + reboot Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: While using the plucky daily from March 12 (that still comes with kernel 6.12) (and working around LP#2101831, by forcing the installation to not apply any updates) I get a system installed, which is at kernel level 6.12. Since 6.14 is out (in plucky release) since yesterday (March 12th) I tried to upgrade from 6.12 to 6.14, and the update itself seemed to be smooth (I couldn't find any errors while doing a full-upgrade in the terminal - see attached logs). But after executing a reboot, the system (in 3 different configurations, that use dm) does not come up again, and ends up in busybox, complaining that the root device couldn't be found: # s1lp15 FCP/SCSI multipath with LVM ALERT! /dev/disk/by-id/dm-uuid-LVM-SlleSC5YA825VOM3t0KHBVFrLJcNWsnwZsObNziIB9Bk2mSVphnuTEOQ2eFiBbE1 does not exist. Dropping to a shell! # s1lp15 2DASDs with LVM: ALERT! /dev/disk/by-id/dm-uuid-LVM-ePTbsojYPfgMacKXwpIMNMvxk80qGzlPhRYw7DJlovmqHyla9TK6NGc70p1JN29b does not exist. Dropping to a shell! # s1lp15 FCP/SCSI Multipath no LVM ALERT! /dev/disk/by-id/dm-uuid-part1-mpath-36005076306ffd6b60000000000002603 does not exist. Dropping to a shell! However, using a single disk without dm (so: no multipath, no lvm) the system is able to come up again after the reboot (after a kernel upgrade). # s1lp15 single DASD no LVM here the root device is: root=/dev/disk/by-path/ccw-0.0.260b-part1 and it exists. In the 3 different cases that (that repeatedly fail) "/dev/disk/by-id" is missing. I am not sure yet what's causing this, it can be an issue with the device-mapper/lvm2 but also udev rules or kernel. So maybe I need to add the kernel as affected component too (for now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2102236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
