Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
i am using redhat advaced server 2.1.while booting my server i am getting error message"kernel panic: No init found. try passing init = option to kernel ".pl give me solution to restore my server.
i am using redhat advaced server 2.1.while booting my server i am getting error message"kernel panic: No init found. try passing init = option to kernel ".pl give me solution to restore my server.
What did you change just before you rebooted? This looks like the kind of error you get when grub/lilo has "misplaced" your boot sector, but we would need to know what happened to get you into this pickle.
Can you boot from a live CD and examine the current filesystem? What you want to do is find out if the drives are still being "seen" the way they once were.
Your '/dev/sdb' might now look like '/dev/sda', if you follow my drift.
Ultimately, your bootloader is probably not pointing to your linux installation.
First things first...boot from live CD, mount your old / file system, examine /etc/fstab and see what it expects as a device...i.e.) sdb, hdb, etc. Post the result for us : )
How is that supposed to help us???? You will need to give more detail on your system configuration.
No--that would cause it not to find the kernel. It is the highlighted entry below that tells the kernel where to find init:
Actually, the key to what's happening *IS* in the loss of narenderiete's swappable drive, IMO. If his drive order is messed up, then narenderiete will get the message "kernel panic: No init found", meaning the boot loader could not continue with kernel initialization and has thrown this error to STDOUT and stopped.
I might be wrong, but I think his /boot partition is being recognized as a different disk, now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.