LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices

Reply
 
LinkBack Search this Thread
Old 11-21-2006, 04:30 AM   #1
Sayoji
LQ Newbie
 
Registered: Nov 2006
Posts: 9

Rep: Reputation: 0
Kernel Panic - not syncing (2.6.9-22)


Hi,
I have downloaded the RedHat Kernel Source and followed the steps of kernel compilation and i am able to boot from my new kernel. I didn't add any new modules to it. But when i proceed the steps again and tried to boot i get the following error.

Creating root device
Mounting root filesystem
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode
mount: error 2 mounting none
Switching to new root
WARNING: can't access(null)
exec of init ((null)) failed!!! 14
umount /initrd/dev failed: 2
Kernel Panic - not syncing: Attempted to kill init!


I could not find what i messed up.
Thanks for any help.
 
Old 11-21-2006, 03:31 PM   #2
Mara
Moderator
 
Registered: Feb 2002
Location: Grenoble
Distribution: Debian
Posts: 9,408

Rep: Reputation: 108Reputation: 108
It looks it has problems mounting the / partition using the new kernel. Most common reason is no support for the filesystem. Look into /etc/fstab and see which filesystem is used for /. Then look into your kernel config. That filesystem must be compiled into the kernel or be available in initrd image. It may be also worth it to see if the initrd file that is used with the new kernel has been created for it (don't use one from the old kernel).
 
Old 11-21-2006, 03:40 PM   #3
sundialsvcs
Senior Member
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 3,681

Rep: Reputation: 329Reputation: 329Reputation: 329Reputation: 329
Or that it doesn't know how to find it. Many distros use the initrd sequence at startup, so you need to make sure that the entire make-sequence has been properly done.

Let me explain the message:
kernel panic - not syncing: attempted to kill init
  • kernel panic -- "you're dead, Jim." The system has reached a state where execution cannot continue.
  • not syncing -- this is not a description of the problem, nor its cause. It actually means that, when the system died, it was not trying to write ("sync") unsaved changes to disk. This is good news: it was successful at writing unsaved changes to disk before it halted.
  • attempted to kill init -- init, or "process #1," is a special process in Linux/Unix systems which must always exist. It cannot be killed; it must not die. This message indicates that it somehow did die.
  • This entire message is actually "just the last shuddering gasp of breath" that the system took before it fell over. The reason for the failure will be found in messages that precede this one.
 
Old 11-21-2006, 10:40 PM   #4
Sayoji
LQ Newbie
 
Registered: Nov 2006
Posts: 9

Original Poster
Rep: Reputation: 0
Thank u for ur time. I have checked my /etc/fstab file. The filesystem used for / is ext3 only and the config file of my new kernel too consists

CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y

I have created a new initrd file for that kernel by
mkinitrd -v -f /boot/new.img 2.6.9-22
When i boot from new kernel i get the same error
Any other solution to solve this issue.
Thanks
 
Old 11-22-2006, 06:08 AM   #5
Sayoji
LQ Newbie
 
Registered: Nov 2006
Posts: 9

Original Poster
Rep: Reputation: 0
I got it . After make modules_install instead of creating initrd image by mkinitrd i give
Quote:
make install
and now my new kernel is booting up. But, i could not find why the initrd image created by mkinitrd shows Kernel Panic error.
Thanks.
 
Old 11-28-2006, 11:56 PM   #6
Nishant Desai
Member
 
Registered: Jul 2006
Posts: 100
Blog Entries: 1

Rep: Reputation: 15
Quote:
Originally Posted by Sayoji
I got it . After make modules_install instead of creating initrd image by mkinitrd i give

and now my new kernel is booting up. But, i could not find why the initrd image created by mkinitrd shows Kernel Panic error.
Thanks.
Dear Sayoji,

You were almost at the solution, when u found the

CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y

In your .config file CONFIG_EXT3_FS='y' instead of 'm' and that is why you are getting the error, so please do the make config step again, and when you found the option "CONFIG_EXT3_FS" give 'y' to enable the EXT3_FS parttion, because Redhat supports the EXT3 and in the cofig you are not enabling that option.

Hope this will help, pls reply me after doing this step.

Thanks,
Nishant
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panic-not syncing PowersurgeX Linux - Newbie 5 09-14-2006 02:27 PM
kernel panic - not syncing gentoo_user Linux - Hardware 1 06-01-2006 08:48 PM
Kernel panic – not syncing alfredo Linux - Newbie 6 02-27-2006 11:12 AM
Kernel panic not syncing n6rob Linux - General 3 02-15-2006 06:13 AM
Kernel panic - not syncing carboncopy Slackware 9 12-13-2005 05:53 AM


All times are GMT -5. The time now is 12:36 PM.

Main Menu
 
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: @linuxquestions
Open Source Consulting | Domain Registration