IPL from the reader using the installation kernel and initrd. Insmod the DASD driver and mount your file systems. Get the network up. Copy the kernel RPM from one of the other systems to the failed one. Chroot to your root file system. Install the RPM. Run zipl. Do a "depmod -a 2.4.21-292-default" command. Exit the chroot, unmount your file systems, and reboot from DASD.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Nix, Robert P. Sent: Wednesday, July 13, 2005 9:03 AM To: [email protected] Subject: Could not get a valid interface name... Our hardware people moved all the penguins to new DASD last night, so we took then all down, along with the two zVMs. When the copying was done, both zVMs came back up without problem, along with all the penguins... Except one. The one zLinux image comes up, but gets the following messages during the boot: Setting up network interfaces: lo ..done hsi0 Ifup: Could not get a valid interface name: -> skipped ..failed I tried ifup hsi0, and it fails the same way. I logged the image out and tried to bring it up from scratch, with the same result. This image was running and using hsi0 before it and the zVM system was brought down. All the other images running on this box are up and communicating. This image is SuSE SLES 8 31 bit, and others of its type are running fine. Redhat, SLES 8 64 bit and SLES 9 64 bit images are running fine. A Q LAN DETAILS shows the image, but not details about it. It does not show up in a Q LAN ACTIVE. /proc/modules does not list the qeth or qdio modules. I'm also getting the following message repeatedly, which might be related: linux modprobe: modprobe: Can't open dependencies file: /lib/modules/2.4.21-292-default/modules.dep (No such file or directory) That directory does not exist, but a 2.4.21-217-default does. This would point to a failed maintenance installation. Copying the 217 directory to the 292 one does not change the problem, with the exception that I get one new message while trying to run ifup hsi0: linux modprobe: modprobe: Can't locate module char-major-10-224 So.... Is there anything I can do, short of re-installing Linux, that could revive this penguin? (Sorry to be so long winded) -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." ---------------------------------------------------------------------- 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
