Windows 10: Checkdisk gives always the same report: Adding 7 bad clusters to the Bad Clusters File.

Hi all,


I hope this finds you all well in these horrible days.

I just run a few weeks ago a checkdisk /f /r /x /b on a secondary and otherwise healthy drive in my Toshiba laptop. It is a mechanical HDD.

It gave me the following conclusion:

Adding 7 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

Later I repeated the test but it gave the exact same message. After this test, I realized that some of my shortcuts disappeared, but I could find them and put them back to the original folder.

And then I repeated the test again. It just keep giving me the same error.

I do not think that each time this HDD develops 7 new bad clusters. I think something is fishy about this.

What do you thing about this?

Have a nice day!

:)

 

Does chkdsk /b is working for bad cluster replaced file from another drive?

1. Got a fixed file from stage 4 of chkdsk like this. this is happened in drive #1.

Stage 4: Looking for bad clusters in user file data ... Windows replaced bad clusters in file 250 of name \temp\~1.mkv

2. Now ~1.mkv file is moved to another drive, drive #2.

3. If run chkdsk /b on drive #2, does chkdsk /b re-evaluate ~1.mkv file again and re-mark as fixed file because of bad cluster, and leaving messages about this on prompt? or just pass as normal file with no any messages?

 

Check Disk, bad clusters

Microsoft Windows [Version 10.0.17134.523]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\Sputh>cmd.exe
Microsoft Windows [Version 10.0.17134.523]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\Sputh>chkdsk E:/f/r
The type of the file system is NTFS.
Volume label is My Passport.
Fixing critical master file table (MFT) files with MFT mirror.

Stage 1: Examining basic file system structure ...
Deleting corrupt file record segment 0.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x1.
File record segment 4 is unreadable.
File record segment 5 is unreadable.
File record segment 6 is unreadable.
File record segment 7 is unreadable.
File record segment 8 is unreadable.
File record segment 9 is unreadable.
File record segment B is unreadable.
File record segment C is unreadable.
File record segment E is unreadable.
File record segment 4700 is unreadable.
File record segment 4702 is unreadable.
File record segment 4703 is unreadable.
File record segment 4704 is unreadable.
File record segment 4706 is unreadable.
File record segment 4707 is unreadable.
File record segment 4708 is unreadable.
File record segment 4709 is unreadable.
File record segment 4880 is unreadable.
File record segment 4882 is unreadable.
File record segment 4883 is unreadable.
File record segment 4884 is unreadable.
File record segment 4885 is unreadable.
File record segment 4980 is unreadable.
281344 file records processed.
File verification completed.
0 large file records processed.
23 bad file records processed.

Stage 2: Examining file name linkage ...
Removing corrupt index $O in file 18.
Removing corrupt index $Q in file 18.
Removing corrupt index $O in file 19.
Removing corrupt index $R in file 1A.
292374 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
55 unindexed files scanned.
49 unindexed files recovered to original directory.
4294967350 unindexed files scanned.
CHKDSK is recovering remaining unindexed files.
6 unindexed files recovered to lost and found.
Lost and found is located at \found.000

Creating object id file.
Creating index $O for file 11.
Inserting an index entry into index $O of file 11.
Inserting an index entry into index $O of file 11.
Inserting an index entry into index $O of file 11.
Inserting an index entry into index $O of file 11.
Inserting an index entry into index $O of file 11.
Inserting an index entry into index $O of file 11.
Inserting an index entry into index $O of file 11.
1276 reparse records processed.
Inserting an index entry into index $O of file 11.
Creating reparse point file.
Creating index $R for file 12.
Creating quota file.
Creating index $O for file 13.
Creating index $Q for file 13.
Inserting default quota record into index $Q in file 13.

Stage 3: Examining security descriptors ...
Insufficient disk space to correct errors
in index $SII of file 9.
Insufficient disk space to correct errors
in index $SII of file 9.
Insufficient disk space to correct errors
in index $SII of file 9.
Insufficient disk space to correct errors
in index $SII of file 9.
Repairing the security file record segment.
Cleaning up 60 unused index entries from index $SDH of file 9.
Cleaning up 60 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 0.
Inserting data attribute into file 1.
Inserting data attribute into file 18.
Inserting data attribute into file 19.
Inserting data attribute into file 1A.
Inserting data attribute into file 42421.
5518 data files processed.
CHKDSK is resetting Usn information...
100 percent completed.
Stage 4: Looking for bad clusters in user file data ...
The disk does not have enough space to replace bad clusters
detected in file 4881 of name .
The disk does not have enough space to replace bad clusters
detected in file 4886 of name .
The disk does not have enough space to replace bad clusters
detected in file 4887 of name .
The disk does not have enough space to replace bad clusters
detected in file 43DAF of name \SURFAC~1\PICTUR~1\CAMERA~1\WI6D24~1.MP4.
The disk does not have enough space to replace bad clusters
detected in file 43DB0 of name \SURFAC~1\PICTUR~1\CAMERA~1\WI1319~1.MP4.
The disk does not have enough space to replace bad clusters
detected in file 43DB1 of name \SURFAC~1\103NIKON\DSCN3937.MOV.

Progress: 277923 of 281328 done; Stage: 98%; Total: 22%; ETA: 6:28:29 ...

So I was running the Check disk for my external hard drive and this is where it is at and eventually stopped at for the last hour or so. I'm worried that if I try to stop it now my data may be a lost cause forever. It's been along while since the last itime
I even used the hard drive (6 plus months) so I didn't notice anything wrong with it. Is it even possible to get my data off of it now?

It eventually stopped but not because it finished. It just became unrecognizable by my computer.

 

Bad clusters - automatic repair can't get into computer?

So my computer came up with automatic repair - your pc did not start correctly. I don't want to lose my files so I tried system reset, restore, startup repair, basically everything.

I ran a chkdsk command which told me that it moved 1 bad cluster to the bad cluster file and that no further action would be required. Nothing haplened.

When I tried system restore it failed and my laptop told me to run a chkdsk /R command. When I tried this it told me the file is write protected and as I can't get into my computer I can't start command prompt as an administrator so I'm stuck. I'm desperate
not to lose my files as most aren't backed up as I was waiting to get a new memory stick.