Ibm System Z: Using Initrd As A Rescue System - Novell LINUX ENTERPRISE SERVER 10 SP2 - INSTALLATION AND ADMINISTRATION Installation Manual

Hide thumbs Also See for LINUX ENTERPRISE SERVER 10 SP2 - INSTALLATION AND ADMINISTRATION:
Table of Contents

Advertisement

3 Reinstall the boot loader using the following command sequence:
4 Unmount the partitions, log out from the "change root" environment, and reboot
51.7 IBM System z: Using initrd as a
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.
51.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 "Making the
Installation Data Available" (Chapter 2, Preparing for Installation, ↑Architecture-
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.
950
Installation and Administration
Apply fixes to the device mapping (device.map) or the location of the root
partition and configuration files, if necessary.
grub --batch < /etc/grub.conf
the system:
umount -a
exit
reboot
Rescue System

Advertisement

Table of Contents
loading

This manual is also suitable for:

Suse linux enterprise server 10 sp3

Table of Contents