Sergey, When you run zipl (or zilo or silo), all the files referenced by the command _must_ reside on the volume you're trying to write to.
So, if you're trying to write the kernel to /dev/dasdg, for example, the kernel, parmfile, boot sector, etc., etc., all have to be on /dev/dasdg1. If they are not, you get strange error messages. So, create a directory on the volume you want to write to, say /bootg, copy all the files into it from /boot, and run your command from there. I seem to remember that the directory name has to be /boot as well, so you may need to rename /boot to /boot.old and /bootg to /boot, and _then_ run zipl/silo/zilo. After it works correctly, you can rename /boot to /bootg, and /boot.old to /boot. Mark Post -----Original Message----- From: Sergey Korzhevsky [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 12:37 PM To: [EMAIL PROTECTED] Subject: Re: zipl 20.06.2002 18:14:38 Rob van der Heij wrote: >At 16:57 20-06-02, Sergey Korzhevsky wrote: > >>How can i write kernel (and ramdisk) on a new disk with zipl? > >Look in the ISP/ASP Redbook for the rescue disk alternate kernel >process. The magic trick is the -r option to point to your initrd >but you may have to remove /etc/zipl.conf or very hard point it >to an empty file somewhere. Someone implement default as the fault. Can you give me example? I can't find, how can i say to zipl boot device. I try to use zilo, but i got some strange errors like "this file on disk 94/0 insteed of 94/24". 94/0 - my root, 94/24 - my new disk, i think. WBR, Sergey
