On 12.04.2016 17:40, Dimitri John Ledkov wrote: > Hello, > > On 12 April 2016 at 16:22, Martha McConaghy <[email protected]> wrote: >> Mark, >> >> I've been using the installer, so I don't get to see the underlying config >> files. I'll try it again and see if I can get to /etc/zipl.conf. The >> installer doesn't say why it can't write out ZIPL, just that it cannot. I >> tried partitioning /boot and formatting it ext2 (which is the way we do >> SLES12), then partitioning the rest of the volume as /. It doesn't seem to >> like that either. >> >> It is at least comforting to know I'm not the only one who has run into this >> issue. >> > > I think we really should do stable release uploads in Debian of the > fixes to have LVM working on jessie for the next point release. > > Because clearly there are users after it like yourself =) > > Regards, > > Dimitri. > > The LVM on DASD issue should be resolved by bumping the release level of zipl-installer to either 0.0.28 or 0.0.32 (preferable) in the next point release. Since this addresses an installability problem, I would hope that such an update would be acceptable. >> Martha >> >> On Mon, 11 Apr 2016 17:25:05 -0600 Mark Post said: >>>>>> On 4/11/2016 at 07:00 PM, Martha McConaghy <[email protected]> wrote: >>>> I've been fighting with a Debian install all day and wonder if anyone else >>>> has run into the same problem. I wanted to use LVM for the root filesystem, >>>> so created a /boot partition and an LVM for the rest. Everything works >>>> fine >>>> until it comes to the step where it tries to write out ZIPL. That step >>>> fails. >>> >>> By "that step" do you mean something the installer is doing that you can't >>> tell >>> exactly what is happening? Or is it a command you're running yourself? >>> >>>> I tried all sorts of combinations, but the only that actually works is >>>> creating 1 partition for / with no LVM at all. Something is not right. >>> >>> While I don't personally care for this kind of setup, it should be fairly >>> straightforward. /boot needs to be mounted at the time zipl is run. It >>> needs >>> to have a file system of ext*, xfs, reiserfs, etc. on it, not something like >>> btrfs. >>> >>> What do the contents of /etc/zipl.conf look like? What are the messages >>> you're >>> getting back that indicate failure? >>> >>> >>> Mark Post >>> >>> ---------------------------------------------------------------------- >>> For LINUX-390 subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO LINUX-390 or >>> visit >>> http://www.marist.edu/htbin/wlvindex?LINUX-390 >>> ---------------------------------------------------------------------- >>> For more information on Linux on System z, visit >>> http://wiki.linuxvm.org/ >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> ---------------------------------------------------------------------- >> For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ > > > > -- > Regards, > > Dimitri. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ >
-- Mit freundlichen Grüßen/Kind Regards Viktor Mihajlovski IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martina Köderitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294
