Windows 10: The disk does not have enough space to replace bad clusters

If when you run the built-in Disk Checker Utility on your Windows computer, ChkDsk throw up an error message while looking for bad clusters – A disk read error occurred, The disk does not have enough space to replace bad [...]

This post The disk does not have enough space to replace bad clusters is from TheWindowsClub.com.

read more...

 

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.

 

Getting Error message " there is insufficient free disk space to correct the bad cluster error"

Allow me to back up and ask the real question I had. I am experiencing unexplained "freezes". That is, I would be doing simple browsing, or editing a local word file, and the computer suddenly becomes totally unresponsive and stays that way for perhaps
a minute and then "recovers". I have tried keeping the task manager visible, but I appear to be using less than 50% of disk, CPU and memory.

Since I have very little visiblility as to what is actually happening, I made the following hypothesis, "there are one or more sectors that are partially bad". That is, when the disk driver tries to read the data, it initially fails and then keeps trying
until it has a success. Is this in fact what the disk driver will do?

Assuming this is the behavior of the disk driver, I want any questionable (that is, has ever had a read error, whether recovered or not) sectors or clusters to be permanently marked bad, and the data moved to a previouslly unused sector or cluster. Ideally
this should be the default behavior of the disk driver. But assuming it is not the default behavior, I would want chkdsk to do this. But the descriptions I get from chkdsk /?, and from your response, are unclear as to exactly what command line parameters
I should use.

What then is the difference between /f and /r ? Which is better for my need?

How many retries does the disk driver make, and how many does chkdsk make?

If the disk driver, upon recovering good data after several (a minutes worth of ???) retries, does not for some technical reason, transfer the data to some previously unused sector, I would like to put in a formal request that it do so. You should not expect
your average user to come up with this hypothesis, or even to know that chkdsk exists.

It sounds like /b will examine the sectors or clusters that have previously been marked bad, and give them a second chance to be removed from the bad sector/cluster list. If that is true, then I should only use this parameter if I was running very low on
disk space? Is this understanding true?

 

Getting Error message " there is insufficient free disk space to correct the bad cluster error"

Original title:chkdsk /r /b

chkdsk has new command line parameters for Win10, as revealed by using /? I tried using "/r" instead of the usual "/f", and got error saying there is insufficient free disk space to correct the bad cluster error, even though the disk was empty. I had just
done a fresh format on it. Error makes no sense. I also tried /r/b, but I am unsure what the /b is needed for.