Sorry but you didn't.

The Master Boot Record(start sectors) and the file system are separate things anyway repairing the MBR doesn't affect the File System.

Judging by the tone of your post(in it's entirety) I get the impression that further help from me will go on deaf ears...so, I guess all that remains is for me to wish you luck.

tone?

I think the "tone" may have been misinterpreted. You have tried to give as much information as you can but it could be read as "I've already done all this, don't tell me what I already know". Which is not how I think you meant it.

You used an old version of software which was written before disks could get anywhere close to 2TB, there were system limitations in place which meant it wasn't even possible to construct drives that size. So blaming Norton is a bit daft.

Doing this may have done damage to the contents of the disk. The checkdisk will, hopefully, resolve that - but you may still lose some data.

Good luck.

yeah it was misinterpreted, and not my intention to have sound like that, that i have tried it all and done it all. but rather try to give as much information as i can and try to react to everyone.
i did the thing stuff stuggested on my 2tb f: drive but at this rate it will take atleast 12-24 hours.
it uses 2gb of ram and sometimes gives a warning that pc is out of memory (everything else is off), so hope its stays up.

and thx.

I wouldn*t recommend Norton anyway, but - no offense - in this case the problem was that you were knowingly using an outdated product while having important data (without backups) on your machine. The conclusion to be drawn from this event certainly isn't "don't use Norton". It is:

1. Don't use outdated software, especially not for things that are crucial for your machine's operation, like partition management.
2. If for some reason you _have to_ use outdated software, make a backup of everything that's important to you before doing so.
3. _Don't_ give an outdated program the power to automatically "fix" things. The chance that it _breaks_ things instead (because it encounters things it doesn't know because of being too old, and then "fixes" these into structures it does know, which will break whatever use and purpose the original structure had) is far too high.

Seriously, spending 5 minutes to download an up-to-date free partitioner instead of using an outdated one just because you "had it lying around" would have solved you _all_ the trouble you're now having.

Anyway. One other option you can try before using another fix again, is to access the files from a different OS. You can burn an Ubuntu live CD and boot it, and then access your HDs and files from there. It _probably_ will show the same problems, but it might be worth a shot, since it's a non-invasive procedure. At this point, every program that is trying to "fix" things has a high probability of breaking other things (though I guess that there won't be a way around using one in the end). Anyway, backup the files you _can_ access before doing anything else. Also check if these files are correct on the content level (the various "fixing" could have corrupted them).