Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 259 — #285
i
i
i
i
i
i
i
i
10
Special Features of SUSE LINUX
Caution
Pay attention to the order of steps outlined in the following sec-
tion for mounting the various devices.
Caution
To access your entire system, mount it step by step in the /mnt directory
using the following commands:
mount /dev/sdb3 /mnt
mount /dev/sdb6 /mnt/usr
Now, access your entire system and, for example, correct mistakes in con-
figuration files, such as /etc/fstab, /etc/passwd, and /etc/inittab.
The configuration files are now located in the /mnt/etc directory instead
of in /etc.
Before recovering lost partitions with the fdisk program by simply setting
them up again, make a printout of /etc/fstab and the output of fdisk
-l.
Repairing File Systems
Damaged file systems are tricky problems for the rescue system. Generally,
file systems cannot be repaired on a running system. If you encounter seri-
ous problems, you may not even be able to mount your root file system and
the system boot may end with kernel panic. In this case, the only way is
to repair the system from the outside using a rescue system.
The SUSE LINUX rescue system contains the utilities reiserfsck, e2fsck,
and dumpe2fs (for diagnosis). These should remedy most problems. In
an emergency, man pages often are not available. For this reason, they are
included in this manual in Appendix C on page 735 and Appendix B on
page 729.
If mounting an ext2 file system fails due to an invalid superblock, the
e2fsck program would probably fail, too. If this were the case, your su-
perblock may be corrupted, too. There are copies of the superblock located
every 8192 blocks (8193, 16385, etc.). If your superblock is corrupted, try
one of the copies instead. This is accomplished by entering the command
e2fsck -f -b 8193 /dev/damaged_partition. The -f option
forces the file system check and overrides e2fsck’s error so that, since the
superblock copy is intact, everything is fine.
259
SUSE LINUX Enterprise Server