Re: kernel panic, no init found
Thank you very much.
I followed your suggestion. Here is what I did and what I got:
Boot from a floppy, with kernel 2.0.35
login as root
> mount /dev/hda2 /mnt
> cd mnt
> rm vmlinuz
> ln -s boot/vmlinuz-2.0.34 vmlinuz
> ls -l sbin/lilo
-rwxr-xr-x 1 root root 50708 Feb 2 17:31 sbin/lilo
sbin/lilo: not found
> ls -l /usr/bin/lilo
-rwxr-xr-x 1 root root 46740 Jul 28 1998 /usr/bin/lilo
> lilo -r /mnt
First boot sector doesn't have a valid LILO signature
Is it the time to re-start from scratch? I am stuck.
On Tue, 16 Mar 1999, Paul Miller wrote:
> Jianming YOU wrote:
> > Hi, Experts,
> > I just upgraded my box from 2.0.34 to 2.2.1 and I got
> > "kernel panic, no init found..." when I tried to boot with the new
> > kernel. The problem have been reported by several people. However, I
> > still don't know how to recover the system after reading those replies,
> > :(.
> > I'd appreciate if anyone can outline a procedure to recover from this
> > situation. For the moment, I can only boot with a 2.0.34 floppy and see
> > the hard disk.
> > Any guidance is very much appreciated.
> After booting from the rescue floppy, find the file called /vmlinuz on
> your hard drive (yes in the root directory). It is a symbolic link to a
> file called /boot/vmlinuz-2.2.1. Delete the /vmlinuz file and make a new
> symbolic link
> ln -s /boot/vmlinuz-2.0.34 /vmlinuz
> Now rerun lilo by simply typing 'lilo'. Now you can reboot off the hard
> drive with your old kernel.
> As for what caused the 'no init found' error. My guess is lack of block
> device support in the new kernel. Under the block device section, there
> is a sub-section for 'Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy
> support'. Be sure to select it then select 'Include IDE/ATA-2 DISK
> support'. Of coarse this assuming you are using an IDE hard drive.
> Paul Miller