LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 06-01-2011, 05:35 AM   #1
pinga123
Member
 
Registered: Sep 2009
Posts: 684
Blog Entries: 2

Rep: Reputation: 36
Kernel 3.0 giving me panic :)


I was very exited to try out new kernel version so i decided to give it a try.
http://www.conceivablytech.com/7683/...-linux-3-0-rc1

So i downloaded the kernel 3.0-rc1 from
http://www.kernel.org/


It was my first kernel compilation everything went smooth until i reboot the system .New kernel is not loading and giving me following error.

The root partition is using LVM and its having no trouble booting from previous 2.6.18-92.el5 kernel .
Code:
Red Hat nash version 5.1.19.6 starting 
reading all physical volumes. This may take while...
No volume groups found
Volume group "VolGroup00" not found
mount: could not find filesystem '/dev/root'
Kernel panic - not syncing :attempted to kill init!
I m not sure why its happening.Is it because the previous kernel was el5 and not rhel5.
Code:
# uname -r
2.6.18-92.el5
# lsb_release -a
LSB Version:    :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: EnterpriseEnterpriseServer
Description:    Enterprise Linux Enterprise Linux Server release 5.2 (Carthage)
Release:        5.2
Codename:       Carthage
 
Old 06-01-2011, 06:34 AM   #2
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Quote:
Originally Posted by pinga123 View Post
Code:
Red Hat nash version 5.1.19.6 starting 
reading all physical volumes. This may take while...
No volume groups found
Volume group "VolGroup00" not found
mount: could not find filesystem '/dev/root'
Kernel panic - not syncing :attempted to kill init!
It seems your kernel lacks drivers for the filesystem and LVM.

Could you please describe in more detail how you did the configuration of your kernel?

Markus
 
Old 06-01-2011, 07:24 AM   #3
pinga123
Member
 
Registered: Sep 2009
Posts: 684
Blog Entries: 2

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by markush View Post
It seems your kernel lacks drivers for the filesystem and LVM.

Could you please describe in more detail how you did the configuration of your kernel?

Markus
I did it exactly as described in following blog .I used previous kernel configuration file to avoid any error.My previous kernel has support for lvm so in that regard the new kernel should be having the support for LVM.

http://www.howtoforge.com/kernel_compilation_fedora_p2
 
Old 06-01-2011, 07:43 AM   #4
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Did you check with
Code:
make xconfig
if the configuration is really correct? You may as well use grep to check your .config file. For example
Code:
grep -i _md .config
Markus
 
Old 06-01-2011, 08:07 AM   #5
grail
LQ Guru
 
Registered: Sep 2009
Location: Perth
Distribution: Manjaro
Posts: 9,255

Rep: Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686
Also did you read any background on the 3.0 kernel? Could be they have changed the way some options are stored. This may affect the fact that you used the old config and those options were named different or not compatible. Markus' idea about grepping for the desired elements should help.
 
Old 06-01-2011, 09:23 AM   #6
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Quote:
Originally Posted by grail View Post
Also did you read any background on the 3.0 kernel? Could be they have changed the way some options are stored. This may affect the fact that you used the old config and those options were named different or not compatible...
Well, I've compiled linux-3.0-rc1 and it's running yet
Code:
Linux samsung 3.0.0-rc1 #1 SMP Wed Jun 1 15:06:53 CEST 2011 x86_64 AMD Athlon(tm) II Dual-Core M320 AuthenticAMD GNU/Linux
There are no big differences to the 2.6.38.2 Kernel which I was running before with Slackware64-13.37. I did a
Code:
make oldconfig
(after copying the .config from the 2.6.38.2 kernel) and used all the defaults on new features and checked whith make xconfig.

Markus
 
Old 06-01-2011, 09:55 AM   #7
grail
LQ Guru
 
Registered: Sep 2009
Location: Perth
Distribution: Manjaro
Posts: 9,255

Rep: Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686
Fair enough ... haven't had a go yet myself so just throwing up some ideas
 
Old 06-01-2011, 10:27 AM   #8
sundialsvcs
LQ Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 7,183

Rep: Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212
The root cause of the problem is in the "Volume not mounted" message.

The message, "not syncing - attempted to kill init" is slightly cryptic, but here is what it really means:
  1. "Not syncing" actually means that Linux was not in the middle of a disk-write when the error occurred. It is not a comment on the problem itself. (It does mean, happily, that your filesystem has probably not just been destroyed.)
  2. "Attempted to kill init" would be better stated as, "init just died ... but init is not allowed to die!"

And so it is. init is one of those very-special processes that are "hand-made" by Linux during the startup sequence. It is fundamental to the operation of the system, such that Linux cannot run if this process is not in good health. If this process dies, or fails to start, or gets killed, for any reason at all, the kernel will stop cold ("panic") with this message.

But, as you can now see, this message is a symptom, or perhaps a consequence, of "the real problem" which occurred moments before. Conditions prevailed at startup-time which made it impossible for init either to start or to stay started, and Linux has no choice but to halt if this ever happens.
 
1 members found this post helpful.
Old 06-01-2011, 10:55 AM   #9
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Quote:
Originally Posted by sundialsvcs View Post
  1. "Not syncing" actually means that Linux was not in the middle of a disk-write when the error occurred. It is not a comment on the problem itself. (It does mean, happily, that your filesystem has probably not just been destroyed.)
  2. "Attempted to kill init" would be better stated as, "init just died ... but init is not allowed to die!"
...
thanks for the detailed explanation. In my post #2 above I referred to this
Quote:
Originally Posted by pinga123
Code:
mount: could not find filesystem '/dev/root'
I had this message sometimes with Gentoo when the kernel was missing either the driver for the filesystem or the SATA-driver (which I had forgotten to compile into the kernel instead of building it as a module). Maybe (otherwise) the system of the OP needs an initrd which was not yet installed.

Markus
 
Old 06-01-2011, 11:06 PM   #10
pinga123
Member
 
Registered: Sep 2009
Posts: 684
Blog Entries: 2

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by markush View Post
Did you check with
Code:
make xconfig
if the configuration is really correct? You may as well use grep to check your .config file. For example
Code:
grep -i _md .config
Markus
Code:
# grep -i _md .config
CONFIG_SCTP_HMAC_MD5=y
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_USB_MDC800=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
Any clue?
 
Old 06-02-2011, 01:07 AM   #11
grail
LQ Guru
 
Registered: Sep 2009
Location: Perth
Distribution: Manjaro
Posts: 9,255

Rep: Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686Reputation: 2686
You could try setting all the 'm' to 'y' as it may be that the driver cannot be a module as Markus mentioned in earlier post.
 
Old 06-03-2011, 01:44 AM   #12
pinga123
Member
 
Registered: Sep 2009
Posts: 684
Blog Entries: 2

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by grail View Post
You could try setting all the 'm' to 'y' as it may be that the driver cannot be a module as Markus mentioned in earlier post.
I did it and recompiled the kernel still facing the same problem.

However i forget to give you some information which i m revealing now.
I was running short of disk space in / partition so i added a new disk and added to / partition using LVM.

Is this a cause of the trouble.
I have also googled the problem and found something which might be related to the error.
http://www.gentoo.org/doc/en/lvm2.xml
Since this is my first kernel compilation i m little confused on what to do ?
 
Old 06-03-2011, 03:54 AM   #13
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Hi,

are you sure, that you can boot with your old kernel? After your last post I'm not sure if the problem actually is the new kernel.

BTW, I read the announcement for kernel 3.0-rc1 at linux.kernel and Linus Torvalds states that there is no big changes in the kernel:
Quote:
Originally Posted by Linus Torvalds at linux.kernel on May 30
...
So what are the big changes?

NOTHING. Absolutely nothing. Sure, we have the usual two thirds driver
changes, and a lot of random fixes, but the point is that 3.0 is
*just* about renumbering, we are very much *not* doing a KDE-4 or a
Gnome-3 here. No breakage, no special scary new features, nothing at
all like that. We've been doing time-based releases for many years
now, this is in no way about features. If you want an excuse for the
renumbering, you really should look at the time-based one ("20 years")
instead.
...
Note that if you have any drivers which are compiled with the old kernel, for example firmware-network-drivers, you'll have to rebuild them with the new kernel. But this requires that you can boot your system and has (as well) nothing to do with kernel 3.0

Markus
 
Old 06-03-2011, 04:12 AM   #14
evo2
LQ Guru
 
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and Scientific Linux
Posts: 5,753

Rep: Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288
Just want to point out that while there are only small changes between 2.6.39 and 3.0-rc1, there are some very significant changes between 2.6.18 and 2.6.39.

Evo2.
 
1 members found this post helpful.
Old 06-03-2011, 05:55 AM   #15
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Hello evo2,

that's a very good point, I didn't recognize that the OP's old kernel is outdated.

Markus
 
  


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
new kernel giving problems? luqman Red Hat 5 03-04-2005 12:24 PM
LIDS not giving all options in kernel subt13 Linux - Security 1 08-11-2004 01:39 AM
Kernel panic puts me in a panic theeeg Linux - Software 2 07-31-2004 05:46 PM
kernel panic (narius panic) narius Linux - Newbie 3 06-20-2002 04:56 PM
Kernel panic making me panic! Linux_N0oby Linux - Software 19 05-29-2002 01:31 AM


All times are GMT -5. The time now is 07:26 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration