Roberto:

There are two things you can try:

The right way is to boot the system off CD, mount all the devices, do a chroot 
to your disks, fix /etc/zipl.conf, do "mkinitrd ; zipl", and then shut 
everything down.  Suse describes it in detail at 
https://www.suse.com/support/kb/doc/?id=7018376

The quick way assumes your boot partition isn't part of the LVM group and that 
you have a rescue system that's very similar to the one that's down.  Mount the 
boot partition to a rescue system (say at /mnt).  Then move some things around:
        # mv /boot /boot.orig
        # ln -s /mnt/boot /boot
        # cp -p /etc/zipl.conf /etc/zipl.conf.bak
Edit /etc/zipl.conf as needed for the new disks.
        # mkinitrd ; zipl
        # rm /boot ; mv /boot.org /boot
        # mv /etc/zipl.conf /etc/zipl.conf.rescue ; mv /etc/zipl.conf.bak 
/etc/zipl.conf
Then unmount and detach the disk from the rescue system.  Make sure the rescue 
system is okay:
        # mkinitrd ; zipl
The two systems have to be running the same kernel and this , but so far I've 
gotten away with it.  

PLEASE:  read all the steps and think through them before you run.  Much of 
this is pasted from my notes, but I haven't had to mess with zipl.conf when 
doing this.

Ted Rodriguez-Bell
[email protected]
Mainframe and Midrange Services, Wells Fargo

Company policy requires:  This message may contain confidential and/or 
privileged information.  If you are not the addressee or authorized to receive 
this for the addressee, you must not use, copy, disclose, or take any action 
based on this message or any information herein.  If you have received this 
message in error, please advise the sender immediately by reply e-mail and 
delete this message.  Thank you for your cooperation.


-----Original Message-----
From: Roberto Ibarra Magdaleno <[email protected]> 
Sent: Thursday, August 15, 2019 6:48 PM
Subject: Defined minidisks RHEL 6.0 on z/VM to grow / FS, forgot to 
Persistently Setting DASDs Online with /etc/zipl.conf and zipl.

Hello all,

I defined 2 new z/VM 6.2.0 minidisks for a RHEL 6.0 VM to grow / FS,
everything went right except I forgot to Persistently Setting DASDs Online
with /etc/zipl.conf and zipl. Got "Refusing activation of partial LV
lv_root. Use --partial to override." in next IPL. Since the kernel is not
finding those two new DASDs:

…

Linux version 2.6.32-71.el6.s390x ([email protected])
(gcc

 version 4.4.4 20100726 (Red Hat 4.4.4-13) (GCC) ) Ñ1 SMP Wed Sep 1
01:38:33 EDT

 2010


setup: Linux is running as a z/VM guest operating system in 64-bit
mode

…

dracut: Couldn't find device with uuid
Pb3hop-nG8p-hZKF-YkcL-N7nC-NsHa-1ZMhR7.

dracut: Couldn't find device with uuid
Yyw4vu-q8l9-MlCf-DZWF-mJLM-l8Mu-62xX3I.

dracut: inactive '/dev/vg_rh60/lv_root' ^21.52 GiB!
inherit

dracut: inactive '/dev/vg_rh60/lv_swap' ^7.77 GiB!
inherit

dracut: Couldn't find device with uuid
Pb3hop-nG8p-hZKF-YkcL-N7nC-NsHa-1ZMhR7.

dracut: Couldn't find device with uuid
Yyw4vu-q8l9-MlCf-DZWF-mJLM-l8Mu-62xX3I.

dracut: Refusing activation of partial LV lv_root. Use --partial to
override.

dracut Warning: LVM vg_rh60/lv_root not found

…
No root device found

No root device found

Boot has failed, sleeping forever.

Tried to IPL with PARM DASD=, PARM RD_DASD=, but didn’t work either:

ÑCP I 200 PARM RD_DASD=0.0.0205 RD_DASD=0.0.0206

…

Kernel command line: root=/dev/mapper/vg_rh60-lv_root rd_DASD=0.0.0200
rd_DASD=0

.0.0201 rd_DASD=0.0.0202 rd_DASD=0.0.0203 rd_DASD=0.0.0204
rd_LVM_LV=vg_rh60/lv_

root rd_LVM_LV=vg_rh60/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM
LANG=en_US.UTF-8 SYS

FONT=latarcyrheb-sun16 KEYTABLE=us cio_ignore=all,]0.0.0009
crashkernel=auto BOO

T_IMAGE=0 rd_dasd=0.0.0205 rd_dasd=0.0.0206




Help please!

TIA
Roberto Ibarra.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to