So I was using an external USB HDD, NTFS-formatted, on a linux machine with Fuse-NTFS. The machine stopped responding and crashed, and I was forced to hard-reboot. I gave it about 2 full minutes to start responding to anything, again, but it just didn't.
I care about the data on the NTFS volume, however. So I plugged it into a Win 7 box, and ran
chkdsk F: and
chkdsk /v F:. Neither one reports any errors which don't explicitly mention a filename with an illegal character for windows, so to me, I think it's safe to assume that all the errors are related to filenames which I have chosen that Windows just doesn't like. For these errors, I really don't care and don't really intend on using windows with the drive aside from for chkdsk, so I don't plan on fixing the filenames to make them windows-legal, and would actually rather not do so. However, chkdsk said,
Index verification completed. Errors found. CHKDSK cannot continue in read-only mode.
Does that mean that if it were to run with /f, it might discover additional errors? Would it progress to non-index sections of the volume to look for more errors with an
/F? Or will it just actively correct the errors that it detected without
/f and do nothing more?
I really do care about real errors that aren't windows being a narcissistic, and would very much like to be aware of those. Will doing anything else with chkdsk potentially make me so? Is there any way to find out if it will without renaming my files against my will?