Hi Calos, Hi sebastian,
most probably this is caused by the fact that your carbon copy of the dasd
has a different devno. The device
number of the dasd is in the kernel parameter line, which zipl stores on
preparation of the boot volume.
You can use the following workaround:
- attach the copy to a running linux guest
- enable it
$bash> echo "add <devno>" >/proc/dasd/devices
(you should see some messages on the console indicating that the
dasd was detected)
- look at /proc/dasd/devices to figure what device name it has (in this
example: dasdx)
- mount it on /mnt
$bash> mount /dev/dasdx1 /mnt
- look at /proc/mounts to verify that the dasd was mounted ok
- switch to the dasd as root device
$bash> chroot /mnt
- edit the parmfile (most probably in /boot/parmfile or similar, maybe in
/etc/zipl.conf - I am not sure where
SuSE puts their kernel parameters)
change the "dasd=<devno>" parameter to fit your new devno
- run zipl to prepare the volume for boot
- logout (to get out of the chroot jail) and log in again
- unmount the dasd
$bash> umount /mnt
- disable the dasd
$bash> echo "set <devno> off" >/proc/dasd/devices
- detach the dasd
- attach it back to the guest that should run it
- ipl
just FYI: with sles9 you can edit the parameters at ipl time, that makes
things much easier
with kind regards
Carsten Otte
--
omnis enim res, quae dando non deficit, dum habetur et non datur, nondum
habetur, quomodo habenda est
carlos <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
14/10/2004 09:45 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Cloning Linux systems problem
hello
----- Original Message -----
From: "Sebastian Welton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 03, 2004 6:51 PM
Subject: Cloning Linux systems problem
We have just installed SLES8 and require another 5 systems so using the
Redbook SLES8 under zVM as our guide we followed the instructions for
cloning. This suggests to use DDR to copy the disks which we dutifully
did.
However upon booting the new system the zVM user goes into a CP wait state
after the initial boot as it cannot read the partition table (dasda1.) As
this is running under FLEX we also tried using a ckdbackup piped into a
ckdrestore as its a lot quicker than DDR and the same problem occurred.
Have
we missed something or is there another way apart from having to install
each zLinux image one at a time?
Many thanks in advance...
MfG / Best Regards
Sebastian
----------------------------------------------------------------------
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
