Part I. Installation / Chapter 5. System Repair | ||||
|---|---|---|---|---|
 | 4.3. RPM—the Package Manager | 5.2. User-Defined Repair |  | |
Part I. Installation / Chapter 5. System Repair | ||||
|---|---|---|---|---|
| 4.3. RPM—the Package Manager | 5.2. User-Defined Repair | | |
Table of Contents
Abstract
In addition to numerous YaST modules for system installation and configuration, SUSE LINUX also offers a feature for repairing the installed system. This chapter describes the various types and steps of system repair. The SUSE Rescue System can provide access to the partitions. An experienced system administrator can use it to repair a damaged system.
Because it cannot be assumed that a damaged system can boot by itself and a running system cannot be easily repaired, boot to repair the system as you would for a new installation. Follow the steps outlined in Chapter 1, Installation with YaST to get to the dialog offering the various installation options then select .
![[Important]](admon/important.png) | Using the Appropriate Installation Medium |
|---|---|
For the repair system to function properly, the installation medium used to boot the system should exactly match the installed system. | |
In the next step, choose how the system repair should be performed. Automatic repair, custom repair, and expert tools are available and are described in this chapter.
This method is intended for repairing a damaged system with unknown cause. Selecting it starts an extensive analysis of the installed system, which takes quite some time due to the large number of tests and examinations. The progress of the procedure is displayed at the bottom of the screen with two progress bars. The upper bar shows the progress of the currently running test. The lower bar shows the overall progress of the analysis process. The log window in the top section tracks the currently running test and its result. See Figure 5.1, “Automatic Repair Mode”. The following main test runs are performed with every run. They contain, in turn, a number of individual subtests.
Checks the validity and coherence of the partition tables of all detected hard disks.
The swap partitions of the installed system are detected, tested, and offered for activation where applicable. The offer should be accepted for the sake of a higher system repair speed.
All detected file systems are subjected to a file system–specific check.
/etc/fstabThe entries in the file are checked for completeness and consistency. All valid partitions are mounted.
The boot loader configuration of the installed system (GRUB or LILO) is checked for completeness and coherence. Boot and root devices are examined and the availability of the initrd modules is checked.
This checks whether all packages necessary for the operation of a minimal installation are present. While it is optionally possible also to analyze the base packages, this takes a long time because of their vast number.
Whenever an error is encountered, the procedure stops and a dialog opens, offering details and possible solutions. It is not possible to describe all these cases. Read the messages on the screen carefully and choose the desired action from the list options. It is also possible to decline the offered repair action in cases of doubt. The system remains unaltered in this case and no repair is ever performed automatically without prompting the user.
