Hi,
You may get a better answer from someone who knows more, but this is what I would try:
Get hold of a Live CD of a distro which uses Grub1 not Grub2 or Lilo. That means most distros.
Boot with it and get a root terminal. Type "grub" to get a grub prompt.
Then
Code:
root (hd0,2)
setup (hd0,2)
This will put Grub into the superblock of sda3. (I assume it is in sda3 that your linux lives)
If you then type
Code:
chainloader +1
boot
it ought to boot. If you get an error eg "File not found" or some such, try typing (from the grub prompt)
Code:
kernel /boot/vmlinu
and then hit the TAB key for autocompletion. Then type
and hit TAB again.Then type
and it should boot.
If you have been using Grub1 to boot, it should be on the MBR. It may be corrupted,in which case from a grub prompt (either using your live CD or in a root terminal in linux), typing
Code:
root (hd0,2)
setup (hd0)
will put it into the MBR, overwriting whatever was there.
If you're with Grub2, then (from your installed linux), typing in a root terminal:
Code:
grub-install /dev/sda
update-grub
will install Grub2 into the MBR, overwriting whatever was there.
I think that the fsck message was probably normal, given that you tried to fsck an extended partition.