[Bug 1680101] Re: Installing the zipl boot loader fails because "/boot' is located on a multi-target device-mapper device"
Frank Heimes
1680101 at bugs.launchpad.net
Tue Apr 10 15:48:17 UTC 2018
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 at s1lp11:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
rootvg 2 2 0 wz--n- 127.99g 0
ubuntu at 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 at 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 at 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 at 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
Foundations Bugs, which is subscribed to debian-installer in 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"
Status in Release Notes for Ubuntu:
Fix Released
Status in Ubuntu on IBM z Systems:
Fix Released
Status in debian-installer package in Ubuntu:
Fix Released
Bug description:
Installer version: 20101020ubuntu501
Kernel: 4.10.0-15
Description/Reproduction:
System is using two multipathed FCP-LUNs. A volume group is created
over these two LUNs and logical volumes for root and home are defined.
~ # vgs
VG #PV #LV #SN Attr VSize VFree
rootvg 2 2 0 wz--n- 39.99g 0
~ # pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/mpatha1 rootvg lvm2 a-- 20.00g 0
/dev/mapper/mpathb1 rootvg lvm2 a-- 20.00g 0
/dev/mapper/mpathc1 lvm2 --- 20.00g 20.00g
/dev/mapper/mpathd1 lvm2 --- 20.00g 20.00g
~ # lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
homelv rootvg -wi-ao---- 11.18g
rootlv rootvg -wi-ao---- 28.81g
The installer fails on "Install the ZIPL boot loader on a hard disk". In syslog you see the following errors:
Apr 5 12:39:49 zipl-installer: Root filesystem on /dev/mapper/rootvg-rootlv (/dev/mapper/rootvg-rootlv)
Apr 5 12:39:49 zipl-installer: info: Root filesystem is on LV ( rootvg rootlv)
Apr 5 12:39:49 zipl-installer: Error: Unsupported setup: Directory '/boot' is located on a multi-target device-mapper device
Apr 5 12:39:49 zipl-installer: Using config file '/etc/zipl.conf'
Apr 5 12:39:49 zipl-installer: Ignore section 'old': Image file '/boot/vmlinuz.old'
Apr 5 12:39:49 zipl-installer: Run /lib/s390-tools/zipl_helper.device-mapper /boot
Apr 5 12:39:49 zipl-installer: Error: Script could not determine target parameters
Apr 5 12:39:49 main-menu[355]: (process:17396): File descriptor 3 (pipe:[11141]) leaked on lvm invocation.
Apr 5 12:39:49 main-menu[355]: (process:17396): Parent PID 17397: /bin/sh
Apr 5 12:39:49 main-menu[355]: (process:17396): File descriptor 4 (/dev/pts/0) leaked on lvm invocation.
Apr 5 12:39:49 main-menu[355]: (process:17396): Parent PID 17397: /bin/sh
Apr 5 12:39:49 main-menu[355]: (process:17396): File descriptor 5 (/dev/pts/0) leaked on lvm invocation.
Apr 5 12:39:49 main-menu[355]: (process:17396): Parent PID 17397: /bin/sh
Apr 5 12:39:49 main-menu[355]: (process:17396): File descriptor 6 (/dev/pts/0) leaked on lvm invocation.
Apr 5 12:39:49 main-menu[355]: (process:17396): Parent PID 17397: /bin/sh
Apr 5 12:39:49 main-menu[355]: WARNING **: Configuring 'zipl-installer' failed with error code 1
Apr 5 12:39:49 main-menu[355]: WARNING **: Menu item 'zipl-installer' failed.
As the error message says, having the /boot partition on a device-mapper device is not supported. If that error is not a bug, then the partitioner should not allow having such a setup and display a warning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1680101/+subscriptions
More information about the foundations-bugs
mailing list