kernel panic after fsck

[LRC1962]

My file system corrupted. fixed that by using e2fsck -b command. now at start up I go into kernel panic because it can not find /sbin/init or /bin/sh. There are other issues also but I can not find how to scroll page by page through the startup to find out what else is going wrong.
From what  I have read I could be missing or have corrupted files or directories as a result of the system file repair. By going into a live CD I do know that those are both linked.
Is this manually fixable or should I just get a new live CD and do a full format?

[musca]

Hello LRC1962,

you have more than one alternative superblock, I think.
How did you choose yours?

man e2fsck:

-b superblock
  Instead  of  using  the  normal  superblock,  use an alternative
  superblock specified by superblock.   This  option  is  normally
  used  when the primary superblock has been corrupted.

man mke2fs:

-n     Causes  mke2fs  to  not  actually create a filesystem,
  but display what it would do if it were to create a filesystem.
  This can be used to determine the location of the backup
  superblocks for a particular filesystem, so long as the mke2fs
  parameters that were passed when the filesystem was originally
  created are used again.  (With the -n option added, of course!)

greeetings
musca

[LRC1962]

Sorry about long delay in reply. Had other issues to deal with.
Used mke2fs to find superblocks and used first one. Then used e2fsck -f -b ***** -y /dev/****. Tried alternatives and came up with the same problem.
Did notice one thing.  Lost and Found Directory is 32GB in size on that partition. There are a lot of directories in it with numbers. I am presuming that is related to block locations of directories. Is there a way to recover that other then manually figuring out what each directory is related to and manually changing the name and putting it back into the file system?