As Canadian Tech covered, a chkdsk f: /r should be performed if there is a possibility there are bad sectors on the drive (physical defect/damage). It is a more thorough 5-stage test that takes an extremely long time to run. If it is just simple file corruption due to a bad eject, table of contents, or flaky cable/power, the chkdsk f: /f will suffice. Since f: does not appear to be your OS drive, a restart is not required. If it was (like your c:), you would have had a different prompt asking if you want to restart.
Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N)
A file on my Seagate hard drive has corrupted, I have looked up for advice and one was to go to command prompt and this was the reply to chkdsk F: /f /r
I'm not really sure what to do.
I have been having issues ejecting the hard drive and resolved to just keep it connected as I couldn't work out a solution. While moving files (from New Folder ) into a new sub folder (in new folder) I had the error message:
F:\New folder is not accessible.
The file or directory is corrupted and unreadable.
I initially entered the command prompt incorrectly and got this back:
C:\Users\User2>chkdsk f:
The type of the file system is NTFS.
Volume label is Seagate Expansion Drive.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
70400 file records processed.
File verification completed.
1544 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
73 percent complete. (70412 of 71358 index entries processed)
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Error detected in index $I30 for file 97.
Index entry 20170421_223325.jpg in index $I30 of file 97 is incorrect.
Index entry 20170423_111602.jpg in index $I30 of file 97 is incorrect.
Index entry 20170424_110406.jpg in index $I30 of file 97 is incorrect.
Index entry 20170426_102255.jpg in index $I30 of file 97 is incorrect.
Index entry 20170426_113359.jpg in index $I30 of file 97 is incorrect.
Index entry 20170426_190839.jpg in index $I30 of file 97 is incorrect.
Index entry 20170426_195447.jpg in index $I30 of file 97 is incorrect.
Index entry 20170428_091137.jpg in index $I30 of file 97 is incorrect.
Index entry 20170428_153344.jpg in index $I30 of file 97 is incorrect.
Index entry 20170429_153031.jpg in index $I30 of file 97 is incorrect.
Index entry 20170429_154514.jpg in index $I30 of file 97 is incorrect.
Index entry 20170429_171302.jpg in index $I30 of file 97 is incorrect.
Index entry 20170429_174206.jpg in index $I30 of file 97 is incorrect.
Index entry 20170430_122419.jpg in index $I30 of file 97 is incorrect.
Index entry 20170430_172917.jpg in index $I30 of file 97 is incorrect.
Index entry 20170421_201205.jpg in index $I30 of file 97 is incorrect.
Index entry 202F22~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F26~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F26~2.JPG in index $I30 of file 97 is incorrect.
Index entry 202F42~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F47~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F5A~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F66~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F6F~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F81~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F83~1.JPG in index $I30 of file 97 is incorrect.
Index entry 202F18~1.JPG in index $I30 of file 97 is incorrect.
71358 index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
this is in Windows 7
help would be greatly appreciated,
Windows for home | Previous Windows versions | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
5 answers
Sort by: Most helpful
-
Anonymous
2023-08-21T03:06:54+00:00 -
Anonymous
2023-08-19T16:30:12+00:00 The proper command is chkdsk f: /r
That will check data integrity and attempt to fix the errors it finds then it will go on and check the readability of the unused sectors on your drive.
If this is the drive that has the OS on it, you must restart Windows to allow it to run
-
Anonymous
2023-08-19T14:21:48+00:00 Ooooo I didnt do anything, heard a bing and checked and its now visible and I'm able to access the file that was corrupted.
Thank you so very much
-
Anonymous
2023-08-19T13:53:56+00:00 Thank you, I did that and I'm now getting a
F:\ is not accessible.
Access is denied.
Do I need to restart?
C:\Users\User2>chkdsk f: /f
The type of the file system is NTFS.
Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Seagate Expansion Drive.
CHKDSK is verifying files (stage 1 of 3)...
70400 file records processed.
File verification completed.
1544 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
73 percent complete. (70412 of 71358 index entries processed)
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
Correcting error in index $I30 for file 97.
-
Anonymous
2023-08-19T13:40:53+00:00 Run chkdsk f: /f and if you receive a prompt, the answer is Y (Yes). Once it is complete you should be able to regain access to the drive to transfer files.