I would say give it a try on the new LPAR. When you think about it, the only DASD volume that zipl _can_ write to is the current one, 322B. It cannot access 322E.
One way to simplify this, and feel better about the end results, would be to make the 322E volume accessible to your current system, copy things over, chroot to it, and run mkinitrd and zipl from there. I do have a pending HOWTO on cloning Linux systems in LPARs, but I haven't had time to get it formatted properly. If what you've done so far didn't really work, I could send it to you. Contact me off-list if necessary. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Russell Sent: Friday, January 12, 2007 11:33 AM To: [email protected] Subject: Migrate Linux to different LPAR We have recently installed CentOS Linux on our test Linux LPAR. We would like to migrate it to our production LPAR without having to do a new install. CentOS is intalled on a single dasd volume. We would like to simply copy the volume and IPL to the new volume on the new LPAR. The problem is that after we IPL on the new volume, Linux is still pointing to the file system on the old volume. This is the process that we followed to try to change the dasd volume that Linux uses. - change /etc/modprode.conf o changed "options dasd_mod dasd=322B" to "options dasd_mod dasd=322C" - run mkinitrd to pick up the changes to modprobe.conf o mkinitrd -v initrd-2.6.9-42.0.2.EL.img 2.6.9-42.0.2.EL o this showed the line "Loading module dasd_mod with options dasd=322C" so it seemed like changes were picked up. - run zipl command o zipl -V o contents of zipl.conf looks like this: * [defaultboot] * default=linux * target=/boot/ * [linux] * image=/boot/vmlinuz-2.6.9-42.0.2.EL * ramdisk=/boot/initrd-2.6.9-42.0.2.EL.img * parameters="root=/dev/VolGroup00/LogVol00" Output from zipl contained the following messages: DASD device number..............: 322b Preparing boot device: dasda (322b). Those messages lead me to believe that it is still pointing to the old dasd address. The plan was to make the dasd address changes, copy the volume, and then set the dasd address back to the original address on the old system, and IPL the new volume in the new LPAR. Is there something that I am missing? Is there and easier way to clone a linux system in a different LPAR? I appreciate any suggestions. Thanks, Russell Jones ANPAC System Programmer ---------------------------------------------------------------------- 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
