At which point are you getting that error? If you do a fresh install then just add these dasds your virtual machine before initializing install process (attach or better define minidisks) and let the installator do the job. Installator should give you an option to add all your dasds into the lvm and partition it the way you want. If you do it this way, you shouldn’t have to go through all these steps we were talking about. These steps are only appropriate if you want to resize existing system. Or that’s exactly what you are doing but you are still getting an error? Gregory
> On Aug 11, 2015, at 9:30 PM, Howard V. Hardiman <hvhar...@ncat.edu> wrote: > > Okay.. Your help and advice is appreciated. I think I see the picture better > now. As a result, I am now starting a fresh install to do so with LVM. I > can create vg and lv's just fine (I think, yet to test completely). But I > get an error that says that zipl bootloader could not be downloaded onto the > device before the installation finishes. I thought that by creating a /boot > partition (100M) on a piece of the dasd not affected by LVM would do the > trick. But I get the same error.... Am I missing something here? > > If I proceed in the installation it says that I can manually boot with the > /vmlinuz kernel on partition /dev/dasda1 and root /dev/mapper/vg1-lv1 passed > as kernel argument. How do I do that? If it works, can I then load zipl or > some bootloader that will allow me to be able to ipl the OS like normal? > > HH > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen > Powell > Sent: Tuesday, August 11, 2015 8:39 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Adding DASD to a Debian guest > > On Tue, 11 Aug 2015 12:27:08 -0400 (EDT), Grzegorz Powiedziuk wrote: >> >> Make sure that when you restart linux, these dasd will automatically >> show up in /proc/dasd/devices. Stephen suggested over here creating >> these empty files in /etc/sysconfig/hardware - I don’t know about that. >> I have never done it this way (but I haven’t been using debian in many >> years and things might have changed). > > Debian uses sysconfig-hardware to configure the hardware and bring it online > at boot time. Other distributions, SUSE in particular, used to use > sysconfig-hardware but don't anymore. But Debian still does. > Creating the empty file in /etc/sysconfig/hardware is all that is necessary > for a DASD device. For other devices, a network device for example, the file > needs to have configuration data in it. If you're using a "plain vanilla" > Debian system, rebuilding the initial RAM file system after creating a file > in /etc/sysconfig/hardware is not necessary. > But if you have reconfigured things the way I do it, so that DASD is brought > online earlier (as I describe in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621080), then rebuilding > the initial RAM file system is necessary. But it never hurts to rebuild the > initial RAM file system. > > This should go without saying, but I'll say it anyway: the way I do it is not > supported by Debian! > > I also need to offer the disclaimer that I have never used LVM2 on Debian. > It's not that I have anything against it: I've just never needed to. > > -- > .''`. Stephen Powell <zlinux...@wowway.com> > : :' : > `. `'` > `- > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to lists...@vm.marist.edu 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/ > NOTICE: This e-mail correspondence is subject to Public Records Law and may > be disclosed to third parties. –– > NOTICE: This e-mail correspondence is subject to Public Records Law and may > be disclosed to third parties. –– ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
