This bug was fixed in the package systemd - 257.4-1ubuntu2
---------------
systemd (257.4-1ubuntu2) plucky; urgency=medium
[ Frank Heimes ]
* Fix d/extra/initramfs-tools/hooks/udev, so that udev rules that are
specific to s390x ccw devices are only prevented from being copied if
zdev_early=0 is set, but copy rules in case of zdev_early=1 or if
zdev_early is not specified at all. (LP: #2102236)
[ Nick Rosbrook ]
* d/extra/polkit-1: let root ignore inhibitors on reboot etc (LP: #2092438)
* d/control: remove Build-Depends: linux-tools-generic.
The src:linux package now ships a bpftool binary package.
-- Nick Rosbrook <en...@ubuntu.com> Fri, 21 Mar 2025 17:48:15 -0400
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
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 does not come up after kernel update + reboot, due to
udev rules missing in initrd
Status in Ubuntu on IBM z Systems:
New
Status in initramfs-tools package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
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
