On Thu, Feb 06, 2003 at 08:36:10AM -0600, James Melin wrote: > We are having a Disaster Recovery exercise in April. My boss thinks it > would be nifty if we could recover the 2.4 Linux system I just got > installed (with much help from you SMOONOL's - Secret Masters Of Obscure > kNowledge Of Linux).
... > So what is necessary after a CDL restore is done to new DASD in order to > IPL the Linux system? Is there an initrd that must be booted from the HMC > so that adjustments to the image may be done? Is there some OTHER way to > alter/access the CDL volume structure from OS/390 to make the changes > necessary to IPL? If we have to have the vendor operator performing initrd > boots and entering in the initial ramdisk information so that I could > telnet into the system and fix things that way. What you probably want is a bootable tape; make sure that, like most distros' IPL systems, you load the DASD driver as a module. Then just document, "after the system comes up, do: modprobe dasd dasd=vol1,vol2,vol3...." Where vol1,2,3, etc. are in the same order that the usual dasda, dasdb, etc. are defined in, but are the new device numbers. Now all your devices are online, and you should be able to do a manual "mount /dev/dasda /mnt"; mount the rest of your volumes wherever they belong (/mnt/usr, and so on). Then: chroot /mnt Now you're inside your system. cd /boot (or whereever you keep your parmfile) cp parmfile parmfile.original echo "new parmfile" > parmfile (where "new parmfile" is the same as the old one, but with your new device numbers) zipl exit Shutdown the rescue system and IPL from your new root DASD. Adam
