Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 190 — #216
i
i
i
i
i
i
i
i
6.5 S/390, zSeries: Using initrd as a
Rescue System
If the kernel of the SUSE LINUX Enterprise Server for S/390 and zSeries
is upgraded or modified, it is possible to reboot the system accidentally in
an inconsistent state, so standard procedures of IPLing the installed sys-
tem 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 installation
package as a rescue system from which the zipl program can be executed to
update the IPL record.
6.5.1 IPLing the Rescue System
Note
Making the Installation Data Available
For this method to work, the SUSE LINUX Enterprise Server
for S/390 and zSeries installation data must be available. For
details, refer to the chapter Making the Installation Data Available
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.
Note
First, IPL the SUSE LINUX Enterprise Server for S/390 and zSeries instal-
lation system as described in the Architecture-Specific Information manual. A
list of choices for the network adapter to use is then presented.
Select 0 for no network. The installation program terminates and the follow-
ing messages are printed:
Example 6.1: Output for No Network Adapter Selected
*** OK, NETWORK ACCESS WILL _NOT_ BE AVAILABLE. ***
You should be able to login via telnet/ssh now.
To restart network setup, enter:
190 6.5. S/390, zSeries: Using initrd as a Rescue System