Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you the solution to the erroneous deletion of libc prompt Kernel panic not syncing: Attempted to kill init in Linux. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

System type: CentOS 6.5 (x64)

Startup prompt: Kernel panic-not syncing: Attempted to kill init

Background: because the soft connection of libc.so.6-> libc-2.12.so was deleted by mistake (figure 1), I didn't expect that many commands could not be used. It turns out that many linux shell commands are inseparable from libc.so.6.

Next, after rebooting the system, it keeps reporting the error of Kernel panic-not syncing: Attempted to kill init (↓ chart).

Method 1:

There are many ways to edit the grub menu on the Internet before, select the "kernel / vmlinuz-XXXXro root=/dev/vogroup00/logvol00 rhgb quiet" column, press the'e' key to enter the edit, and restart after adding enforcing=0 at the end, but this method is not applicable in this case.

Method 2:

Restart the virtual machine and enter the first aid mode: press ESC when you see the interface of VMWARE after reboot, select CD-rom to start, or directly change bios and choose CD-ROM to start. As long as you enter the rescue mode and find the relevant folder, the rest will be the same as before, revenge and vengeance.

English is selected by default.

US is selected by default for keyboard.

three. Select whether to configure the network card

General system to rescue, the network is not needed, so you can choose whether or not to skip the network card configuration, of course, if you need to choose yes, the specific setup process is the same as the installation.

Choose to continue (Conyinue)

The system on the hard drive has been found and mounted under / mnt/sysimage

There are three options:

1.shell enters command line mode

2.fakd is the diagnostic mode

3.reboot restart the computer

We choose shell here to enter the command line mode

Since all files are read-only: READ-ONLY when you first enter, you must use the command to give read and write access:

Mount-o remount rw / and mount-o remount rw / mnt/sysimage

Enter / mnt/sysimage, under this folder is the real system path, enter / lib (or / lib64 as the case may be)

Then re-establish the soft link

And use the chroot / mnt/sysimage command (the prompt will change from bash-4.1# to sh-4.1#)

In sh-4.1# mode, you need to exit exit first, go back to bash-4.1# before you can restart the system by reboot, and enter the system smoothly after reboot.

There is another pit is: the link to the system file must not be deleted casually, must update the lib file, you can use ln-sf to forcefully update the link, just repaired and did not slow down, want to change 2.14 to 2.12 as a result, just deleted the soft link and become the previous look, repair again, so, the link to the system file must not be deleted casually!

The above is the solution to the mistakenly deleted libc prompt Kernel panic not syncing: Attempted to kill init in the Linux shared by the editor. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.