Ubuntu
s390-tools package

zipl without stand-alone /boot fails.

Bug #1543514 reported by Dimitri John Ledkov on 2016-02-09

This bug report is a duplicate of: Bug #1541575: zipl-installer: set up re-IPL to boot newly installed Ubuntu/Linux. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	s390-tools (Ubuntu)	New	Undecided	Dimitri John Ledkov

Bug Description

As per:

https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1541510/comments/18

zipl instalaltion fails, onto lvm2 without a standalone /boot.

But I thought that should be working now. To check.

Tags:

bugproxy (bugproxy) on 2016-02-10

tags:

added: architecture-s39064 bugnameltc-136898 severity-medium targetmilestone-inin1604

Revision history for this message

bugproxy (bugproxy) wrote on 2016-02-11: Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-02-11 11:28 EDT-------
(In reply to comment #3)
> As per:
>
> https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1541510/comments/18
>
> zipl instalaltion fails, onto lvm2 without a standalone /boot.
>
> But I thought that should be working now. To check.

It is hard to tell if it works or not unless the syslog is available for checking the zipl output messages.

Revision history for this message

bugproxy (bugproxy) wrote on 2016-02-11:

------- Comment From <email address hidden> 2016-02-11 12:11 EDT-------
(In reply to comment #4)

I just reproduced the issue and attached the log files for that.

I created one partition on the DASD and installed LVM on that using Manual partitioning. The installation fails at "Install the ZIPL boot loader on a hard disk", as described.

Revision history for this message

bugproxy (bugproxy) wrote on 2016-02-11: Syslog, partman log, hardware-summary

Syslog, partman log, hardware-summary Edit (580.0 KiB, application/x-tar)

------- Comment (attachment only) From <email address hidden> 2016-02-11 12:05 EDT-------

Revision history for this message

bugproxy (bugproxy) wrote on 2016-02-12: Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-02-12 03:16 EDT-------
Hi Michael,

(In reply to comment #6)
> (In reply to comment #4)
>
> I just reproduced the issue and attached the log files for that.
>
> I created one partition on the DASD and installed LVM on that using Manual
> partitioning. The installation fails at "Install the ZIPL boot loader on a
> hard disk", as described.

could you explain if you used a specific LVM setup. If /boot is on an LVM then the LVM must be linear mapped in order to IPL from an underlying device. If striping is used or other stuff, a separate /boot must be used.

Thanks.

Revision history for this message

bugproxy (bugproxy) wrote on 2016-02-12:

------- Comment From <email address hidden> 2016-02-12 04:09 EDT-------
Hi Hendrik,

(In reply to comment #7)
> Hi Michael,
>
> (In reply to comment #6)
> > (In reply to comment #4)
> >
> > I just reproduced the issue and attached the log files for that.
> >
> > I created one partition on the DASD and installed LVM on that using Manual
> > partitioning. The installation fails at "Install the ZIPL boot loader on a
> > hard disk", as described.
>
> could you explain if you used a specific LVM setup. If /boot is on an LVM
> then the LVM must be linear mapped in order to IPL from an underlying
> device. If striping is used or other stuff, a separate /boot must be used.
>
> Thanks.

this is my configuration:

DASD 0.0.5d32 (ECKD) - 7.4 GB IBM S390 DASD drive
> #1 7.4 GB K lvm
> 49.2 kB FREE SPACE
LVM VG rootVG, LV rootLV - 7.4 GB Linux device-mapper (linear)
> #1 7.4 GB f ext4 /

I basically used the whole partition on the DASD as physical volume for LVM

Revision history for this message

bugproxy (bugproxy) wrote on 2016-02-12:

------- Comment From <email address hidden> 2016-02-12 05:46 EDT-------
Hi all,

(In reply to comment #8)
> (In reply to comment #7)
> > Hi Michael,
> >
> > (In reply to comment #6)
> > > (In reply to comment #4)
> > >
> > > I just reproduced the issue and attached the log files for that.
> > >
> > > I created one partition on the DASD and installed LVM on that using Manual
> > > partitioning. The installation fails at "Install the ZIPL boot loader on a
> > > hard disk", as described.
> >
> > could you explain if you used a specific LVM setup. If /boot is on an LVM
> > then the LVM must be linear mapped in order to IPL from an underlying
> > device. If striping is used or other stuff, a separate /boot must be used.
> >
> > Thanks.
>
> this is my configuration:
>
> DASD 0.0.5d32 (ECKD) - 7.4 GB IBM S390 DASD drive
> > #1 7.4 GB K lvm
> > 49.2 kB FREE SPACE
> LVM VG rootVG, LV rootLV - 7.4 GB Linux device-mapper (linear)
> > #1 7.4 GB f ext4 /
>
> I basically used the whole partition on the DASD as physical volume for LVM

After some testing and debugging, we identified the root cause of this problem.

The device mapper zipl helper program fails to correctly identify the DASD device that is part of the LVM mapped device. This is because the sysfs is not mounted in the target system. The zipl-installer runs zipl with a chroot in the target system but mounts only proc prior to the zipl call. The /dev is mounted generally, but sysfs is mounted.

A problem fix is already available for this issue but in the context of supporting re-IPL into the newly installed target system. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813506 which is tracked via LTC Bug 136526 - LP1541575 : zipl-installer: set up re-IPL to boot newly installed Ubuntu/Linux

I will reject this is a duplicate of 136526.

*** This bug has been marked as a duplicate of bug 136526 ***