My tests on 18.04 beta 2 show that this is fixed.
Installed and configured a system like follows and it boots fine - hence
closing this ticket.
┌────────────────────────┤ [!!] Partition disks ├─────────────────────────┐
│ │
│ This is an overview of your currently configured partitions and mount │
│ points. Select a partition to modify its settings (file system, mount │
│ point, etc.), a free space to create partitions, or a device to │
│ initialize its partition table. │
│ │
│ - │
│ Multipath mpatha (WWID 36005076306ffd6b60000000000002600) - 68.7 ▒ │
│ > #1 primary 68.7 GB K lvm ▒ │
│ Multipath mpathb (WWID 36005076306ffd6b60000000000002601) - 68.7 0 │
│ > #1 primary 68.7 GB K lvm ▒ │
│ LVM VG rootvg, LV homelv - 100.0 GB Linux device-mapper (linear) ▒ │
│ > #1 100.0 GB f ext4 /home ▒ │
│ LVM VG rootvg, LV rootlv - 37.4 GB Linux device-mapper (linear) ▒ │
│ > #1 37.4 GB f ext4 / ▒ │
│ . │
│ │
│ <Go Back> │
│ │
└─────────────────────────────────────────────────────────────────────────┘
┌───────────────────────┤ [!!] Partition disks ├───────────────────────┐
│ │
│ If you continue, the changes listed below will be written to the │
│ disks. Otherwise, you will be able to make further changes manually. │
│ │
│ The partition tables of the following devices are changed: │
│ LVM VG rootvg, LV homelv │
│ LVM VG rootvg, LV rootlv │
│ │
│ The following partitions are going to be formatted: │
│ LVM VG rootvg, LV homelv as ext4 │
│ LVM VG rootvg, LV rootlv as ext4 │
│ │
│ Write the changes to disks? │
│ │
│ <Yes> <No> │
│ │
└──────────────────────────────────────────────────────────────────────┘
ubuntu@s1lp11:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
rootvg 2 2 0 wz--n- 127.99g 0
ubuntu@s1lp11:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/mpatha-part1 rootvg lvm2 a-- <64.00g 0
/dev/mapper/mpathb-part1 rootvg lvm2 a-- <64.00g 0
ubuntu@s1lp11:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/mpatha-part1 rootvg lvm2 a-- <64.00g 0
/dev/mapper/mpathb-part1 rootvg lvm2 a-- <64.00g 0
ubuntu@s1lp11:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync
Convert
homelv rootvg -wi-ao---- 93.13g
rootlv rootvg -wi-ao---- <34.86g
ubuntu@s1lp11:~$ sudo lvdisplay
--- Logical volume ---
LV Path /dev/rootvg/rootlv
LV Name rootlv
VG Name rootvg
LV UUID 7j6RLf-6G7U-f0ad-GSYD-XTqM-2xJX-PZOnr2
LV Write Access read/write
LV Creation host, time s1lp11, 2018-04-10 06:22:21 -0400
LV Status available
# open 1
LV Size <34.86 GiB
Current LE 8924
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4
--- Logical volume ---
LV Path /dev/rootvg/homelv
LV Name homelv
VG Name rootvg
LV UUID RxHMhS-QahA-QJeS-4j6f-CcCV-94lW-eTATPk
LV Write Access read/write
LV Creation host, time s1lp11, 2018-04-10 06:22:33 -0400
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23842
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5
** Changed in: debian-installer (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ubuntu-z-systems
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680101
Title:
Installing the zipl boot loader fails because "/boot' is located on a
multi-target device-mapper device"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1680101/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
