------- Comment From [email protected] 2017-01-18 10:36 EDT-------
(In reply to comment #21)
> Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
> After installation and reipl, I did the following:

> $ sudo update-initramfs -u

I understand that things work with this explicit call.
However, users can easily miss this since it's not entirely obvious.

> At the end of all of this I have triggered a reboot; whilst watching
> Operating system messages. Reboot was completed successfully. Thus imho this
> bug is invalid.

> However, I do think that on Ubuntu systems "chzdev -e" should always trigger
> "initramfs-update -u" irrespective of what has been activated. Such that
> initramfs has as up-to-date udev rules as possible. Simply because it is
> impossible to predict at chzdev activation time whether or not something
> will be formated and added to become part of the rootfs backing devices or
> not.

Hm, good point. But then again, it would be suboptimal to have hundreds
of disks (paths) (or vNICs or other device types) activated early in
initramfs just because a few of the disks are actually required to mount
the root-fs (and that's all an initramfs should do). Alas, I don't know
how to solve it optimally.

(In reply to comment #18)
> I have now added zdev root update hook in zesty, such that chzdev will
> call update-initramfs -u.
> I will test the behaviour and will cherry-pick that as an SRU into
> xenial & yakkety.

I cannot quite follow why this bug is invalid.
I thought your above quoted code changes actually fixed this bug by not 
requiring the user to explicitly run  "update-initramfs -u" any more.
If the bug is now declared invalid as in "user error", then I'm puzzled about 
the reasons for a code change.

-- 
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

Reply via email to