0

Short form: How do I "run an offline scan" in chkdsk?

Details:

I'm running Win 11 Pro and trying to examine and possibly resurrect an external NTFS drive which appears to be corrupted. Following the chkdsk docs in: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk?tabs=event-viewer

My first attempt was this:

>chkdsk f: /scan
The type of the file system is NTFS.
Insufficient storage available to create either the shadow copy storage file or other shadow copy data.

A snapshot error occured while scanning this drive. Run an offline scan and fix.

The documentation says that /forceofflinefix will "Bypass all online repair; all defects found are queued for offline repair (for example, chkdsk /spotfix).", so that sounds like the right thing. But I get the same error:

>chkdsk f: /scan /forceofflinefix
The type of the file system is NTFS.
Insufficient storage available to create either the shadow copy storage file or other shadow copy data.

A snapshot error occured while scanning this drive. Run an offline scan and fix.

So: how do I "run an offline scan"?

6
  • It is working fine here. Is F: too small?
    – anon
    Commented Jul 13, 2023 at 16:22
  • 2
    chkdsk is a bad idea for resurrecting drives. explain the issue and what you're trying to accomplish. if you want data back, avoid chkdsk. if not it's simpler to reformat the volume. Commented Jul 13, 2023 at 16:23
  • @JoepvanSteen This is the C: drive from another Windows 11 machine. It won't boot. When I try to mount it on my Win 11 machine, it puts up a window that it's corrupted. I want to try to salvage the files that are on the drive. What tool would you suggest? Commented Jul 13, 2023 at 16:25
  • 1
    If the data is important, you may wish to get an estimate of recovery from a local recovery agency.
    – anon
    Commented Jul 13, 2023 at 17:04
  • @fearless_fool, my personal default goto tool is DMDE. Commented Jul 13, 2023 at 18:18

1 Answer 1

0

Figured out the answer: it needed the /X option. This worked, and chkdsk managed to repair the volume:

>chkdsk f: /X /scan /forceofflinefix

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .