Kernel Panic - not syncing: Attempted to kill init!

General support questions
JamesSimpson
Posts: 5
Joined: 2013/06/02 16:37:33
Contact:

Kernel Panic - not syncing: Attempted to kill init!

Postby JamesSimpson » 2013/06/02 16:59:05

Hi All,

I am a bit of a Linux/CentOS newb, although I've worked with it a bit before, but I wish I never tried to update my new server.

Background:

I received a new server which already had CentOS installed and was working perfectly - It's a Dell Poweredge R210 II, last night I did a yum update and installed the latest version of Linux, and this morning, I restarted the server, and got the following error message:

Kernel Panic - not syncing: Attempted to kill init!
Pid: 1 comm: init Not tainted 2.6.32-358.6.2.e16.x86_64 #1
Call Trace:
[] ? panic+0xs7/0x16f
[] ? do_exit+0x862/0x870
[] ? fput+0x25/0x30
[] ? do_group_exit+0x58/0xd0
[] ? sys_exit_group+0x17/0x20
[] ? system_call_fastpath+0x16/0x1b


I have read up on google, and everyone suggests the repair CD, the issue I have, the server doesnt come with a CD drive - which leaves me high and dry as the OS was installed over the network when I purchased it.

May this be an issue with the raid controller?

I can get into the GRUB but I dont know what to do from there, I have also tried booting from the old kernal as that was listed in the menu, but get the same error as above.

JamesSimpson
Posts: 5
Joined: 2013/06/02 16:37:33
Contact:

Re: Kernel Panic - not syncing: Attempted to kill init!

Postby JamesSimpson » 2013/06/02 17:04:13

PS. it has a RAID1 configuration (2x 1TB drives in RAID 1 = 1TB Usable)

JamesSimpson
Posts: 5
Joined: 2013/06/02 16:37:33
Contact:

Re: Kernel Panic - not syncing: Attempted to kill init!

Postby JamesSimpson » 2013/06/02 17:07:56

PPS, thinking back actually, It did boot this morning as I tried to install Webmin, and started following this process:
http://rbgeek.wordpress.com/2012/05/27/ ... entos-6-2/

Restarted the server after disabling selinux and the above error started

JamesSimpson
Posts: 5
Joined: 2013/06/02 16:37:33
Contact:

Re: Kernel Panic - not syncing: Attempted to kill init!

Postby JamesSimpson » 2013/06/02 17:33:19

I think I have found my issue:
http://darktraining.com/vmware/86/

Hmmm now how can I edit that without a CD rom drive - can I put it on a USB pen and boot from that?

JamesSimpson
Posts: 5
Joined: 2013/06/02 16:37:33
Contact:

Re: Kernel Panic - not syncing: Attempted to kill init!

Postby JamesSimpson » 2013/06/02 21:39:17

Right spent all day on this without any luck now.

Managed to get a bootable image into USB, ran Linux repair from the centos install menu, went thought that process and goes to Bash command line, now how do I get to that file and edit the text using bash?

The code that states in the website I posted above wont work as it says addon not allowed (or something like that)

I tried using VI command to edit it (/etc/says admin/...) but it just says it's creating a new file... Would this be creating the document on my memory pen?

I'm so confused right now. But then again there is no way like learning new things hah

simon_matthews
Posts: 315
Joined: 2012/09/15 21:06:54

Kernel Panic - not syncing: Attempted to kill init!

Postby simon_matthews » 2013/06/03 03:01:46

In the "Linux rescue" option, when booting, it should ask you if you want it to mount the Linux partitions. Assuming you said yes to this, you should have your filesystem in /mnt/sysimage, so to edit the file, you will need to edit /mnt/sysimage/etc/sysconfig/selinux .

kekkonj
Posts: 1
Joined: 2014/07/08 11:39:06

Re: Kernel Panic - not syncing: Attempted to kill init!

Postby kekkonj » 2014/07/08 11:46:27

Even this is an old thread, I would like to remind that there might be several reasons, not only the selinux, causing exactly the same kernel panic loop. Here below few of them:

1. wrong/incorrect/missing entries in the /etc/fstab file, requires reboot in the rescue mode in CentOS/Fedora/RHEL and might be painful in the virtualized environments if not having any attachable CD-ROM iso images of the CentOS/Fedora/RHEL OS for the VMs.

2. wrong/incorrect/missing entries in the /etc/grub.conf (sym link to /boot/grub/grub.conf), requires reboot in the rescue mode in CentOS/Fedora/RHEL as above. You can also remove the boot parameters "quiet" and "rhgb" from your grub.conf file to be able to troubleshoot the issue more when troubleshooting rebooting the system up. This of course you can do only when you have the local file systems being mounted in the rescue mode (google more for the rescue mode, being lazy writing the whole process herein).

3. Wrong/incorrect configuration in the LVM environment causing a dracut related issues while booting the OS. This you can troubleshoot more using the Fedora Wiki at: http://fedoraproject.org/wiki/How_to_debug_Dracut_problems

4. If you have tried already the grub boot parameter enforcing=0 and that didn't do the trick, stop troubleshooting the selinux, it's not the faulty part and try the above options. If the above options won't solve the issue, then keep trying, the issue is somewhere down there...

paulopctek
Posts: 1
Joined: 2014/11/02 20:50:52

Re: Kernel Panic - not syncing: Attempted to kill init!

Postby paulopctek » 2014/11/02 21:26:00

I still have the error even I deactivate Selinux, I was doing some reasearch about dracut but understand why the system stop booting when reaches this point:

Code: Select all

vmw_pvscsi 0000:03:00.0: PCI INT A -> GSI 18 (level, low)-> IRQ 18
vmw_pvscsi: using 64bit dma
vmw_pvscsi: using MSI-X
scsi2 : UMware PVSCSI storage adapter rev 2, req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=64
vmw_pvscsi 0000:03:00.0: UMware PVSCSI rev 2 host #2
 scsi 2:0:0:0: Direct-Access   VMware   Uirtual disk 1.0 PQ: 0 ANSI: 2
 
sr0: scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sd 2:0:0:0: [sda] 125829128 512-byte logical blocks: (64.4 GB/68.8 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:8:8:8: [sda] Cache data unavailable
sd z:a:a:a: [sda] Assuming drive cache: write tllrough
sd 2:8:8:8: [sda] Cache data unavailable
sd 2:8:8:8: [sda] Assuming drive cache: write through
sda: sda1 sda2 sda3
sd 2:8:8:8: [sda] Cache data unavailable
sd 2:8:8:8: [sda] Assuming drive cache: write through
sd 2:8:8:8: [sda] Attached SCSI disk
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts:
dracut: Mounted root filesystem /dev/sda2
dracut: Switching root
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
sh-4.1#