11.06.2004 00:58:16 Ranga Nathan wrote:
>I have a similar issue. We are on SLES8. I am testing DR scenario by
>snapshotting 5 volumes to another set and bring up Linux from the
backups.
>I gathered that zipl.conf need to be changed. But when? Obviously I could
>not do this when the zipl.conf on the new boot disk still points to the
>old boot partition.
>
>e.g
>zipl.conf now says....
>[ipl]
>target=/boot/zipl
>image=/boot/kernel/image
>ramdisk=/boot/initrd
>parameters="dasd=2300-230F root=/dev/dasda1"
>
>So when I IPL from the new volumes, he is going to look for /dev/dasda1
>and not find it!
>
>Like lilo, are there alternate configs possible? At the ops console, do
>any of these options come up?
>
Easy with new s390-tools.
I 750 CLEAR
zIPL v1.3.0 interactive boot menu
0. default (2.6.5-3)
1. 2.6.5-3
2. 2.6.5-2
3. 2.4.21-6
4. 2.6.5-2old
Note: VM users please use '#cp vi vmsg <input>'
Please choose (default will boot in 5 seconds):
#CP VI VMSG 1 ROOT=/DEV/DASDH1
....
From the man page of zipl:
If the 'prompt' setting of the menu section is set to 1, a
menu text will be displayed during IPL and the boot pro┤
gram will wait for user input:
zIPL interactive boot menu
0. default (linux)
1. linux
2. test
Please choose:
The menu prompt expects the configuration number as input.
Typing '0' will start the default configuration. Addi┤
tional kernel parameters can be specified by supplying
them after the configuration number, separated by a blank
character. Example input:
2 mem=128m maxcpus=1
This will start configuration 2 and append the string
"mem=128m maxcpus=1" to the existing kernel command line.
Note that the extra parameters are only temporary and
won't be saved for the next IPL process. Note also that
the selected configuration number will be available to the
init process through the environment variable named
BOOT_IMAGE.
VM users need to prefix all input with the VM VINPUT com┤
mand, e.g. type '#cp vinput vmsg 0' to boot the default
configuration.
WBR, Sergey
