Mount your new root file system on /mnt. Mount your new boot file system on /mnt/boot. _Then_ "chroot /mnt" to do the rest of your work.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Dave Myers Sent: Wednesday, May 04, 2005 11:09 PM To: [email protected] Subject: Question using chroot with / and /boot partitions Here's the background before the question. We are attempting to clone a RHEL4 system (LPAR / NOT VM!) using DFDSS backup/restore. So (after the backup/restore) we need to change the DASD= device numbers in the newly restored system by mounting the new dasd to the source system (as /dev/dasdc1 and /dev/dasdc2) and then editing /etc/modprobe.conf. (Note: we used /dev/dasdb for some other user filesystem, thus the /dev/dasdc1 for the new mount) Our disk partition layout is: /boot /dev/dasda1 / /dev/dasda2 When we mounted the newly restored DASD, we mounted like this: /dev/dasdc1 /mnt /dev/dasdc2 /mnt2 So /mnt is the new /boot and /mnt2 is the new / Our problem/question is this: When we go to run the mkinitrd and zipl, we need to "chroot" to /mnt2, which works...but then when we try to mount /mnt in the new root so that we can get to the new /boot, it does not work. We think this is because in the newly cloned system, we did not have the new dasd device number (for dasdc) marked as ONLINE in the /sys filesystem... so the new root can not mount it. Is this correct? If so, is there a way to get around this problem? Thanks, Dave ---------------------------------------------------------------------- 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
