Kernel panic - not syncing: Attempted to kill init

[tebogo]

I need help with this error.
I had tried everything and I could not resolve the error.

I am using Centos 7 to boot rescue mode.

I was uninstalling the following rpm's
- glibc-2.14.1-14.12.5.x86_64.rpm
- libtalloc-2.1.2-1.el7.x86_64.rpm
- libtevent-0.9.21-1.el6.x86_64.rpm
- samba-client-3.6.23-24.el6_7.x86_64.rpm
- samba-common-3.6.23-24..el6_7.x86_64.rpm
- samba-winbind-3.6.23-24.el6_7.x86_64.rpm
- samba-winbind-clients-3.6.23-24.el6_7.x86_64.rpm

the command to uninstall was: rpm -e glibc-2.14.1-14.12.5.x86_64 libtalloc-2.1.2-1.el7.x86_64 libtevent-0.9.21-1.el6.x86_64 samba-client-3.6.23-24.el6_7.x86_64 samba-common-3.6.23-24..el6_7.x86_64 samba-winbind-3.6.23-24.el6_7.x86_64 samba-winbind-clients-3.6.23-24..el6_7.x86_64

after the installation was complete, there was no command to be executed except cd and exit. any other command was generating an error below:
-> bash: /bin/ls: /lib64/ld-linux-x86_64.so.2: bad ELF interpreter: No such file or directory

I rebooted the VM then the following error was generated:
-> Kernel panic - not syncing: Attempted to kill init!
-> Pid: 1, comm: switch_root Not tainted 2.6.32-358.el6.x86_64 #1
-> Call Trace:
-> [ffffffff8150cfc8>] ? panic+0xa7/0x16f
-> [ffffffff81073ae2>] ? do_exit+0x862/0x870
-> [ffffffff81073b48>] ? do_group_exit+0x58/0xd0
-> [ffffffff81073bd7>] ? sys_exit_group+0x17/0x20
-> [ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b

I am new in Linux. Your help will be highly appreciated.

[TrevorH]

Split this away from an unrelated topic in the CentOS 6 forums. Please don't hijack threads.

Why on earth would you rpm -e glibc?? I'd be pretty sure that is not the command you ran to do it especially since we do not and never have shipped a glibc-2.14 for any version. CentOS 6 uses glibc-2.12 and CentOS 7 uses 2.17.

In case you didn't know, glibc is the C runtime for all packages on a linux system. Without it *nothing* will work.

Reinstall.

[TrevorH]

I've now moved this back to the CentOS 6 forums since it appears that you are running CentOS 6. In which case why have you attempted to install CentOS 7 packages on it and where did you get a non-CentOS glibc from? From a quick Google search it appears that this package belongs to OpenSUSE. Do not try to install foreign packages on CentOS - especially not ones that affect every single other package installed.

I am 100% sure that rpm would not have let you erase glibc. If I try that here on CentOS 7, I get 9,244 error messages telling me that I cannot rpm -e glibc because some other package depends on it. The only way in which it might work is if you also used rpm -e --nodeps to force it to do it.

So, 1) do not install packages from other systems on CentOS. 2) do not install packages from other versions of CentOS on your system 3) never use rpm -e --nodeps

To fix this, I think you need to reinstall the system.

[tebogo]

Meaning there is no other way to resolve this

[tebogo]

Really need the VM. I had really needed to copy rpm to be installed to the VM.

I had needed to install samba client to the VM and however I could not do so. Therefore I installed the rpms using sudo rpm -ivh --replacefiles *.rpm in a folder with all uninstalled rpms below.

samba client was used to attack my VM and therefore I made a to uninstall samba client.

[tebogo]

My VM is Centos 6.4.

I use Centos 7 for rescue mode.

[TrevorH]

You installed a foreign glibc which, on its own, was probably enough to entirely break your system.

To compound matters you then erased it and did not replace it with a different version. Your system now has no C runtime libraries and no installed programs will run.

Everything on your system uses glibc and depends on the exact version that we ship. You cannot just flip in a copy of a random package that you found via a google search and that belongs to a different distro altogether.

CentOS 6.4 is unsupported and has been since the release of 6.5 in December 2013. It is more than 4 *years* old. The current version is 6.9 and is the only version that receives updates. Do not run 6.4 as it contains multiple high severity security vulnerabilities.

At this point your best bet is to backup your data and reinstall the system.

The samba security vulnerabilities you talk about trying to fix are some of those high severity security vulnerabilities that I mentioned above that are fixed in 6.9. The correct method to fix those would have been to run yum update and pull down the fixed packages from the CentOS repos.

[tebogo]

Thank you very much.

[tebogo]

Hi TrevorH.

Thank you very much, I managed to fix the VM with the information you provided. I had followed the steps below:
-> accessed the VM using ubuntu live
->mounted /dev/sda2 to the create directory /data then transferred the listed rpms to the directory
# glibc-2.12-1.7.el6.x86_64.rpm
# glibc-common-2.12-1.7.el6.x86_64.rpm
-> umount /data directory
-> Shutdown Ubuntu live then access the VM using Centos 7 rescue mode
-> type chroot /mnt/sysimage then press enter
-> create directory /data then mount /dev/sda2 to the directory
-> execute the command below to install the rpms
# rpm -ivh --force --root=/mnt/sysimage/ glibc-2.12-1.7.el6.x86_64.rpm glibc-common-2.12-1.7.el6.x86_64.rpm
-> umount /data directory then type exit
-> When you start the VM, it will boot.