Hi, I am running Fedora Core 2 on an 2.4.22-1.2194.nptl kernel.
My box consists of an AMD Duron(750MHz) with 384MB of RAM, have to HDD's, first one has(Maxtor 2R015H1) WinXP Pro and the other HDD(6E030L0) used to have FC 2 on it.
I did not install Fedora Core using ISO images cause my CDROM does not allow me to boot from it.
So what I did was use the bootdisk.img(floppy) and installed it through the Internet(HTTP).

Right now the current ERROR I am trying to solve is:

' Kernel Panic: No init found. Try passing init=option to Kernel ', which I have no clue of how.

Problem started when:

Yesterday I updated the FC 2 system using 'yum', i.e. '#yum update', once yum finished updating I went ahead and rebooted the machine just to make sure everything was working, cause I've had so many problems with this distribution since installing FC 1 on this machine.

During the boot, the GRUB interface came on
i.e. (1) Fedora Core (kernel 2.4.22-1.2194.nptl)
(2) DOS
so I selected choice (1) and it scrolled the normal text on the window, but it stayed on this text window with the following ERROR:

ERROR: insmod: insmod usb-uhci failed
EXT3-fs error(device ide0(3,66)): ext3_get_inode_loc:
unable to read inode bloc K- inode = 2583838, block = 5177352

and then prompted me to enter root passwd OR press CTRL-D to reboot.
I entered root passwd and used the 'fsch -c or the other options' for many hours and all I get is a prompt for FileSystem #1 or #2 or #3 or etc............ each time. I gave up on using the fsch at this point.

I turned the machine off(cause it was getting late and I needed get some sleep).
This morning when I turned the machine and selected choice (1) from the GRUB prompt it gave me a different ERROR, this time the ERRO is

"Kernel Panic: No init found. Try passing init=option to Kernel"
and it hangs there.

When I try to use the floppy(bootdisk.img) and try to reinstall FC 1 it goes through downloading the .img but once it gets to the Fedora Core window to make the mouse and monitor selections it freezes for about 2 minutes and prompts an 'INPUT/OUTPUT' ERROR.

I tried using the RESCUE option in the bootdisk.img and I get no where cause it brings the same prompt 'INPUT/OUTPUT' ERROR.

The RESCUE option gets me to the shell screen as a last option thing, and I discover that the partitions that I use to have for FC 2 no longer exist, I discovered this using the FDISK command, it only shows my Windows XP Pro. Partition on "hda", nothing on "hdb".

I know I've written down alot but I am in a position where I don't know where to go from here, I am really stuck.
All I want right is just wipe out what ever is in my "hdb" and do a fresh reinstall of FC 1 not FC 2.
Any help will be appreciated, thanks in advance!!

Did you check the contents of /mnt/sysimage? This is the place where Rescue mode keeps your Linux Partitions.

hi ppuru, thanks for the reply.
when rescue tries to make the /mnt/sysimage it fails because there are Linux partitions on my drive(hdb).
My question is how can I reinstall my partitions because it will not let me do it through the method I've been doing all this time which was to boot from the "bootdisk.img" insert my "drivernet.img" disk, tell it get the images from an HTTP site, give the hostname of the site and the directory of the Fedora Core OS and then it is a smooth transition from there, but not anymore it gives me an INPUT/OUTPUT ERROR once it's done getting the images from the HTTP site and it's on the Fedora Core Screen.

So once again my Linux partitions do not exist anymore.

aaahh linux - no wonder why it dont take the world of desktop and fly - in linux we like to make the simple hard and the easy impossible...

I haven't post a message for a while.
Yeah, two days later my Maxtor HDD gave up, so I am waiting for Maxtor to send me anothe HDD.
This is the second Maxtor HDD that died while trying to install Fedora Core 1.

But I am going to go at it again once I install the new HDD, Linux ain't simple at first it needs, alot of patience and the commitment to learn it, from a newbie.

try booting into single user mode then fsck'ing the disk to remove errors