Kernel panic - Confused partitions

[NetMasker]

Thanks for your response Tommy but it seems that I didn't erased my root
partition.
I booted again with the cd-rom rescue method and I can see my files and
linux files also.
I think that the "mke2fs" command fortunately didn't run successfully.

I run:
tune2fs -j /dev/hda8 (root partition) and
tune2fs -j /dev/hda7 (boot partition)
and it tells me that they already have a journal!
also e2fsck -fy creates no errors.

But I think my partitions are still confused. I tried to unmount and mount
the partitions again but it told me that they were mounted differently in
/etc/mtab.

What if I run lilo again? I use the windows nt boot loader to boot and I
don't want to destroy this.
I run the test: "lilo -t -v" and I took this message:
fatal: open /boot/boot.b: No such file or directory.
I also noticed that the "/boot" directory has no contents (but the others
directories are ok).

What else can I do to make linux boot again ?

Below is the boot error again:
----------------------
Creating root device
Mounting root filesystem
Kjournald starting. Commit interval 5 seconds.
EXT3-fs: mounted filesystem with ordered data mode.
pivotroot: pivot_root(/sysroot/, /sysroot/initrd) failed: 2
Freeing unused kernel memory: 280k free
Kernel panic: No init found. Try passing init= option to kernel.
----------------------



"Tommy Reynolds" <TommyReynolds at yahoo.com> wrote in message
news:pan.2004.12.05.00.39.26.190137 at yahoo.com...
> On Sun, 05 Dec 2004 02:12:45 +0200, Net Masker wrote:
>
> > I boot with the first cd-rom of redhat in rescue mode, I checked my
> > "lilo.conf" file and it was OK!!
> > My ext3 root partition is on /dev/hda8 and I run:
> > mke2fs /dev/hda8
> > tune2fs ...
> > tune2fs -j /dev/hda#
> > e2fsck ...
> > (for all my /dev/hda# without understanding what am I doing exactly and
> > taking some superblock errors at first...)
>
> Well, when you ran "mke2fs /dev/hda8" you erased everything already
> in that partition.
>
> If you are seeing superblock errors, your disk is probably going bad.
>
> Another re-install is in order, so we can check the disk without
> worrying about corrupting anything.
>
> 1)  Boot into rescue mode again.
>
> 2)  Manually run
>
> # fdisk /dev/hda
>
>     and lay out the partitions the way you want them.
>
> 3)  Build a filesystem on each partition.  Use a command like this:
>
> # mkfs -t ext3 -c /dev/hda1
> # mkfs -t ext3 -c /dev/hda2
> # mkfs -t ext3 -c /dev/hda3
>
>     and so on.  The "-c" switch performs a surface analysis of the
>     media, looking for bad blocks.  If you get errors, you need a new
>     drive.
>
> Hope this helps.
>
> Cheers!
>