locked
Error: "CHKDSK cannot continue in read-only mode" and "An unspecified error occured (766f6c756d652e63 3f1)" RRS feed

  • Question

  • I am having problem to run chkdsk on all my internal or external hard drives. Checking internal drives at reboot runs fine without any problem (using fsutil dirty set).

    Got same error in recovery mode, safe mode, using administrator account or UAC disabled.

    Defragment runs OK without any problem. External hard drives can be checked (no error and bad sector) on another computer (win7 pro x64).

    This computer is win7 pro x86. Clean install without any additional software.

    When using UI to do checking disk, the dialog disappears immediately after clicking "Start" button. Following are the error in elevated command line.

    C:\Windows\system32>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>chkdsk c:
    The type of the file system is NTFS.

    Errors found.  CHKDSK cannot continue in read-only mode.

    C:\Windows\system32>chkdsk d:
    The type of the file system is NTFS.

    Errors found.  CHKDSK cannot continue in read-only mode.

    C:\Windows\system32>chkdsk e:
    The type of the file system is NTFS.

    Errors found.  CHKDSK cannot continue in read-only mode.

    C:\Windows\system32>chkdsk d: /f
    The type of the file system is NTFS.
    An unspecified error occurred (766f6c756d652e63 3f1).

    C:\Windows\system32>chkdsk e: /f
    The type of the file system is NTFS.
    An unspecified error occurred (766f6c756d652e63 3f1).

    C:\Windows\system32>chkdsk c: f
    Invalid parameter - f

    C:\Windows\system32>chkdsk c: /f
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process.  Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N) n

    C:\Windows\system32>chkdsk g:     <--- G: is an external hard drive.
    The type of the file system is NTFS.

    Errors found.  CHKDSK cannot continue in read-only mode.

    C:\Windows\system32>chkdsk g: /f
    The type of the file system is NTFS.
    An unspecified error occurred (766f6c756d652e63 3f1).

    Please help me solve the puzzle.

    Thanks,

    jin

    Saturday, December 3, 2011 5:28 PM

Answers

  • Found hotfix http://support.microsoft.com/kb/2502789

    It solved my problem.

     

    • Marked as answer by Arthur Xie Wednesday, December 7, 2011 5:49 AM
    Monday, December 5, 2011 4:55 PM

All replies

  • Please see:

    How to perform disk error checking in Windows XP
    http://support.microsoft.com/kb/315265

    The situation in Windows 7 is the same. If you just run chkdsk, it runs in Read-only Mode. You need to add parameters in your commands.


    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. ”
    Monday, December 5, 2011 3:15 AM
  • I got errors. Please read detail of my post.

    Normal chkdsk should return something like following

    C:\Windows\system32>chkdsk x:
    The type of the file system is NTFS.
    Volume label is Test.

    WARNING!  F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
      256 file records processed.
    File verification completed.
      0 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)...
      282 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      256 file SDs/SIDs processed.
    Security descriptor verification completed.
      13 data files processed.
    Windows has checked the file system and found no problems.

        255999 KB total disk space.
         48216 KB in 10 files.
            16 KB in 15 indexes.
             0 KB in bad sectors.
          3235 KB in use by the system.
          2560 KB occupied by the log file.
        204532 KB available on disk.

          4096 bytes in each allocation unit.
         63999 total allocation units on disk.
         51133 allocation units available on disk.

    C:\Windows\system32>chkdsk x: /f
    The type of the file system is NTFS.
    Volume label is Test.

    CHKDSK is verifying files (stage 1 of 3)...
      256 file records processed.
    File verification completed.
      0 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)...
      282 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      256 file SDs/SIDs processed.
    Security descriptor verification completed.
      13 data files processed.
    Windows has checked the file system and found no problems.

        255999 KB total disk space.
         15448 KB in 9 files.
            16 KB in 15 indexes.
             0 KB in bad sectors.
          3235 KB in use by the system.
          2560 KB occupied by the log file.
        237300 KB available on disk.

          4096 bytes in each allocation unit.
         63999 total allocation units on disk.
         59325 allocation units available on disk.

     

    Monday, December 5, 2011 1:04 PM
  • I tried to find the root reason. I used windbg to debug the chkdsk. There may be a bug in ifsutil.dll or my computer has driver issue.

    The performance counter frequency returned on my computer is 974140. This is a netbook with AMD C60.

    The codes inside BLOCK_CACHE::Initialize (ifsutil.dll) assume the frequency is larger than 1000000. That caused "divided by zero" exception later.

    Monday, December 5, 2011 4:34 PM
  • Found hotfix http://support.microsoft.com/kb/2502789

    It solved my problem.

     

    • Marked as answer by Arthur Xie Wednesday, December 7, 2011 5:49 AM
    Monday, December 5, 2011 4:55 PM