Is CHKDSK (without the /F parm) on NTFS Partions really Read-only?

On an NTFS partion, while running CHKDSK, I see errors like: "Badly linked attribute" and "Deleting index $130 of file 28" followed by: "Run CHKDSK with /F parameter to fix ". If I re-run CHKDSK (without the /F parm) the error does not (always) show. The questions are:

1- Did I really have a disk error?

2- Was CHKDSK *really* in R/O mode?

I am trying to debug a data loss problem on my system. If I run CHKDSK against an NTFS partion, I see the above errors relatively frequently. If I re-format the partion to FAT32, I never see any errors. Put it back to NTFS, errors again. Any idea what might be happening? Thanks.

SRL

 

Steve,

Thanks for the quick reply, but I think you missed the point of my question. If I run CHKDSK without any switches set, is it *really* in Read Only mode. I know that it *says* it is. However, if I run it enough (as in doing it from a batch file), I will get various kinds of errors. Lastest flavor of error is: "Deleting corrupt attribute record (128, " ")." However, from the logging I am doing with the batch file, the errors are not consistant, and out of say 200 times, there might be three different errors (and a 197 times it checks "OK "). I would think that if the error(s) were *real*, it would show every time, assuming that CHKDSK is operating in Read-Only mode.

I believe that my data loss is from running CHKDSK with the /F, and a "false" error was "corrected ". I have come up missing entire directories, only I do not discover it until I go to access a file or program. I am not sure of the cause. The problem is in determining if the errors are real, and if so, what is causing them?

Any additional ideas?