Share via

Fix Disk Errors - chkdhk - Process does not finish

Stefan 0 Reputation points
2026-06-19T19:22:17.8333333+00:00

Hello, I am using an old HDD for storage of files and Windows started notifying me today that I should Restart so it can fix disk errors.

I tried that and it went through stages 1/3 and 2/3 (got to 99%) but then it failed and started over. The second attempt went similarly (stage1/3 and then stage 2/3) but it just booted Windows normally after that. Shortly after, I got the same prompt to Restart to fix disk errors.

I tried using "Error Checking" from Properties->Tools and it seemed to go the same way - the progress bar filled up once and tarted over (Stage 1/3) then after it did Stage 2/3 it gave an error message. Here it is, based on the Event Logger:

Chkdsk was executed in read/write mode.

Checking file system on D:

Volume label is Local Disk.

Stage 1: Examining basic file system structure ...

Read failure with status 0xc000009c at offset 0xc899f800 for 0x400 bytes.

File record segment 2267E is unreadable.

428544 file records processed. File verification completed.

Phase duration (File record verification): 7.27 minutes.

1863 large file records processed. Phase duration (Orphan file record recovery): 8.61 milliseconds.

1 bad file records processed. Read failure with status 0xc000009c at offset 0xc899f000 for 0x400 bytes.

Read failure with status 0xc000009c at offset 0xc899f400 for 0x400 bytes.

Read failure with status 0xc000009c at offset 0xc899f800 for 0x400 bytes.

Read failure with status 0xc000009c at offset 0xc899fc00 for 0x400 bytes.

Phase duration (Bad file record checking): 30.22 seconds.

Stage 2: Examining file name linkage ...

724 reparse records processed. An unspecified error occurred (696e647863686b2e 733).

The drive seems to be working normally despite the warning from Windows and I am wondering whether to keep using it or maybe salvage what data I can and Format the drive...

Windows for home | Windows 11 | Files, folders, and storage
0 comments No comments

2 answers

Sort by: Most helpful
  1. Igor Leyko 111K Reputation points Independent Advisor
    2026-06-19T19:58:08.3166667+00:00

    Hi,

    likely this means corrupted file structure on the drive or bad sectors on the drive.

    Please check drive's health using third-party CrystalDiskInfo tool and show the tool's window with all data.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-06-19T19:22:35.61+00:00

    The disk is experiencing read failures and file system corruption that chkdsk cannot fully repair. Continued use risks further data loss. Priority should be to back up data and then treat the disk as unreliable.

    Recommended steps:

    1. Back up data immediately
      • Copy all important files from the affected HDD (D:) to another healthy drive or external storage.
      • Focus first on irreplaceable data (documents, photos, etc.). Some files in bad sectors may fail to copy; note which ones fail.
    2. Run a non‑destructive scan to assess health
      • Open an elevated Command Prompt and run:
             chkdsk D: /scan
        
      • This checks the file system and disk surface without taking the volume offline or making changes, as described in the disk corruption guidance.
    3. Attempt repair only after backup
      • If data is backed up, schedule a full repair during a maintenance window, because the disk will be unavailable and repairs can be time‑consuming:
             chkdsk D: /f /r
        
      • /f fixes logical file system errors; /r locates bad sectors and attempts to recover readable data.
      • If chkdsk reports it cannot run because the volume is in use, allow it to schedule the check for the next restart.
    4. If chkdsk still fails or errors persist
      • The repeated read failures and unspecified error indicate underlying disk problems (bad sectors or failing disk subsystem).
      • If chkdsk /f /r does not complete successfully or errors continue to appear in Event Viewer, the disk should be considered unreliable.
      • At that point, rely on the backup and replace the HDD rather than continuing to use it for important data.
    5. When to stop using the drive
      • Event logs showing read failures and file record segments that are unreadable, combined with repeated chkdsk failures, match scenarios where Microsoft guidance recommends verifying hardware and, if structural problems persist, replacing the disk as soon as possible.

    In summary: back up everything now, run chkdsk D: /scan and then chkdsk D: /f /r once, and if errors persist or the process cannot complete, retire the drive and restore data to a new disk.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.