Table of Contents
Advertisement
52.7 IBM System z: Using initrd as a
Rescue System
If the kernel of the SUSE® Linux Enterprise Server for IBM System z is upgraded or
modified, it is possible to reboot the system accidentally in an inconsistent state, so
standard procedures of IPLing the installed system fail. This most commonly occurs if
a new or updated SUSE Linux Enterprise Server kernel has been installed and the zipl
program has not been run to update the IPL record. In this case, use the standard instal-
lation package as a rescue system from which the zipl program can be executed to update
the IPL record.
52.7.1 IPLing the Rescue System
IMPORTANT: Making the Installation Data Available
For this method to work, the SUSE Linux Enterprise Server for IBM System z
installation data must be available. For details, refer to Section 2.1, "Making
the Installation Data Available" (Chapter 2, Preparing for Installation, ↑Architec-
ture-Specific Information) from Architecture-Specific Information. Additionally,
you need the channel number of the device and the partition number within
the device that contains the root file system of the SUSE Linux Enterprise
Server installation.
First, IPL the SUSE Linux Enterprise Server for IBM System z installation system as
described in the Architecture-Specific Information manual. A list of choices for the
network adapter to use is then presented.
Select 4 Start Installation or System then 3 Start Rescue System to start the rescue system.
Depending on the installation environment, you now must specify the parameters for
the network adapter and the installation source. The rescue system is loaded and the
following login prompt is shown at the end:
Skipped services in runlevel 3:
Rescue login:
You can now login as root without a password.
nfs nfsboot
Common Problems and Their Solutions
951
Advertisement
Table of Contents
Troubleshooting
