Yes that was the issue, 0.0.0009 was there twice, (my fat finger). I fixed that. Have another question. When you receive the file with VMUR, to comes across with NETDATA format. How can I convert that to ASCII?
Thanks Scott -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Malcolm Beattie Sent: Tuesday, March 05, 2013 11:01 AM To: [email protected] Subject: Re: Issues using VMUR Shumate, Scott writes: > Contents of /etc/zipl.conf [...] > parameters="root=/dev/mapper/VolGroup00-lv_root rd_DASD=0.0.0701 > rd_DASD=0.0.0700 rd_NO_LUKS rd_DASD=0.0.0702 LANG=en_US.UTF-8 rd_NO_MD > KEYTABLE=us cio_ignore=all,!0.0.0009,!0.0.000c rd_LVM_LV=VolGroup00/lv_root > SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=VolGroup00/lv_swap > rd_NO_DM" That shows the !0.0.000c and looks fine so 00c should be available after the next reboot, provided zipl is run after the edit and before rebooting. > Output from cat/proc/cmdline (I don't see !0.0.000c) > > [root@wil-zvmdb01 ~]# cat /proc/cmdline > root=/dev/mapper/VolGroup00-lv_root rd_DASD=0.0.0701 rd_DASD=0.0.0700 > rd_NO_LUKS rd_DASD=0.0.0702 LANG=en_US.UTF-8 rd_NO_MD KEYTABLE=us > cio_ignore=all,!0.0.0009,!0.0.0009 rd_LVM_LV=VolGroup00/lv_root > SYSFONT=latarcyrheb-sun16 crashkernel=auto > rd_LVM_LV=VolGroup00/lv_swap rd_NO_DM BOOT_IMAGE=0 This shows two copies of !0.0.0009 in place for the current boot. Since the original was cio_ignore=all,!0.0.0009 it looks as though an additional 0.0.0009 had been added giving cio_ignore=all,!0.0.0009,!0.0.0009 instead of the second one being !0.0.000c. I've just tried on an RHEL62 system with the exact same kernel as yours and !0.0.000c works fine for me. Any chance the second !0.0.0009 was added, then zipl run (which writes the change to the boot block) and only then was it noticed and changed to !0.0.000c without then rerunning zipl and rebooting? > Ouput from cio_ignore -l > > Ignored devices: > ================= > 0.0.0000-0.0.0008 > 0.0.000a-0.0.000b > 0.0.000d-0.0.06ff This, though, shows that 00c is not being ignored and should be usable at the moment. Given that it isn't in the kernel cmdline shown above for the current boot, it must have dynamically set via a cio_ignore command done directly or indirectly. RedHat uses various scripts triggered from udev hot-plug rules to fiddle with cio_ignore for things like dasd but I hadn't thought they'd done anything as polished for vmur. > Output from zipl > > [root@wil-zvmdb01 ~]# zipl > Using config file '/etc/zipl.conf' > Run /lib/s390-tools/zipl_helper.device-mapper /boot/ Building bootmap > in '/boot/' > Building menu 'rh-automatic-menu' > Adding #1: IPL section 'linux-2.6.32-220.el6.s390x' (default) > Preparing boot device: dasdb. > Done. Running zipl doesn't just tell you the current configuration, it writes the current zipl.conf settings into the boot block to be used for the next reboot. It looks as though maybe some of the various steps and tests (dynamic cio_ignore, editing zipl.conf, running zipl, rebooting, seeing /proc/cmdline and the current cio_ignore table and accessing the device) weren't in the intended order. If (1) zipl.conf really does have the !0.0.000c in it as shows (2) and zipl has been run after that change was made then you should find that after the next reboot you see the newly stamped setting via /proc/cmdline and the corresponding omission of 0.0.000c in the output from cio_ignore -l. --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK ---------------------------------------------------------------------- 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/
