Kernel panic

[satimis at writeme.com (Stephen Liu)]

Hi Nathan,

Thanks for your response.

I did not do anything on this disk which is mounted on a mobile rack having 
been idle for sometimes.  2 day before I plug the tray (this mobile rack) 
into its housing then the nightmare started.

B.Regards
Stephen Liu


At 08:30 AM 12/1/2002 -0500, Nathan Meyers wrote:
>On Sun, Dec 01, 2002 at 09:13:28PM +0800, Stephen Liu wrote:
> > Hi all folks,
> >
> > When starting RH7.3 the screen hanged on :
> > Kernel panic: No init found. Try passing init=option to kernel.
> >
> > Used rescue disk to start trying to mount without success.
> >
> > # fdisk -l
> > Device Boot Start End Block Id System
> > /dev/hdc1 * 1 6 48163+ 83 Linux
> > /dev/hdc2 7 794 6329610 83 Linux
> > /dev/hdc3 795 826 257040 82 Linux swap
> >
> > Created a mount point
> >
> > # mkdir /mnt/rescue
> > # mount /dev/hdc2 /mnt/rescue
> > mount: Mounting /dev/hdc2 on /mnt/rescue failed:Device or Resource busy
>
>The rescue system already mounted that drive at /tmp/hdc2 (see below),
>which is why you can't mount.
>
> > # mount
> > rootfs on /type rootfs (rw)
> > /dev/root.old on /type ext2 (rw)
> > /proc on /proc type proc (rw)
> > /dev/pts on /dev/pts type devpts (rw)
> > /proc/bus/usb on /proc/bus/usb type usbdevfs (rw)
> > /tmp/cdrom on .mnt/source type iso9660 (rw)
> > /tmp/loop0 on /mnt/runtime type ext3 (rw)
> > /tmp/hdc2 on /mnt/sysimage type ext3 (rw)
> > /tmp/hdc1 on /mnt/sysimage/boot type ext3 (rw)
> > none on /mnt/sysimage/dev/pts type devpts (rw)
> > none on /mnt/sysimage/proc type proc (rw)
> >
> > # fsck
> > Warning: Couldn't open /etc/fstab : no such file or directory
> > e2fsck 1:27 (8-mar-2002)
> > /: recovering journal
> > /: clean, 102828/791840 files, 491473/1582402 blocks
>
>There's no /etc/fstab for the rescue system - you need to tell it
>what disk to check. You could unmount and check both disks thus:
>
>   umount /tmp/hdc1
>   umount /tmp/hdc2
>   fsck -y /dev/hdc1
>   fsck -y /dev/hdc2
>
> > Kindly advise how to fix this problem.
>
>Well... that said, I'm not sure fsck will find the problem. Did you do
>something disruptive, like perhaps installing a new kernel without
>rerunning LILO?
>
>Nathan Meyers
>nmeyers at javalinux.net