Today to install Oracle on a test server, with Yum installation dependent package always prompt glibc version conflict, originally installed version is relatively high, so hand owed directly rpm-e glibc and Glibc-common to delete, and then operations to find I said server login not up , and my side has been the error:
-bash:/usr/bin/ls:/lib64/ld-linux-x86-64.so.2:bad ELF interpreter:no such file or directory
No matter what the operation is to report the above error, thought this is finished, is not necessary to re-install the server AH. Consulted with SA, said it is possible to use the CD-ROM boot into recovery mode to repair.
The idea is to copy the missing files back.
Enter Repair mode
650) this.width=650; "src=" Https://s2.51cto.com/oss/201711/02/6c513aaf1915e8fddf0785cb4e66d519.png "style=" float: none; "title=" 1.png "alt=" 6c513aaf1915e8fddf0785cb4e66d519.png "/>
650) this.width=650; "src=" Https://s2.51cto.com/oss/201711/02/00c22638f295ccdf62035a472b39c17c.png "style=" float: none; "title=" 2.png "alt=" 00c22638f295ccdf62035a472b39c17c.png "/>
Copy the missing files back into the system
650) this.width=650; "src=" Https://s2.51cto.com/oss/201711/02/ebabcb4ac5095144414fa4f3157cec6c.png "title=" 3.png " alt= "Ebabcb4ac5095144414fa4f3157cec6c.png"/>
Switch to the original system using Chroot
650) this.width=650; "src=" Https://s5.51cto.com/oss/201711/02/a6ff4feee876af498a47aa6928f09dd0.png "title=" 4.png " alt= "A6ff4feee876af498a47aa6928f09dd0.png"/>
Missing after the discovery or the file, and then after a reboot, the system still cannot boot.
Later thought that the lost files should not only be reported out of those, there are many do not know the package has also been lost.
On the Internet to find an introduction to the recovery method of the blog, the first is that I used this method, he said that is not recoverable, and then the second method is to reinstall the GLIBC software package, and then began a second attempt:
650) this.width=650; "src=" Https://s2.51cto.com/oss/201711/02/68e1950d782b929cc84e3f00f2f2da92.png "title=" 5.png " alt= "68e1950d782b929cc84e3f00f2f2da92.png"/>
System returns to normal after reboot
650) this.width=650; "src=" Https://s5.51cto.com/oss/201711/02/557bb7dc558038b2b96e7160a8c6ec71.png "title=" 6.png " alt= "557bb7dc558038b2b96e7160a8c6ec71.png"/>
The blog also has a third method of recovery, where there is no attempt, interested students can try.
Reference: http://chocchen.blog.51cto.com/5099327/1329888
This article is from the "DBA fighting!" blog, so be sure to keep this source http://hbxztc.blog.51cto.com/1587495/1978568
Linux 7.2 Recovery after mis-deletion of glibc