[Bug 1680101] Re: Installing the zipl boot loader fails because "/boot' is located on a multi-target device-mapper device"

[Dimitri John Ledkov]

I have not reproduced this bug yet, if true, I will try to fix, but I
think it is too late to make onto 17.04 release media.

** Also affects: ubuntu-release-notes
   Importance: Undecided
       Status: New

** Changed in: ubuntu-release-notes
       Status: New => Confirmed

-- 
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:
  Confirmed
Status in Ubuntu on IBM z Systems:
  New
Status in debian-installer package in Ubuntu:
  New

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