check for corrupted files

Other than chkdsk, What program can interactively check if NTFS files are corrupted (either written corrupt files or files which became corrupted after their original write)

If such a program exists, does it need to first checksum every file on the drive to have a "known-good" reference table?

Does NTFS keep checksum information for every file by default?

Is there a way to check files for corruption without knowing their original checksum?

>>1
AUTOCHK.EXE (ran on boot if the drive is marked as dirty) doesn't compare checksums, nor NTFS keeps them at all; that'd be hell slow. It just checks the MFT, the metadata, and other NTFS structures and fixes inconsistent information about your filesystem, splitting, deleting, or assigning files in the process. You probably got it mixed with SFC.EXE which protects system files.

Is there a way to check files for corruption without knowing their original checksum?
Nope, sorry.

>>2
cant checksums be kept in ntfs alternate data streams

how long can it really take to write a checksum as each new file is written to disk

>>3
cant checksums be kept in ntfs alternate data streams
You can, but no tool that I know does that

how long can it really take to write a checksum as each new file is written to disk
The problem is you not only have to create it for every file, you have to keep it updated on every change, and to check your disk for sanity, you need to read every frigging file.

>>4
so how can ntfs disks be checked in windows for file integrity against corruption incase the hardware slowly begins to fail

someone must have made a program to do it

reading every file to verify them is fine, it would only be necessary ondemand when you want to recover files off the drive etc

i wrote a script to sfv files when they are written to a storage directory, storage files rarely get changed, system files do change a lot though

>>5
We have SMART to check if the hardware is slowly beginning to fail.

>>6
yea i'm using a program called activesmart now to monitor changes in smart attributes

but for the file integrity itself, ive had many corrupt files on a few drives and it was impossible to tell which files were bad

even recovery software like ontrack would give general errors not specific to individual files, like "errors occurred during recovery" not x y z etc files are corrupted

the only workaround i can see is recovering each file as a seperate job and see if "errors occurred during recovery" is displayed, as a way to narrow down the corrupt files

ofcourse there are thousands of files to recover... and the ontrack software allows no automation or scripting within the program, nor command line switches to the program

there must be a definitive drive recovery program that can measure if files are corrupt on ntfs filesystems