NO, the upload limit (maximum global size for attachments on MSFN.ORG forum) is much lower expecially - I believe - for new members, if you sum all the screenshots and logs you posted, you have probably reached it.
It does matter that you find a way to produce that screenshot, as I need to know the actual LBA of the "real", "good" $MFT (the one found for the volume that starts @16373760) and have to know what actually it is found when using that $MFT.
From what I could gather till now, partition Wizard simply recreated a partition with a slightly different situation.
It is possible that CHKDSK made some "damage", but I doubt it (and it shoudl have been an extremely "short" run of CHKDSK)
In the meantime I thought a bit about WHAT caused the issue, and (morally only ) I have good news .
It was not strictly your fault (nor the fault of the tools you used), it was one of the lesser known SERIOUS glitches with XP (actually with it's Disk Manager), see here:
basically the XP disk manager CANNOT deal with disks containing logical volumes NOT aligned to cylinders and whenever you do *anything* on such a disk, even something as trifling as changing the active status of a Primary partition, it attempts to re-calculate/re-check the whole partitioning setup, fails and plainly deletes any and all logical volumes inside extended.
The issues (if any) with that NAS are the following:
- the filesystem of the partition on which you create the huge file must be capable of making such a big file (this means either NTFS or Ext2/3/4, I am not familiar with that hardware but - if by any chance the filesystem is FAT32 it won't work ) and you need to have anyway 2,000,398,934,016 free space on the volume on which you make the file, if the actual disk in the NAS is 2Tb in size, I doubt you will have that amount of space actually free in the filesystem
- transferring 2 Tb over the network might be very slow (normally such dd copies are made to disks directly connected to the machine)
I am not aware of a limitation in the free edition of DMDE about the imaging, but you can use datarescuedd as well as *any* tool capable of making a dd-like copy of the disk.
BEFORE you make the "huge copy" I would like to have a look at:
some 100 sectors starting from sector 0:
dsfo \\.\PhysicalDriven 0 51200 C:\myfirst100.bin
some 300 sectors starting from sector 16370098 <- these include also the beginning of the "bad" $MFT which is @16370322
dsfo \\.\PhysicalDriven 8381490176 153600 C:\mybadpart300.bin
some 300 sectors starting from sector 16373560
dsfo \\.\PhysicalDriven 8383262720 153600 C:\mygoodpart300.bin
some 300 sectors starting from sector (the whatever sector the "good $MFT" is)
dsfo \\.\PhysicalDriven ???????? 153600 C:\mygood$MFT300.bin
(in the screenshot you posted http://www.msfn.org/...-1385319889.jpg which is about the "bad" $MFT, the meaningful LBA address is the one in the top left of the right bottom pane, in GREEN LBA:16370322, I need the corresponding one for the "good" $MFT)
The n in the above is the "usual" disk number.
You can get the dsfo.exe as part of the DSFOK toolkit:
extract it in a directory like C:\dsfok, then open a command prompt and navigate to it and then enter the command lines above.
If you have issues with command line tools, say so BEFORE attempting using them incorrectly.
As an alternative you can use the DMDE or the DatarescueDD to create the needed "partial" .bin files.
Once you have created them, do compress them all into a .zip archive, upload to a free hosting site and post a link to the file.
Ask for clarifications if you have doubts.