Hello everyone again, Mark,
I tried to IPL in rescue mode by doing these 2 configuration files: RESCUE PRM A1 root=/dev/ram0 ro ip=off ramdisk_size=40000 cio_ignore=all,]0.0.0009 inst.rescue CMSDASD=191 CMSCONFFILE=redhat.conf REDHAT CONF A1 DASD="200-206" HOSTNAME="linux8" NETTYPE="qeth" IPADDR="172.27.20.19" SUBCHANNELS="0.0.0900,0.0.0901,0.0.0902" NETMASK="255.255.0.0" GATEWAY="172.27.20.254" It does IPL the installation dialog but never the rescue system. What am I missing? TIA. Regards. Roberto. El vie., 16 de ago. de 2019 a la(s) 14:38, Roberto Ibarra Magdaleno ( [email protected]) escribió: > Hello Mark, > > Tried adding the DASDs in the IPL command, same result: > > *CP I 200 PARM RD_DASD=0.0.0205 > RD_DASD=0.0.0206 * > > zIPL v1.8.2-28.el6 interactive boot > menu > > > > > 0. default > (linux) > > > 1. > linux > > > Note: VM users please use 'Ñcp vi vmsg > <input>' > > Please choose (default will boot in 5 > seconds): > > Booting default > (linux)... > > Initializing cgroup subsys > cpuset > > Initializing cgroup subsys > cpu > > 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 > > … > > dasd-eckd 0.0.0204: DASD with 4 KB/block, 7212240 KB total size, 48 > KB/track, co > > mpatible disk > layout > > dasde:VOL1/ VM941C: > dasde1 > > dracut: Scanning devices dasda1 dasdb2 dasdc1 dasdd1 dasde1 for LVM > logical vol > > umes vg_rh60/lv_root > vg_rh60/lv_swap > > 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: Refusing activation of partial LV lv_root. Use --partial to > override. > > dracut Warning: LVM vg_rh60/lv_root not > found > > > > > Boot has failed, sleeping > forever. > > > > Also tried DASD=, rd.DASD= and had the same result. > > About your good recommendations: > > >My preferred way of fixing problems like this is either > >1. Have a rescue system laying around that can be IPLed. > > Have one, working from it to make 3. > > >2. Boot from the installation kernel and initrd. > > Haven’t done it, hoping not to have to. Can I zipl with this? > > >3. Log the guest off and attach the disks(s) to another, running system,. > > Working on this from 1. Mounted its first DASD (200) and could read it, > didn’t found the /etc/dasd.conf needed. > > Linked second DASD (201) tried to mount it, and couldn´t: > > [root@rescue ~]# mount -t ext4 /dev/dasdf1 /lx8/20x > > mount: wrong fs type, bad option, bad superblock on /dev/dasdf1, > > missing codepage or helper program, or other error > > In some cases useful info is found in sysl > > Any advice? > > Thanks again. > Roberto. > > > > > El vie., 16 de ago. de 2019 a la(s) 12:13, Mark Post ([email protected]) > escribió: > >> On 8/16/19 9:32 AM, Dan Horák wrote: >> > I think the kernel cmdline parameters are case sensitive, so using >> > something like >> > #cp vi vmsg 1 rd_DASD=210 rd_DASD=211 >> > on the console to manually select the boot entry might fix the problem >> >> It's might easier and less guess-intensive if you put that on the IPL >> command: >> >> ipl devno parm rd_DASD=210 ... >> >> My preferred way of fixing problems like this is either >> 1. Have a rescue system laying around that can be IPLed. >> 2. Boot from the installation kernel and initrd. >> 3. Log the guest off and attach the disks(s) to another, running system,. >> >> Mark Post >> >> ---------------------------------------------------------------------- >> 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
