It may be faster to reinstall linux, unfortunately. What fsck is trying to tell you by saying it don't run fsck with the a or the p switch is that there are enough problems with your filesystem that it doesn't wan't to fix them automatically. Normally when a system gets powered down there aren't a whole lot of things that fsck has to fix, so it will do it automatically. It sounds like you are having to fix so many problems by answering yes and it just keeps finding another problem...
I've only seen this type of behavior 1 time from fsck and it was on a "second" disk other than the one that was "hosting" linux. When I would start from scratch on the second disk by using (fdisk, mkfs, and fsck -- I'm not suggesting this as a fix to your issue) fsck would give me so many errors on a newly created file system it was ridiculous. It turned out to be a bug in the kernel that shipped with my distribution, and updating the kernel fixed it.
Unfortunately I don't have an easy solution for you, unless installing linux was easy for you the first time
Hopefully someone more experienced than me can help.
If you have extra disk space, you might be able to do another "parallel" linux installation , and then try to fix the file systems that have your data on them - truly I have no experience with linux this way.
I do have a couple of questions that might get more info from you tho
What is your linux distribution or kernel?
How big was the file system that fsck is complaining about?
Was there a bunch of data on it you need to keep?