I usually get rid of cio_ignore every time I install a Linux guest (but sometimes I forget to). I think this parameter is usable only when you install Linux on a partition, and this partition can see every device on the mainframe. On a Linux guest, the only devices Linux can see is the devices we gave to it, so cio_ignore does nothing we haven't already done. But it can lead to a lot of confusion and scratched heads when we change a device.
Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. 2013/5/21 Mark Post <[email protected]> > >>> On 5/21/2013 at 04:25 AM, SrinivasG <[email protected]> wrote: > > Hi, > > > > I am getting error while doing an IPL of virtual Linux server. > > > > I have dumped the volumes of cloner server to the virtual server created. > > Dumping is successful > > > > Dumping volume 300 ,301 to virtual server volume 200, 201 using DDR(zVM > > dump/restore program) command in zVM > > > > After dumping, trying to IPL using the volume 200 and getting the > following > > error: > > > > ***************** > > dracut: dracut-004-283.el6 > > dracut: rd_NO_LUKS: removing cryptoluks activation > > device-mapper: uevent: version 1.0.3 > > device-mapper: ioctl: 4.22.6-ioctl (2011-10-19) initialised: > > [email protected] > > > > udev: starting version 147 > > dracut: Starting plymouth daemon > > dracut: rd_NO_DM: removing DM RAID activation > > dracut: rd_NO_MD: removing MD RAID activation > > dracut Warning: No root device "block:/dev/mapper/vg_mysgld-lv_root" > found > > dracut Warning: LVM vg_mysgld/lv_root not found > > dracut Warning: LVM vg_mysgld/lv_swap not found > > Others have pointed out that changing the virtual device numbers from > 200-201 to 300-301 will most likely fix this problem. (That's one of the > nice things about z/VM when doing cloning. You don't _have_ to change the > virtual device numbers.) > > However, I believe this problem is rooted in the cio_ignore kernel > parameter. LVM doesn't care what device numbers are used. It scans all > block devices not filtered out by /etc/lvm/lvm.conf, and looks for LVM > metadata. If the devices aren't even probed by the kernel at IPL time due > to cio_ignore, LVM won't have the chance to scan them later. > > > 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/
