Re: Moving root to a new volume
For us non-VM aware users, can I assume that the command CP LINK causes the new root disk to be available -- aka online, to the original or (old/source) system? -Original Message- From: Tom Shilson [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 8:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving root to a new volume Here is a list of the steps I did to move my root disk. YMMV. Good Luck. Shut down my target system From a second system, CP LINK to the old root system and the new root disk dasdfmt -b 4096 -v -f /dev/dasdd [This prepares the disk to receive the data. ] fdasd -a -b 4096 /dev/dasdd mke2fs -j -b 4096 /dev/dasdd1 mount old root system as /oldroot mount new disk as /mnt cp --preserve=all --recursive /oldroot/* /mnt/ [There are two dashses before preserve and recursive] cd /mnt/etc Create the zipl.ths.conf file below. cd /mnt/sbin ./zipl -c /mnt/etc/zipl.ths.conf [You want to execute the copy of zipl on the target system] cd / [You need to get out of /mnt so you can umount it.] umount /mnt umount /oldroot CP DET the two minidisks Modify the directory of the targe system to swap the addresses of the old and new root disks. Boot the target system newroot/etc/zipl.ths.conf: # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters=dasd=201-20F root=/dev/dasda1 newroot/etc/fstab: /dev/dasda1 / ext3defaults 1 1 /dev/dasdc1 /homeext3defaults 1 2 /dev/dasdb1 /usr ext3defaults 1 2 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /procproc defaults 0 0 tom - - - - - - - - - - - - Toto, I have a feeling we're not in the mainframe world any more. _/) Tom Shilson ~GEDW VM System Services Aloha Tel: 651-733-7591 tshilson at mmm dot com Fax: 651-736-7689 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/28/2004 08:42:49 AM: Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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 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
Re: Moving root to a new volume
Hi, Yes, but In my example, I was making the old and new root disks available to a second system. In a follow-on note to mine, Mark Post gave an example of doing it all on one system. I suggest that you look at his method first. From Mark's Post Taking the system out of service for such a long period of time can easily be avoided by: 1. Adding the new disk to the existing system dynamically 2. Doing the same dasdmft, fdasd and mke2fs. 3. Following the HOWTO at http://linuxvm.org/Info/HOWTOs/movefs.html from steps 3 to 4, but doing the cd to /, instead of /usr. 4. chroot to /mnt 5. Update /etc/zipl.conf, but only if any device numbers will change. 6. Run zipl 7. exit the chroot environment 8. Unmount the new file system. 9. Reboot at the time of your choice. This also eliminates the need to modify all the other parameters in /etc/zipl.conf to remove the /mnt from the directory paths. Mark Post tom - - - - - - - - - - - - Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/29/2004 12:19:59 PM: For us non-VM aware users, can I assume that the command CP LINK causes the new root disk to be available -- aka online, to the original or (old/source) system? ...snip... -- 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
Re: Moving root to a new volume
Not exactly. It makes it available to CP for that z/VM guest. To make it accessible to CMS, you would do an access command (if it were CMS formatted). To make it available to Linux, you would need to go through the echo add device range=xxx /proc/dasd/devices routine. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 1:20 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving root to a new volume For us non-VM aware users, can I assume that the command CP LINK causes the new root disk to be available -- aka online, to the original or (old/source) system? -Original Message- From: Tom Shilson [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 8:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving root to a new volume Here is a list of the steps I did to move my root disk. YMMV. Good Luck. Shut down my target system From a second system, CP LINK to the old root system and the new root disk dasdfmt -b 4096 -v -f /dev/dasdd [This prepares the disk to receive the data. ] fdasd -a -b 4096 /dev/dasdd mke2fs -j -b 4096 /dev/dasdd1 mount old root system as /oldroot mount new disk as /mnt cp --preserve=all --recursive /oldroot/* /mnt/ [There are two dashses before preserve and recursive] cd /mnt/etc Create the zipl.ths.conf file below. cd /mnt/sbin ./zipl -c /mnt/etc/zipl.ths.conf [You want to execute the copy of zipl on the target system] cd / [You need to get out of /mnt so you can umount it.] umount /mnt umount /oldroot CP DET the two minidisks Modify the directory of the targe system to swap the addresses of the old and new root disks. Boot the target system newroot/etc/zipl.ths.conf: # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters=dasd=201-20F root=/dev/dasda1 newroot/etc/fstab: /dev/dasda1 / ext3defaults 1 1 /dev/dasdc1 /homeext3defaults 1 2 /dev/dasdb1 /usr ext3defaults 1 2 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /procproc defaults 0 0 tom - - - - - - - - - - - - Toto, I have a feeling we're not in the mainframe world any more. _/) Tom Shilson ~GEDW VM System Services Aloha Tel: 651-733-7591 tshilson at mmm dot com Fax: 651-736-7689 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/28/2004 08:42:49 AM: Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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 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 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
Moving root to a new volume
Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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
Re: Moving root to a new volume
On Dec 28, 2004, at 8:42 AM, Gene Walters wrote: Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? I'd do the following: mount /dev/newdisk /mnt cp -a -x / /mnt chroot /mnt mkinitrd (if required) zipl exit shutdown -h now Then swap the device addresses and IPL from the new volume. Adam -- 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
Re: Moving root to a new volume
Here is a list of the steps I did to move my root disk. YMMV. Good Luck. Shut down my target system From a second system, CP LINK to the old root system and the new root disk dasdfmt -b 4096 -v -f /dev/dasdd [This prepares the disk to receive the data. ] fdasd -a -b 4096 /dev/dasdd mke2fs -j -b 4096 /dev/dasdd1 mount old root system as /oldroot mount new disk as /mnt cp --preserve=all --recursive /oldroot/* /mnt/ [There are two dashses before preserve and recursive] cd /mnt/etc Create the zipl.ths.conf file below. cd /mnt/sbin ./zipl -c /mnt/etc/zipl.ths.conf [You want to execute the copy of zipl on the target system] cd / [You need to get out of /mnt so you can umount it.] umount /mnt umount /oldroot CP DET the two minidisks Modify the directory of the targe system to swap the addresses of the old and new root disks. Boot the target system newroot/etc/zipl.ths.conf: # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters=dasd=201-20F root=/dev/dasda1 newroot/etc/fstab: /dev/dasda1 / ext3defaults 1 1 /dev/dasdc1 /homeext3defaults 1 2 /dev/dasdb1 /usr ext3defaults 1 2 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /procproc defaults 0 0 tom - - - - - - - - - - - - Toto, I have a feeling we're not in the mainframe world any more. _/) Tom Shilson ~GEDW VM System Services Aloha Tel: 651-733-7591 tshilson at mmm dot com Fax: 651-736-7689 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/28/2004 08:42:49 AM: Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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
Re: Moving root to a new volume
Taking the system out of service for such a long period of time can easily be avoided by: 1. Adding the new disk to the existing system dynamically 2. Doing the same dasdmft, fdasd and mke2fs. 3. Following the HOWTO at http://linuxvm.org/Info/HOWTOs/movefs.html from steps 3 to 4, but doing the cd to /, instead of /usr. 4. chroot to /mnt 5. Update /etc/zipl.conf, but only if any device numbers will change. 6. Run zipl 7. exit the chroot environment 8. Unmount the new file system. 9. Reboot at the time of your choice. This also eliminates the need to modify all the other parameters in /etc/zipl.conf to remove the /mnt from the directory paths. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Tom Shilson Sent: Tuesday, December 28, 2004 11:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving root to a new volume Here is a list of the steps I did to move my root disk. YMMV. Good Luck. Shut down my target system From a second system, CP LINK to the old root system and the new root disk dasdfmt -b 4096 -v -f /dev/dasdd [This prepares the disk to receive the data. ] fdasd -a -b 4096 /dev/dasdd mke2fs -j -b 4096 /dev/dasdd1 mount old root system as /oldroot mount new disk as /mnt cp --preserve=all --recursive /oldroot/* /mnt/ [There are two dashses before preserve and recursive] cd /mnt/etc Create the zipl.ths.conf file below. cd /mnt/sbin ./zipl -c /mnt/etc/zipl.ths.conf [You want to execute the copy of zipl on the target system] cd / [You need to get out of /mnt so you can umount it.] umount /mnt umount /oldroot CP DET the two minidisks Modify the directory of the targe system to swap the addresses of the old and new root disks. Boot the target system newroot/etc/zipl.ths.conf: # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters=dasd=201-20F root=/dev/dasda1 newroot/etc/fstab: /dev/dasda1 / ext3defaults 1 1 /dev/dasdc1 /homeext3defaults 1 2 /dev/dasdb1 /usr ext3defaults 1 2 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /procproc defaults 0 0 tom - - - - - - - - - - - - Toto, I have a feeling we're not in the mainframe world any more. _/) Tom Shilson ~GEDW VM System Services Aloha Tel: 651-733-7591 tshilson at mmm dot com Fax: 651-736-7689 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/28/2004 08:42:49 AM: Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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 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
Re: Moving root to a new volume
Oh, and: 5.5 Re-run mkinitrd if needed as well I guess it may be time to update the HOWTO to take that into account. Mark Post -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 3:03 PM To: 'Linux on 390 Port' Subject: RE: Moving root to a new volume Taking the system out of service for such a long period of time can easily be avoided by: 1. Adding the new disk to the existing system dynamically 2. Doing the same dasdmft, fdasd and mke2fs. 3. Following the HOWTO at http://linuxvm.org/Info/HOWTOs/movefs.html from steps 3 to 4, but doing the cd to /, instead of /usr. 4. chroot to /mnt 5. Update /etc/zipl.conf, but only if any device numbers will change. 6. Run zipl 7. exit the chroot environment 8. Unmount the new file system. 9. Reboot at the time of your choice. This also eliminates the need to modify all the other parameters in /etc/zipl.conf to remove the /mnt from the directory paths. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Tom Shilson Sent: Tuesday, December 28, 2004 11:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving root to a new volume Here is a list of the steps I did to move my root disk. YMMV. Good Luck. Shut down my target system From a second system, CP LINK to the old root system and the new root disk dasdfmt -b 4096 -v -f /dev/dasdd [This prepares the disk to receive the data. ] fdasd -a -b 4096 /dev/dasdd mke2fs -j -b 4096 /dev/dasdd1 mount old root system as /oldroot mount new disk as /mnt cp --preserve=all --recursive /oldroot/* /mnt/ [There are two dashses before preserve and recursive] cd /mnt/etc Create the zipl.ths.conf file below. cd /mnt/sbin ./zipl -c /mnt/etc/zipl.ths.conf [You want to execute the copy of zipl on the target system] cd / [You need to get out of /mnt so you can umount it.] umount /mnt umount /oldroot CP DET the two minidisks Modify the directory of the targe system to swap the addresses of the old and new root disks. Boot the target system newroot/etc/zipl.ths.conf: # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters=dasd=201-20F root=/dev/dasda1 newroot/etc/fstab: /dev/dasda1 / ext3defaults 1 1 /dev/dasdc1 /homeext3defaults 1 2 /dev/dasdb1 /usr ext3defaults 1 2 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /procproc defaults 0 0 tom - - - - - - - - - - - - Toto, I have a feeling we're not in the mainframe world any more. _/) Tom Shilson ~GEDW VM System Services Aloha Tel: 651-733-7591 tshilson at mmm dot com Fax: 651-736-7689 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/28/2004 08:42:49 AM: Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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 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
Re: Moving root to a new volume
So much to learn I was worried that some change would be made to the original root disk and not picked up on the new root disk. tom Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/28/2004 02:03:15 PM: Taking the system out of service for such a long period of time can easily be avoided by: 1. Adding the new disk to the existing system dynamically 2. Doing the same dasdmft, fdasd and mke2fs. 3. Following the HOWTO at http://linuxvm.org/Info/HOWTOs/movefs.html from steps 3 to 4, but doing the cd to /, instead of /usr. 4. chroot to /mnt 5. Update /etc/zipl.conf, but only if any device numbers will change. 6. Run zipl 7. exit the chroot environment 8. Unmount the new file system. 9. Reboot at the time of your choice. This also eliminates the need to modify all the other parameters in /etc/zipl.conf to remove the /mnt from the directory paths. 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
