On Wed, 5 Mar 2003, lar lar wrote:

> i have a server that's dead, when it boots up it gives the 
> following message, complaining it cant find initrd:
> "Kernel Panic: No init found. Try passing init= option to kernel"
> booting with linux init=/bin/sh, it still complains about not 
> finding initrd, and gives the same message. booting linux rescue 
> doesn't seem to phase it either, neither does specifying root= and 
> kernel=. gives the same messages upon boot every time. is there 
> some option you can compile with to make the kernel not take user-
> specified options on boot, and if so, is there a way to get around 
> it, or is there something else wrong?
> 
Try booting from one of the rescue floppies or CDs (or even the rescue 
mode on the install CD/disk).  If it isn't finding the initial ramdisk, 
then chances are it isn't able to load modules needed to access the root 
file system, or you have a hard drive problem.  If it is just the 
drivers, you can rebuilt the initial ramdisk, and go from there.  If it 
is the hard drive, it may require hands-on from a "geek"...

If you made an emergency boot floppy during install, now is the time to 
dig it out!  If you can boot the system off the floppy, then see what 
errors you get.  If you get the same error message from the boot floppy, 
then it is a bad hard drive.  (Hardware, or a disk curruption...)

Mikkel
-- 

    Do not meddle in the affairs of dragons,
 for you are crunchy and taste good with ketchup.



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to