This issues was rejected by Canonical, and closed as invalid on 2017-01-18.
This bug is incorrectly filed against src:linux, I will move it to src:s390-tools shortly. Further discussion is about upstream features. Canonical does not participate in s390-tools upstream development. It is absolutely normal to expect users to regenerate boot files after significantly modifying their root filesystem. On ubuntu `update- initramfs -u` regenerates initramfs and reruns zipl as needed on s390x. This is no different than from other Ubuntu platforms with different bootloaders. Further discussion is about providing new features and/or workarounds in upstream chzdev. Given that no external patches are accepted into s390-tools there is no meaningful way for me to participate in that discussion between upstream developers. My personal opinion is that adding new flags will not fix the user experience here (the user in the original user story already forgot update-initramfs -u, thus I'm not expecting the new flag to be used either) and that on Ubuntu we would not regenerate initramfs on shutdowns as that is somewhat risky. On ubuntu, we ship zdev-root-update hook, as per upstream recommendation, that calls appropriate commands on ubuntu to update initramfs/zipl, ie. update-initramfs -u. My personal opinion is that whenever persistent & activate configuration is modified together by chzdev, it must call zdev-root-update. Example: chzdev dasd 0.0.0.0200 -e call should exec zdev-root-update if 0200 was not previously configured in the persistent configuration. But this is something for upstream to implement / fix - the fact that zdev-root-update is not called often enough; not automatic enough under more conditions. Calling zdev-root-update by chzdev more often would improve usability of any Linux on z. ** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641078 Title: System cannot be booted up when root filesystem is on an LVM on two disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1641078/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
