"No root device found.Boot has failed.sleeping forever." on rhel6 when compile kernel
 

It is on a server,with Xeon E5506,SATA,SSD,SAS,etc.
I never compiled the kernel on a server,and I don't know is there any special to pay attention to.
I downloaded kernel source code from kernel.org,then using the old config from boot directory,then compiled it as usual.reboot then it told me
I compiled 2.6.32,2.6.30,2.6.36,3.0.1,etc,and it is no change.
I delete the "quiet"option from menu.lst,and these appeared:
I'm sure the config file has ext4=y

so anybody who can help me?Thanks very much.

Noooooooooooooooo!!!!!!!!!!!!!!
 

Noooooooooooooooooooooooooooooooooooooooooo....the config HAS to be build by the package...

Steps to follow

- download the source
- unpack in a NON ROOT folder
- open (console) the folder
- enter make menuconfig
- enter make
- THEN go to ROOT mode
- enter make install

I guess the old config had sent the server to the "big backup in the sky"...

I'd like to keep this thread in view to see if I could help further...

Luck

Thor

without config file from boot,I don't know how to config the kernel
 

without config file from boot,I don't know how to config the kernel
could you explain it what's the meaning of "big backup in the sky"?
Using the old kernel I found those messages from dmesg
but my kernel just told me:
when I press ctrl+alt+delete,it print

You can use the old .config file to compile the new kernel.
Take a look at this guide
http://www.cyberciti.biz/tips/compil...kernel-26.html
Use'
instead of
@Thor_2.0
I unpack the source in
Didn't you forget the
Kind regards

actually no matter what I did
copy old config then make menuconfig
or
copy old config then make oldconfig,and type enter for any questions

then make&&make modules_install&&make install,then reboot.
it was still "No root device found.Boot has failed.sleeping forever."

thank you everyone

The clue to your mystery is in the messages which precede the actual panic: none of the identified file systems could be processed.

A very likely culprit is that you have configured the system with the necessary filesystem support in a loadable kernel module, instead of specifying that it must be compiled into the resident kernel. A filesystem driver can't be loaded if a filesystem driver is necessary in order to load it ... "Catch-22."

what does "Catch-22"mean？

@ repo

Yes, I seem to have left that out, my bad... :banghead:

Hmm, that's a good spot, but on my system, I'd need Root rights, and I made it a rule-of-thumb to use the Root account a less as possible...but, yes, it's a good spot.

@ OP

Catch-22, as Wikipedia sees it ;)

my expression of "having died"... :)

I always did a make menuconfig, no matter what. Just to ensure crispness, but...my way is not carved in marble... :D

Thor

I still have no idea to solve this problems.I am wondering if it is the hardware made this.

Okay, so, you've gotten the source, if you're at that point, the reast can be followed in this tutorial...

Pardon me. It's an American expression, explained here.

The phrase specifically refers to a book about pilots who were flying combat missions. "(Pilot) Orr was crazy and could be grounded. All he had to do was ask; and as soon as he did, he would no longer be crazy and would have to fly more missions. Orr would be crazy to fly more missions and sane if he didn't, but if he were sane, he had to fly them. If he flew them, he was crazy and didn't have to; but if he didn't want to, he was sane, and therefore had to fly the missions." This was 'Catch #22' in the official bureaucratic rule-book.

In my usage: "if the necessary file-system support code is in a kernel module, then the computer has to have access to the filesystem in order to load the module. But it can't do that, because, without the necessary file-system support code, it can't find and load the module."

It is common to include filesystem support in kernel modules. (For example, you don't need to be able to read a CD-ROM filesystem until, and unless, you actually stick a CD-ROM into the drive. The same goes for, say, USB memory sticks.) But, for whatever filesystem you have used for the kernel, support for that filesystem must be resident in the kernel. It's a common mistake. (I can say that ... :hattip: ... with absolute authority.)

Thank you for your kindness and explaination.
Actually,I used ext4 format for the root partition,ext3 for boot.so what is the support for that ext4?
And "be resident" means say yes or module to the config file?

No matter "make oldconfig" or "make defconfig",it is always sleeping forever.I still cannot firgure out what the problem is.