[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel panic: NO INIT FOUND, but seems to be there.



On Mon, Apr 22, 2002 at 11:54:18PM -0500, dman wrote:
> On Mon, Apr 22, 2002 at 11:29:25PM -0400, Jerome Acks Jr wrote:
> | On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
> | > Hi!
> | > 
> | > Thank you for your answer. I have tried passing to the boot prompt
> | > 
> | > linux root=/dev/hda9 init=/sbin/init,
> | > 
> | > but the result is the same as before. Actually /sbin is on the root
> | > partition.
> | > 
> | > I guess the reason why my system hanged, was that I tried suspending to
> | > disk while my ethernet card was working. It hanged while writing
> | > a huge list of messages on the console. I shut the power down, and now it
> | > does not work.
> | > 
> | > Do you have any other ideas what to try? Should I reinstall everything? I
> | > hope there is something more to try.
> | 
> | Hi Alessandro,
> | 
> | Since you can boot from a floppy, I would try reinstalling the kernel
> | or a new kernel using chroot before reinstalling everything.
> 
> Is it possible to re-create /dev in the chroot environment?  The 2.4
> kernel-image packages need to access stuff in /dev to build the initrd
> image.  I know because I've tried this, and failed as a result.

Yes. 

I usually have devfs mounted on /dev. However, I never removed the
old /dev or maybe the root file system on tomsrtbt boot disk may be what makes
this possible. If you have removed the old /dev, maybe running the
MAKEDEV script may make it work.

Just to double check, I installed the debian stock
kernel-image-2.4.18-386_2.4.18-4_i386.deb this morning. I had no
problem creating the initrd image. The only problem I had was lilo run
from the install scripts did correctly remap symlinks in /boot. So
I ended up having having to manually fixing these and running lilo a
second time. Boot messages did give me warnings that modprobe "can't
find module /dev/root.old". I think this may be due to differences
between /dev when I install the kernel and /dev with devfs mounted,
Other than that the new kernel seem to work OK.

Here is what I did:
1) boot from tomsrtbt (I used version 1.7.342 -- not the newest)
2) mount partions on /mnt to recreate your disk root file system
        e.g.: mount /dev/hdb2 /mnt
              mount /dev/hdb1 /mnt/boot
              mount /deb/hdb7 /mnt/var
              etcetera...
3) chroot /mnt
4) mount /proc
5) su -                   # dpkg won't find needed scripts without this
6) edit /etc/lilo.conf
7) dpkg -i <kernel-image-package>
8) exit
9) umount everything you previously mounted
10) exit (from tomsrtbt)
11) reboot

-- 
Jerome

Attachment: pgped12H6R_yf.pgp
Description: PGP signature


Reply to: