Kernel Panic – Not Syncing: Attempted To Kill Init!

Home » CentOS » Kernel Panic – Not Syncing: Attempted To Kill Init!
CentOS 21 Comments

Just installed CentOS 6.3 from a minimal install disc. All was well, so I ran a yum update, as well as installed some additional packages
(mysql, httpd, libjpeg, libpng, and more that I don’t remember off the top of my head). Went to reboot the machine and now it won’t book up. As it starts to boot, says:

Kernel panic – not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-279.5.1.el6.x86_64 #1
Call Trace:
[] ? panic+0xa0/0x168
[] ? do_exit+0x862/0x870
[] ? fput+0x25/0x30
[] ? do_group_exit+0x58/0xd0
[] ? sys_exit_group+0x17/0x20
[] ? system_call_fastpath+0x16/0x1b

Also, tried selecting the previous kernel at boot, but got the same message, except with 2.6.32-279.el6.x86_64 referenced.

Machine is a dell poweredge 620, perc h310 raid controller, 4x600GB 10K
SAS, 16GB RAM, 2xIntel Xeon E5-2630 2.3GHz procs (hex-core), dual 495W
power supplies.

Any help would be much appreciated.

Thanks,

21 thoughts on - Kernel Panic – Not Syncing: Attempted To Kill Init!

  • Joseph Koenig wrote:

    My first reaction is when the menu, or the “about to boot kernel…” line comes up, edit that, then add rdshell to the end of your kernel line, and let it boot. If it gets to the rdshell, you might check to see if there’s an agreement between the root (hdx,x) line in grub.conf and what the system leads grub to think is the first h/d.

    Also, here’s what I’m assuming: a) the PERC controller is actually presenting the drives to the system, and b) that grub was in fact installed.

    mark

  • Thanks for the suggestion – just tried and doesn’t get to rdshell. The panic happens within a few seconds (if not less) from when I edit the kernel line and hit enter to start booting. Yes, grub was installed, and it would seem PERC controller is presenting drives to the system – at least it was. Before I ran a yum update after installing the system, I could boot it and log in just fine.

    Worth reinstalling from the minimal install disc again just to make sure that still works? Would that rule out something having gone awry with my RAID card or disk?

  • Installed from minimal the first time around, which is why I thought doing that again may be helpful. You think I’d be best to get the full install and run that though?

    Thanks for all the help.

  • Joseph Koenig wrote:
    Well, I think there’s a minimal server, rather than the full server install. Of course, I could be confusing that with our pxeboot setup….

    Odd thought: have you tried a) looking at the drives in the PERC firmware, or b) booting to linux rescue, and examining the filesystems?

    mark

  • Well, sure enough, it can’t seem to find any good superblocks. Even backups are showing corrupt. Will reinstall and see what happens…

    Thanks!

  • Joseph Koenig wrote:

    You mean the backup superblocks are bad? And it was a running system before?

    Is it still under warranty? You might consider talking to Dell about checking it out. They’ll want you to run the OMSA utility that scans the system.

    mark

  • Yep, was running just fine, install went fine, then at reboot after the yum update, this happened. Server is maybe a week old, so yeah, will get a hold of Dell. Thanks,

    Joe

  • I have the same behavior 6.2 vs latest on my Toshiba satellite.

    32-220 boots fine (except for the touchpad and power detection)
    32-279.2.1 crashes immediately

    Glad to forward logs

    ——————————————————————–

  • After some days viewing all stuff related to this kernel panic issue I found a solution at a Z68 configuration RAID1 / LVM.
    I had done a yum update from Centos 6.0 to 6.3 / kernel 2.6.32-279.14.1.el6.x86_64 and the reboot failed with mentioned kernel panic.

    The solution / workaround: Change in grub.conf DM with MD.
    The newer kernel 2.6.32-279 interacts different with MD / DMRAID configuration then the Centos 6.0 base kernel 2.6.32-71.

    See some lines from the grub.conf.
    Default entry 0 now works, but entry 1 gives the kernel panic.

    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.32-279.14.1.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-279.14.1.el6.x86_64 ro root=/dev/mapper/vg_virtualbox-lv_root rd_DM_UUID=hidden rd_DM_UUID=hidden rd_LVM_LV=vg_virtualbox/lv_root rd_LVM_LV=vg_virtualbox/lv_swap rd_NO_LUKS rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us nomodeset rhgb quiet
    initrd /initramfs-2.6.32-279.14.1.el6.x86_64.img
    title CentOS (2.6.32-279.14.1.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-279.14.1.el6.x86_64 ro root=/dev/mapper/vg_virtualbox-lv_root rd_MD_UUID=hidden rd_MD_UUID=hidden rd_LVM_LV=vg_virtualbox/lv_root rd_LVM_LV=vg_virtualbox/lv_swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us nomodeset rhgb quiet
    initrd /initramfs-2.6.32-279.14.1.el6.x86_64.img
    title CentOS (2.6.32-71.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=/dev/mapper/vg_virtualbox-lv_root rd_MD_UUID=hidden rd_MD_UUID=hidden rd_LVM_LV=vg_virtualbox/lv_root rd_LVM_LV=vg_virtualbox/lv_swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us nomodeset rhgb quiet
    initrd /initramfs-2.6.32-71.el6.x86_64.img

  • I have the same problem. Loaded 6.3 to a SanDisk 16GB USB drive and everything loaded fine and ran fine. I rebooted the system several times – but then ran yum and updated the system. Unfortunately I also started loading other packages too and then rebooted the system. Same “Kernel-panic-not-syncing-attempted-to-kill-init” error.

    I tried swapping the USB drive to different ports and that made no difference. I booted from the ISO CD and ran the disk utility to do a file check and it says “Clean File System”. I’m going to reload the system just incase something got corrupted (but I don’t think it is), we’ll see.

  • I have the same problem. Loaded 6.3 to a kingstoneDisk 4GB USB drive and everything loaded fine and ran fine. I rebooted the system several times – but then ran yum and updated the system. Unfortunately I also started loading other packages too and then rebooted the system. Same “Kernel-panic-not-syncing-attempted-to-kill-init” error.

    Pls help me.

  • Hello all,

    I am having the same problem as above, trying to boot RHEL workstation 6.3 (through virtualbox as it appears from your grub.conf that you are doing as well). I have tinkered with grub.conf a bit and changed instances of DM with MD and so forth but to no avail…

    I am fairly new to linux, does anybody have any suggestions as to how to overcome this?

    Thanks in advance!

  • hi,em is

    I have create a bootable USB pen drive with centoos 6.4. I am trying to do a new install(no upgrade). However, I get the same problem.

    I have seen the grub file and the Default value is 0.

    I am getting the kernel panic with the same message that is being discussed above.

    Can some one help.

    regards
    Raghu

  • Trying disabling selinux during boot in grub.

    e.g. in line 2 of grub boot you will see like:

    kernel /vmlinuz-2.6.32-279.14.1.el6.x86_64 ro root=/dev/mapper/vg_virtualbox-lv_root rd_DM_UUID=hid

    add the words selinux=0 at the end and then try booting. I did this and my Centos 6.4 now boots OK.

  • i have window 7 and i want to run dual os like centos 6.5 so when i installing centos 6.5 then it create error kernel panic not syncing attempted to kill init… what is do????
    plz help me

LEAVE A COMMENT