none
When chkdsk always finds errors

    Question

  • Hi,
    I have a question regarding repeated errors found with chkdsk /f. Over the years, I have experienced the situation where you will have a server that have logical disk errors. After running chkdsk /f, it fixes errors but doing a chkdsk read-only, there are errors found. No matter how much time you do the chkdsk /f, errors are always found and repaired. I won't get into details for now but I've seen that situation a couple of times over the years. For almost all of them, it did not produce a problem but for some it has. Of course when this happens, you cannot clone to another server since they are logical errors (MFT) that will migrate even when cloned to another box.
    My question is, when this happens, is there an alternate solution then to format the machine and start over again?
    Thanks
    Tuesday, June 07, 2011 9:13 PM

Answers

  • Hi,

     

    It seems that you have bad disk sectors that cannot be fixed by CHKDSK.

     

    Based on the current situation, I would like to suggest you run HD Tune to scan the hard disk for errors. For your reference, you may refer to the following link to download the HD Tune trial version.

     

    http://www.hdtune.com/

     

    Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

     

    If it indicates that the hard disk is corrupted, please contact the hardware vendor for repair.

     

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Mr XMVP Wednesday, June 08, 2011 6:48 AM
    • Marked as answer by sleb123 Wednesday, June 08, 2011 1:52 PM
    Wednesday, June 08, 2011 5:12 AM
    Moderator

All replies

  • Hi,

     

    It seems that you have bad disk sectors that cannot be fixed by CHKDSK.

     

    Based on the current situation, I would like to suggest you run HD Tune to scan the hard disk for errors. For your reference, you may refer to the following link to download the HD Tune trial version.

     

    http://www.hdtune.com/

     

    Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

     

    If it indicates that the hard disk is corrupted, please contact the hardware vendor for repair.

     

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Mr XMVP Wednesday, June 08, 2011 6:48 AM
    • Marked as answer by sleb123 Wednesday, June 08, 2011 1:52 PM
    Wednesday, June 08, 2011 5:12 AM
    Moderator
  • It's a good suggestion. Thanks for the tool. I'll use it the next time I have this error on a server. I always took for granted that I did not need those kind of tools since it always said "0 kb in bad sectors" meaning that the problem is not physical so no need to scan with manufacturer disk tools or others alike but based on your answer, it seems that there could be physical errors even though chkdsk does not see them.
    Thanks for your post.
    Regards
    Wednesday, June 08, 2011 1:56 PM
  • If only so that other's reading this can see the resolution I found, I had this issue with several computers in the past, and 2 such computers right now.

    HDD surface scans, SMART attributes and a full thorough RAM test ruled out obvious hardware reasons.

    As above, loading into Windows, a read only checkdisk run reported errors and suggested /F to correct them, which didn't resolve or even find errors once run. Running from a preinstallation environment or with the HDD in question attached to another PC with Windows installed, a read only checkdisk ran with no issues.

    I tried loading into Safe mode, and the read only checkdisk ran fine. Loaded into diagnostic mode using system configuration (MSCONFIG) and it reoccurred.

    Long story short, on one of the PCs it turned out to be caused by the anti-virus program, the services run in diag mode, but not safe mode, and once uninstalled, the checkdisk errors disappeared. In this instance the AV program used was SEP version 12 of some flavour.

    The other PC seemed to be caused by something else, as uninstalling SEP hasn't resolved it.

    Wednesday, September 25, 2013 11:02 AM