How To Solve Kernel Panic Error In Centos
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business
Kernel Panic Not Syncing Offline Nt
Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation kernel panic not syncing unable to mount root fs on unknown block Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like
Centos Kernel Panic Not Syncing
you, helping each other. Join them; it only takes a minute: Sign up How to solve “Kernel panic - not syncing - Attempted to kill init” — without erasing any user data [closed] up vote 12 down kernel-panic-not-syncing-attempted-to-kill-init-exitcode-0x00000100 vote favorite 3 I was trying to update libc in our Ubuntu server but it failed and now when I reboot the server I get a error message: Kernel panic - not syncing - Attempted to kill init! and it just hangs. What is the solution to this problem? The server is used by 10 people so I don't want to reinstall erasing their data. security ubuntu linux-kernel selinux panic share|improve this question edited Jul 8 kernel-panic-not-syncing-attempted-to-kill-init-exitcode-0x00007f00 '14 at 8:39 RzR 1,7561325 asked Oct 12 '12 at 21:50 Slayer 68831214 closed as off-topic by Undo♦ Aug 29 at 2:18 This question appears to be off-topic. The users who voted to close gave this specific reason:"Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – UndoIf this question can be reworded to fit the rules in the help center, please edit the question. Kernel panics happen for a variety of reasons. Often due to hardware failure... You'll need to check out /var/log/dmesg and /var/log/syslog to get more info about what actually happened. –hsanders Oct 12 '12 at 21:58 1 You should try to boot using a "Live CD", and then mount the HDD partition that held / and /lib. Then try to restore the libc files. –sawdust Oct 12 '12 at 23:43 6 This isn't really the right forum for this question. You're better off asking on superuser.com or ubuntu.stackexchange.com. This question looks like it'll be migrated to superuser.com shortly. –Craig Ringer Oct 13 '12 at 7:40 add a comment| 8 Answers 8 active oldest votes up vote 11 down vote if the full message is: kernel panic - not syncing: Attempted to kill inint !
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the
Drm_kms_helper Panic Occurred Switching Back To Text Console
workings and policies of this site About Us Learn more about Stack kernel panic not syncing redhat linux Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions
Drm_kms_helper Panic Occurred Ubuntu
Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; http://stackoverflow.com/questions/12867591/how-to-solve-kernel-panic-not-syncing-attempted-to-kill-init-without-er it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to repair system if kernel panic? up vote 3 down vote favorite I've just updated packages: 2013-05-23 11:15:34 startup archives unpack 2013-05-23 11:15:35 upgrade locales:all 2.13-38 2.17-3 2013-05-23 11:15:35 status http://unix.stackexchange.com/questions/76812/how-to-repair-system-if-kernel-panic half-configured locales:all 2.13-38 2013-05-23 11:15:35 status unpacked locales:all 2.13-38 2013-05-23 11:15:35 status half-installed locales:all 2.13-38 2013-05-23 11:15:35 status triggers-pending man-db:amd64 2.6.3-3 2013-05-23 11:15:35 status half-installed locales:all 2.13-38 2013-05-23 11:15:38 status half-installed locales:all 2.13-38 2013-05-23 11:15:38 status unpacked locales:all 2.17-3 2013-05-23 11:15:39 status unpacked locales:all 2.17-3 2013-05-23 11:15:39 upgrade libc6:i386 2.13-38 2.17-3 2013-05-23 11:15:39 status half-configured libc6:i386 2.13-38 2013-05-23 11:15:40 status unpacked libc6:i386 2.13-38 2013-05-23 11:15:40 status half-configured libc6:amd64 2.13-38 2013-05-23 11:15:40 status half-installed libc6:i386 2.13-38 2013-05-23 11:15:47 status half-installed libc6:i386 2.13-38 2013-05-23 11:15:47 status unpacked libc6:i386 2.17-3 2013-05-23 11:15:48 status unpacked libc6:i386 2.17-3 2013-05-23 11:15:48 upgrade libc6:amd64 2.13-38 2.17-3 2013-05-23 11:15:48 status half-configured libc6:amd64 2.13-38 2013-05-23 11:15:48 status unpacked libc6:amd64 2.13-38 2013-05-23 11:15:48 status half-installed libc6:amd64 2.13-38 2013-05-23 11:15:53 status half-installed libc6:amd64 2.13-38 2013-05-23 11:15:53 status unpacked libc6:amd64 2.17-3 2013-05-23 11:15:54 status unpacked libc6:amd64 2.17-3 2013-05-23 11:15:54 trigproc man-db:amd64 2.6.3-3 2.6.3-3 2013-05-23 11:15:54 status half-configured man-db:amd64 2.6.3-3 2013-05-23 11:16:00 status installed man-db:amd64 2.6.3-3 2013-05-23 11:16:01 startup packages configure 2013-05-23 11:16:01 configure libc6:amd64 2.17-3
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://superuser.com/questions/730387/kernel-panic-after-lvm-group-rename more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Kernel panic after LVM group rename up vote 2 down vote favorite kernel panic 1 I have a CentOS 6.3 VM running and I got the error message below after I did lvm group rename and rebooted (SELinux running). vgrename vg_name1 vg_name2 reboot The error message is: Kernel panic - not syncing: Attempted to kill init! Screenshot How to solve this boot problem? centos share|improve this question edited Jan 11 '15 at 10:38 nyuszika7h 7941826 asked Mar 18 '14 at 9:43 Xianlin 2741310 add a comment| 3 Answers 3 active oldest kernel panic not votes up vote 4 down vote accepted I just had the same problem. In my case the issue was that I had renamed the devices, but not told my bootloader about it. I booted using a live CD/DVD, found and mounted my boot filesystem, then edited the bootloader configuration (i.e. /grub/grub.conf). I corrected the names of the LVM disks in that file to their new versions, then rebooted and all was fine. share|improve this answer answered Apr 2 '14 at 9:59 TheBamf 812 1 Yep, i deleted a secondary swap file from LVM but forgot to remove it from grub command line. Did not use a LiveCD but edited grub command line at initial bootup. Then once i was booted up, edited /etc/grub..conf. –rjt Jul 30 '14 at 15:27 add a comment| up vote 2 down vote I have a feeling its SELinux causing the problem. Try the following Reboot the machine. When the Grub menu shows up, hit the up/down key. Then hit the 'A' key. You will enter a minimal shell for Grub. Add the following after whatever is on the screen selinux=0 enforcing=0 And then hit enter. Let us know what happens. Ideally you should be taken to the login prompt. You then need to figure out why SELinux is causing trouble. You might want to start with the messages log. You could technically disable