Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 854

Table of Contents

Advertisement

WARNING: Limitations
Although you have full access to the files and applications of the installed sys-
tem, there are some limitations. The kernel that is running is the one that was
booted with the rescue system. It only supports essential hardware and it is
not possible to add kernel modules from the installed system unless the kernel
versions are exactly the same (which is unlikely). So you cannot access a sound
card, for example. It is also not possible to start a graphical user interface.
Also note that you leave the "change root" environment when you switch the
console with Alt + F1 to Alt + F6 .
Modifying and Reinstalling the Boot Loader
Sometimes a system cannot boot because the boot loader configuration is corrupted.
The start-up routines cannot, for example, translate physical drives to the actual locations
in the Linux file system without a working boot loader.
To check the boot loader configuration and reinstall the boot loader, proceed as follows:
1 Perform the necessary steps to access the installed system as described in
2 Check whether the following files are correctly configured according to the
3 Reinstall the boot loader using the following command sequence:
838
Deployment Guide
"Accessing the Installed System"
GRUB configuration principles outlined in
(page 405).
• /etc/grub.conf
• /boot/grub/device.map
• /boot/grub/menu.lst
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
(page 837).
Chapter 18, The Boot Loader
Section

Advertisement

Table of Contents
loading

This manual is also suitable for:

Linux enterprise desktop 10 sp2

Table of Contents