Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Errors found. CHKDSK cannot continue in read-only mode.  (Read 15208 times)

0 Members and 1 Guest are viewing this topic.

animestan

    Topic Starter


    Greenhorn

    Errors found. CHKDSK cannot continue in read-only mode.
    « on: October 02, 2009, 01:41:07 PM »
    Errors found. CHKDSK cannot continue in read-only mode.
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\Stan>chkdsk
    The type of the file system is NTFS.
    WARNING! F parameter not specified.
    Running CHKDSK in read-only mode.
    CHKDSK is verifying files (stage 1 of 3)...
    Deleted corrupt attribute list entry
    with type code 128 in file 101013.
    Deleting corrupt attribute record (128, "")
    from file record segment 101079.
    Deleting corrupt attribute record (128, "")
    from file record segment 101096.
    Deleting corrupt attribute record (128, "")
    from file record segment 124715.
    Deleting corrupt attribute record (128, "")
    from file record segment 126850.
    Deleting corrupt attribute record (128, "")
    from file record segment 126898.
    Deleting corrupt attribute record (128, "")
    from file record segment 257165.
    Deleting corrupt attribute record (128, "")
    from file record segment 274406.
    Deleting corrupt attribute record (128, "")
    from file record segment 296505.
    Deleting corrupt attribute record (128, "")
    from file record segment 299759.
    Deleting corrupt attribute record (128, "")
    from file record segment 303759.
    Deleting corrupt attribute record (128, "")
    from file record segment 312663.
    Deleting corrupt attribute record (128, "")
    from file record segment 330632.
    Deleting corrupt attribute record (128, "")
    from file record segment 334126.
    Deleting corrupt attribute record (128, "")
    from file record segment 345900.
    File verification completed.
    Deleting orphan file record segment 101079.
    Deleting orphan file record segment 101096.
    Deleting orphan file record segment 312612.
    Errors found. CHKDSK cannot continue in read-only mode.

    My reason for running chkdsk was because:
    My pc (hard drive to be specific) had no activity during gaming (my whole pc freezes at this point). I have a small led light that blinks or dims to show HDD activity, and when my game freezes(whole pc doesnt not respond) the light turns off, I figured that there would be something wrong with the HDD.

    *I've ran a CHKDSK (the one that runs when you boot up the pc and not while you are logged in)
    BUT, I did not know the results of it. It ran, but obviously I don't have the time to wait hours for it to finish. Once I came back to check on my pc, it was at the Windows Login screen.

    patio

    • Moderator


    • Genius
    • Maud' Dib
    • Thanked: 1686
      • Yes
    • Experience: Beginner
    • OS: Windows 7
    Re: Errors found. CHKDSK cannot continue in read-only mode.
    « Reply #1 on: October 02, 2009, 02:59:14 PM »
    Quote
    obviously I don't have the time to wait hours for it to finish.

    If you don't have the patience to let it complete we cannot help you here...
    You should run chkdsk /r from the command prompt with as many running background apps shut down as possible.
       
     
    " Anyone who goes to a psychiatrist should have his head examined. "


    Allan

    • Moderator

    • Mastermind
    • Thanked: 1203
    • Experience: Guru
    • OS: Windows 10
    Re: Errors found. CHKDSK cannot continue in read-only mode.
    « Reply #3 on: October 03, 2009, 02:07:02 PM »
    Boot to the recovery console and run chkdsk /r - and leave it alone until it finishes.

    GLOOPS



      Hopeful

    • NOPAIN - NO GAIN
      • Experience: Beginner
      • OS: Windows 7
      Re: Errors found. CHKDSK cannot continue in read-only mode.
      « Reply #4 on: July 31, 2010, 07:19:25 AM »
      Patio is right here.   ;D   I have just had to replace a hard drive! CHKDSK was telling me, in effect, that the drive was done in.    I ran CHKDSK with the '/F' peramiter and it automatically repares as it goes. (or /r as patio recomends).   If after doing this, errors still occure, you are needing a new HD.  >:(  :o  ::)

      I state here, that there is nothing like running a HD testing 'gizmo', if you can find a good one.  There are plenty about.  Whatch out for 'HD Sentinel' though as it did not report my knackered drive to me, it kept telling me that it was OK!  >:(