Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
After installation and reipl, I did the following:
$ sudo chzdev -e 254d
ECKD DASD 0.0.254d configured
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.4.0-60-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Using config file '/etc/zipl.conf'
Ignore section 'old': Image file '/boot/vmlinuz.old'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Ignore #2: IPL section 'old'
Preparing boot device: dasda (154d).
Done.
$ sudo pvcreate /dev/dasdb1
WARNING: ext4 signature detected on /dev/dasdb1 at offset 1080. Wipe it? [y/n]:
y
Wiping ext4 signature on /dev/dasdb1.
Physical volume "/dev/dasdb1" successfully created
$ sudo vgextend s1lp7-vg /dev/dasdb1
Volume group "s1lp7-vg" successfully extended
$ sudo lvextend s1lp7-vg/root /dev/dasdb1
Size of logical volume s1lp7-vg/root changed from 38.89 GiB (9957 extents) to
80.16 GiB (20521 extents).
Logical volume root successfully resized.
$ sudo resize2fs /dev/mapper/s1lp7--vg-root
resize2fs 1.42.13 (17-May-2015)
Filesystem at /dev/mapper/s1lp7--vg-root is mounted on /; on-line resizing
required
old_desc_blocks = 3, new_desc_blocks = 6
The filesystem on /dev/mapper/s1lp7--vg-root is now 21013504 (4k) blocks long.
Which is activate another dasd drive; update initramfs; format physical
volume on the new drive's partition; extend volume group to include that
physical volume; extend root logical volume to use new the new physical
volume; and resize the root filesystem. Confirmed with df that root
filesystem is now twice as big.
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.
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-z-systems
Status: Triaged => Invalid
--
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
