Conflicting results from chkdsk
0 pts.
0
Q:
Conflicting results from chkdsk
When running chkdsk /r, I get messages saying 'Windows replaced bad clusters in file ...', then at the end it says '0 KB in bad sectors'.
Can anyone explain how this can be possible? How can you have bad clusters without having bad sectors?
Regards,
Bill
ASKED: Aug 4 2006  9:18 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
0 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
If you can observe the results you would come to know that's not the conflicting output.
Chkdsk checked the clusters which are bad and removed the data from those bad clusters and placed in a new place and at the end of the process. There are bad clusters or sectors but "0 KB in bad sectors". That means no data in bad sectors. It's not saying that it doesn't have bad sectors. It's saying that there is no data in bad sectors after the repair operation."

Cheers!!!
Last Answered: Aug 8 2006  9:52 AM GMT by 9949748886   0 pts.
0
0
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

BillBald   0 pts.  |   Aug 12 2006  5:09PM GMT

Thanks for your reply. It seems very logical.
Do you mind if I ask whether you know for a fact that Chkdsk works in this way, or whether it is an educated guess?
You might be interested to know that I have checked the drive using Powermax, and it is apparently error-free. To run Powermax I had to switch the drive from the Promise controller to the standard IDE controller. I have left it connected to the IDE controller, and I don’t seem to be getting any more errors, so I suspect the problem may have been with the Promise controller.
Regards,
Bill

 

Tangor64   0 pts.  |   Aug 14 2006  6:53PM GMT

Yes, chkdsk does, in fact work this way, however, there is always the possibility of hardware creating a false-positive on the error check. Your Promise controller could be flakey, but without specific diagnostics I couldn’t say for certain. If you are not getting any performance degredation or errors on the new configuratiion, keep it that way and shelve the Promise card until you have time to test it.

 
0