"Post, Mark K" wrote:
> From: Scully, William [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 26, 2002 9:52 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Enlarging Root File System
>
>
> Here's my zipl configuration file. Note that we normally boot off the 201
> (/dev/dasda1) device, and the new larger disk was added at address 20E
> (/dev/dasd01). To put the new disk into production I swapped 201 and 20E
> via the VM Directory.
>
>
> [defaultboot]
> default=ipl
>
> [ipl]
> target=/mnt/boot/zipl
> image=/mnt/boot/kernel/image
> #ramdisk=/boot/initrd
> parameters="dasd=0200-21f root=/dev/dasdo1 noinitrd"
>
> [dumptape]
> target=/boot
> dumpto=/dev/rtibm0
>
>
> It was placed into production using the command: zipl -c /etc/zipl.new.root
> On further investigation (and from a suggestion off-list from Willem
> Konynenberg) I suspect that I have the "parameters" value incorrect, as this
> seems to be the only explaination of what's gone wrong here. Since I'm
> working with a production server I can't bounce and test at will. (The
> changes must be scheduled.) If someone can confirm this suspicion that
> would be very helpful to me.
Yes, confirmed.
Some of the data in the zipl config file are being used at the
time you run the zipl utility, and they must reflect the situation
at the time the zipl utility runs. Other data (e.g. the kernel
command line) is being used at the time the kernel boots, and they
must reflect the situation at the time the kernel boots.
Normally, both situations are the same, and thus there is no
confusion, but in this particular case, you change the configuration
between these two steps, and you have to take that into account.
By the time the kernel boots and interprets that command line,
the root filesystem you want it to mount is located at /dev/dasda1,
not /dev/dasdo1.
--
Willem Konynenberg <[EMAIL PROTECTED]>
Konynenberg Software Engineering
