My drive started showing bad sectors and now some important files won’t open. I’m thinking about running CHKDSK, but I’m worried it could make data recovery harder or cause more file loss. I need help understanding whether CHKDSK is safe in this situation and what I should do first to recover data from a failing hard drive.
Stop poking the drive
I learned this one the hard way. If a drive starts spitting CRC errors, freezing File Explorer, or hanging on certain folders, stop there. Don’t keep opening directories to ‘see what still works.’ If it’s external, unplug it. If it’s your main internal drive, power the machine down.
Why so strict? Because every extra read forces the drive to try again on bad spots. Windows also likes to jump in and do its own cleanup. I’ve seen a drive go from flaky to unreadable after a bunch of repeated retries. It was ugly.
Two different kinds of bad sectors
This part matters because people mix them together.
Soft bad sectors are more like broken bookkeeping. I’ve seen them show up after a crash, a sudden power loss, or a bad shutdown. The data and the error correction info no longer match, even though the hardware itself might still be fine. Sometimes those are recoverable.
Hard bad sectors are the uglier kind. That points to physical trouble. The platter surface might be damaged. The head might be wearing out. Once you’re in that territory, software isn’t fixing the drive. At best, it skips damaged areas and saves what it still can.
Why CHKDSK is a bad first move
A lot of people run CHKDSK right away. I wouldn’t.
CHKDSK is built to make a file system usable again. It is not built to preserve every last piece of damaged data. If the file system has broken links or corrupted records, CHKDSK might ‘fix’ them by cutting loose parts it can’t reconcile. Great for getting Windows to stop complaining. Not great if your goal is to recover files intact.
If the data matters, the first goal is simple. Do not change the failing disk.
What I’d do first
Make a full sector-by-sector copy to a healthy drive. Byte for byte. Then leave the original alone.
Once you have a clone or image, do all recovery work on the copy. Not on the sick drive. This lowers the risk a lot. If the scan goes sideways, your source is still untouched.
The home recovery route
For DIY recovery, I’d start with software made for unstable drives. Disk Drill is one of the better-known options, mostly because it includes byte-to-byte backup tools.
What stood out to me with newer builds is how they deal with unreadable sections. Older tools often hit one bad patch and sit there forever, grinding away. Better tools skip ahead, copy the easy readable areas first, then come back and retry the bad parts in smaller chunks. That approach puts less stress on the drive and usually gets more data off before things get worse.
A plain workflow that makes sense
- Get another healthy drive with enough free space.
- Create a full image of the failing disk.
- Load or mount the image in your recovery software.
- Scan the image, not the original disk.
- Save recovered files to a different healthy drive.
One thing I’d stick to, only power up the bad drive for the imaging step. Don’t recover files back onto it. Don’t write temp files to it. Don’t let Windows ‘repair’ it if you care about the contents.
When to stop doing DIY
If the drive clicks, grinds, beeps, won’t spin up, or doesn’t show up at all, I’d stop messing with software. Those symptoms usually point to mechanical failure. At that point, each extra power cycle feels like a gamble.
If the data matters more than the cost, send it to a lab. Places like Gillware or Techchef exist for this reason. They have cleanroom setups, donor parts, and hardware tools normal users don’t. The bill hurts, though. I usually see numbers in the $500 to $3,000 range depending on what failed and how bad it is.
After recovery
Once your recovered files are checked and open нормально, then you can think about testing or wiping the old drive. A full format or chkdsk /r might mark bad sectors so the system avoids them later. I still wouldn’t trust the drive for anything important after it starts doing this.
A drive with CRC errors and read hangs has already told you what it is.
The boring fix that saves your skin
Backups. The 3-2-1 rule is still the least painful answer.
- 3 copies of your important data
- 2 different types of storage
- 1 copy off-site or in the cloud
It takes a bit of setup. Still better than staring at a dying drive at 2 a.m. hoping one more reboot will do something different.
1 Like
No, I would not run CHKDSK first if your goal is data recovery.
CHKDSK is a repair tool. It tries to make the file system consistent. During that process, it might relink files, truncate damaged data, move entries into FOUND.000, or mark clusters bad and move on. That helps Windows mount the drive. It does not help preserve every file.
I agree with @mikeappsreviewer on the main point, stop working the drive. I disagree a bit on one detail people often miss. Not every bad sector case means instant disaster. Sometimes SMART shows a few reallocated sectors and the disk still reads fine for long enough to pull data. The key is to measure the drive first, not guess.
What I’d do:
- Check SMART before anything else.
Use CrystalDiskInfo or smartctl.
Look at:
- Reallocated Sector Count
- Current Pending Sector Count
- Uncorrectable Sector Count
If pending or uncorrectable is above 0, treat the drive as unstable.
-
Copy important files first, largest value first.
Do not sort folders, preview videos, or open random stuff. Copy the most important data off in the shortest path possble. -
If normal copying fails, image the disk.
Disk Drill is fine here because it has a byte-to-byte backup feature and recovery from the image. Work from the image, not the source drive. -
Run CHKDSK only after data is safe.
If you want syntax, people usually use chkdsk /f for file system errors and chkdsk /r if they want a surface scan plus bad sector handling. On a weak drive, /r is the heavier option and pushes more reads.
One more thing. CRC errors do not always mean bad sectors. CRC often points to cabling, USB bridge issues, or controller errors. Swap the SATA cable or enclosure first if this is an external or desktop HDD. I’ve seen a ‘failing drive’ turn out to be a bad USB cable. weird, but common.
If you want a plain-English explainer on bad block handling, this is decent:
how hard drives track and manage bad blocks
Short version. Recover first. Repair later. If the drive clicks, disappears, or slows to a crawl during reads, stop DIY and move to a lab.
CHKDSK is safe for the file system, not neccesarilly safe for the data you’re trying to save. That’s the distinction people miss.
I mostly agree with @mikeappsreviewer and @byteguru, but I’ll push back on one thing: CHKDSK is not some evil drive-killer by default. The real problem is timing. If you run it before recovery, it can rename, detach, truncate, or “clean up” damaged file records in ways that make later recovery messier. So if the files matter, don’t make CHKDSK your first move.
A better way to think about it:
- If the drive has logical corruption only, CHKDSK can help Windows read it again.
- If the drive has real unreadable sectors, CHKDSK can hammer those weak areas with extra read attempts.
- If the drive is already degrading, that extra stress is a bad bet.
Also, don’t assume “bad sectors” just because Windows says so. Sometimes the issue is cable/enclosure/controller related. Before doing anything invasive, look at the SMART health data and review SMART bad sector counts and pending sector warnings. This is a decent sanity check: how to read SMART bad sector counts before a drive dies
My order would be:
- Stop opening random folders/files.
- Check SMART.
- If the drive is still readable, get the important stuff off first.
- If reads are failing, make an image/byte-to-byte backup.
- Recover from the image.
- Only then test CHKDSK if you still care about making the volume mount cleanly.
If you want a consumer tool for that workflow, Disk Drill makes sense because it can image the disk first and then scan the image instead of the original. That’s the part that matters.
One more blunt point: if this is an SSD showing bad blocks, or an HDD that’s clicking / dropping offline / freezing the system, stop trying to “repair” it. At that point DIY gets real dumb real fast.
I’m with @byteguru, @sterrenkijker, and @mikeappsreviewer on the big picture, but I’ll add one nuance: if the drive is still readable enough to stay online, sometimes a targeted copy of just the irreplaceable files beats a full repair attempt or even a long diagnostic session. The mistake is letting Windows “work on it” before you decide.
What CHKDSK changes:
- directory entries
- file records
- allocation maps
- lost cluster handling
So yes, it can absolutely reduce recovery options if run too early.
My rule:
- Need the data: do not run CHKDSK yet
- Need the volume usable again and data is already backed up: fine, then try it
One thing not mentioned enough: check the Event Viewer for disk, NTFS, and controller errors. If you see controller resets or I/O timeouts, the issue might be broader than just surface damage. Also, if this is an external drive, avoid cheap USB hubs while copying. Direct connection only.
About Disk Drill specifically:
Pros:
- byte-to-byte backup is the right feature for shaky drives
- can scan an image instead of the original
- simple enough for non-tech users
Cons:
- not the cheapest option
- deep scans can take a long time
- if the drive is mechanically failing, software won’t save the day
So no, CHKDSK is not the safe first move for recovery. Stabilize, copy or image, recover elsewhere, repair later if you still care.