CentOS Rescue Mode (rescue installed system) repairs damaged systems

Some time ago encountered the developer update glibc version, the/usr/lib64/libc-2.12.so & libc.so.6-libc-2.12.so This soft connection changed after the error caused:

Ls:error while loading shared libraries:libc.so.6:cannot open Shared object file:no such file or directory

Cannot log on remotely, terminal can not login, also cannot log on single user,

Telnet

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/7C/6C/wKiom1bQFCeA8SsFAAAemVJRLBY130.png "style=" float: none; "title=" 1.png "alt=" Wkiom1bqfcea8ssfaaaemvjrlby130.png "/>

Terminal login:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7C/6C/wKiom1bQFCjT2neQAAAZdjq8ZzE758.png "style=" float: none; "title=" 2.png "alt=" Wkiom1bqfcjt2neqaaazdjq8zze758.png "/>

Single-User:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7C/6A/wKioL1bQFJnTxP12AAAr0ulXcao377.png "style=" float: none; "title=" 3.png "alt=" Wkiol1bqfjntxp12aaar0ulxcao377.png "/>

In fact, after the execution of the wrong operation only do not disconnect the remote connection there is room for recovery, but the remote abnormal disconnection after a lot of people did not switch, ready to salvage data & files, re-install system, in fact, here we do not worry about reloading the system, let's try rescue!

First, prepare the system installation disk, start using the installation disk:

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7C/6B/wKioL1bQFyiiyx9pAAGi8wcejWs890.png "title=" Select Rescue installed System "alt=" Wkiol1bqfyiiyx9paagi8wcejws890.png "/>:

Second, choose the language and keyboard (the default is good):

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7C/6C/wKiom1bQFpnQUkFGAABXeZieUXc445.png "title=" Select language " alt= "Wkiom1bqfpnqukfgaabxezieuxc445.png"/>

Three, wait a moment will appear to set up the network, generally speaking, the network is not a problem without setting, I choose No:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/7C/6C/wKiom1bQFy6SBsq-AAA1PQGe3yE741.png "title=" Set Network " alt= "Wkiom1bqfy6sbsq-aaa1pqge3ye741.png"/>

Four, here is the rescue option:

1. Select Continue, the rescue mode program will automatically find the system's existing file system and mount them to the/mnt/sysimage directory.

2. Select Read-only to mount the existing file system in a read-only manner.

3. Manual mount then skip.

4. Advanced, the premium option is not explained.

Let's choose Continue here:

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M02/7C/6B/wKioL1bQGCDDcHoqAACDKFkw2gE957.png "title=" Rescue option "alt=" Wkiol1bqgcddchoqaacdkfkw2ge957.png "/>

Five, the original system mount path/mnt/sysimage, if you want to get the original system root environment, execute line command: Chroot/mnt/sysimage can.

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/7C/6B/wKioL1bQGdThFUjbAABWTp9lqv0392.png "title=" System Mount instructions "alt=" Wkiol1bqgdthfujbaabwtp9lqv0392.png "/>

Six, here can perform FAKD diagnosis, of course, we here directly into the shell command line:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7C/6C/wKiom1bQGqeT8qgyAAA-3a6VVso643.png "title=" 9.png " alt= "Wkiom1bqgqet8qgyaaa-3a6vvso643.png"/>

Seven, this plays the play, because/usr/lib64/libc-2.12.so & libc.so.6---libc-2.12.so problem, executive Chroot/mnt/sysinage will error:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/7C/6D/wKiom1bQGzmhzNfRAABQaSlSqbQ574.png "title=" chroot /mnt/sysinage error "alt=" Wkiom1bqgzmhznfraabqaslsqbq574.png "/>

Eight, do not be afraid to do:

Cp/lib64/libc-2.12.so/mnt/sysimage/lib64/libc-2.12.socp/lib64/libc.so.6/mnt/sysimage/lib64/libc.so.6

Copy the disc file to the system file, and then execute the chroot/mnt/sysinage as normal:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/7C/6E/wKiom1bQHe7TjnaLAABX_O5j2MU011.png "title=" Copy Files " alt= "Wkiom1bqhe7tjnalaabx_o5j2mu011.png"/>

In fact, here I rescue has been completed, because the system is missing/usr/lib64/libc-2.12.so files and libc.so.6-libc-2.12.so soft connection, copy the past is good.

Ix. Exit Shell & Reboot

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/7C/6E/wKiom1bQHuryNHddAAAZAeE9iu0368.png "title=" reboot "alt=" Wkiom1bqhurynhddaaazaee9iu0368.png "/>

Other system file corruption can also be referred to the same procedure, not to repeat here.

Welcome everyone to advise ~ ~ ~

This article is from the "Little Mo Growth Road" blog, please be sure to keep this source http://309173854.blog.51cto.com/7370240/1745376

CentOS Rescue Mode (rescue installed system) repairs damaged systems