File Record Segment Unreadable: Fixes That Work

Updated 8 November 2026 · Standard formula, shown below

When you get a “file record segment is unreadable” error, it means Windows cannot read a critical part of the NTFS file system, often due to disk damage or corruption. Start by running chkdsk /f on the affected drive from an elevated Command Prompt, then restart; if that fails, use chkdsk /r to locate and recover data from bad sectors. This article explains why the error occurs, how to fix it step by step, and how to recover your data safely.

What Does the Error Mean?

The “file record segment is unreadable” message appears when Windows encounters a problem reading a specific entry in the NTFS Master File Table (MFT). The MFT is a database that stores information about every file and folder on the drive, including its name, size, permissions, and location. Each file or folder has a record in the MFT, and if that record becomes corrupted or the disk sector containing it goes bad, Windows cannot access the file.

This error is different from a simple “file not found” because the file system itself is damaged. It can affect a single file, a folder, or the entire drive, and it often indicates deeper issues like bad sectors, power outages, improper shutdowns, or failing hardware.

Why Does It Happen?

Several factors can cause the MFT to become unreadable:

Bad sectors: Physical damage to the disk surface can make certain sectors unreadable, including those that store MFT records.
Power failures: An abrupt shutdown while the system is writing to the MFT can leave records incomplete or corrupted.
Improper removal: Unplugging an external drive without safely ejecting it can interrupt writes and cause corruption.
Malware or viruses: Some malicious software can damage file system structures.
Hardware failure: Failing hard drives, loose cables, or faulty controllers can cause read errors.

Understanding the cause helps you choose the right fix. For example, if bad sectors are the issue, chkdsk /r is more effective than chkdsk /f.

How to Fix the Error Step by Step

Follow these steps in order. Start with the least invasive method and escalate only if needed.

Back up any accessible data immediately. If you can still access some files, copy them to another drive. Do not wait, as the drive may fail further.
Run chkdsk /f: Open Command Prompt as Administrator (right-click Start, choose “Command Prompt (Admin)” or “Windows PowerShell (Admin)”). Type chkdsk C: /f (replace C: with your drive letter) and press Enter. If the drive is in use, you’ll be prompted to schedule it for the next restart. Restart and let it run.
Run chkdsk /r: If /f does not fix the error, run chkdsk C: /r. This scans for bad sectors and attempts to recover readable information. It takes much longer but is more thorough.
Try a different cable or port: For external drives, a faulty USB cable or port can cause read errors. Try a different cable and a different port.
Use a different computer: Connect the drive to another PC and run chkdsk there. This helps determine if the problem is with the drive or your system.
Use data recovery software: If chkdsk cannot fix the MFT, you may need to recover files using specialized tools like Recuva, TestDisk, or PhotoRec. These can often recover data even when the MFT is damaged.

What to Do If chkdsk Fails

If chkdsk reports that it cannot fix the problem or the error persists, the drive may have physical damage or the MFT is too corrupted. In this case:

Stop using the drive immediately. Continuing to use it can overwrite data that might be recoverable.
Use a Linux live CD: Boot from a Linux USB stick and try to mount the drive. Linux often reads NTFS drives even when Windows cannot. Copy files to another drive if possible.
Try TestDisk: This open-source tool can rebuild the MFT or recover deleted partitions. It’s powerful but requires careful following of instructions.
Consider professional recovery: If the data is critical and other methods fail, a data recovery service may be your last option. Costs vary, but they can often recover data from severely damaged drives.

How to Prevent It in the Future

While you can’t always prevent hardware failures, you can reduce the risk of MFT corruption:

Always safely eject external drives. Use the “Safely Remove Hardware” icon before unplugging.
Use a UPS (uninterruptible power supply) for desktops to avoid power outages.
Run chkdsk regularly. Schedule a disk check monthly or after any sudden shutdown.
Monitor drive health. Use tools like CrystalDiskInfo or SMART data to check for early signs of failure.
Keep backups. The best defense is a recent backup. Use the 3-2-1 rule: 3 copies, 2 different media, 1 offsite.

Common Mistakes to Avoid

Many people make these errors when dealing with this issue:

Ignoring the error: Continuing to use the drive can worsen the damage.
Running chkdsk with the wrong flags: Using /f when /r is needed, or vice versa, can leave corruption unresolved.
Formatting the drive too early: Formatting erases the MFT and makes data recovery much harder. Only format as a last resort.
Assuming chkdsk will fix everything: chkdsk can repair logical corruption but cannot fix physical bad sectors. It marks them and tries to recover data, but some data may be lost.
Not backing up after the fix: Even after a successful chkdsk, the drive may be unstable. Back up important files immediately.

Frequently Asked Questions

Can I recover files from a drive with an unreadable file record segment?

Yes, in many cases. If the MFT record is partially readable, chkdsk /r may recover the file. If not, data recovery software like TestDisk or PhotoRec can scan the raw data and reconstruct files. The success rate depends on the extent of the damage and whether the data has been overwritten.

Is chkdsk /r safe to run?

Yes, chkdsk /r is a read-only scan that also attempts to repair bad sectors. It does not write to the disk except to mark bad sectors, so it’s safe. However, it can take hours on large drives, so plan accordingly.

What is the difference between chkdsk /f and chkdsk /r?

/f fixes logical file system errors, such as corrupted MFT records. /r does everything /f does plus it scans for bad sectors and tries to recover readable data from them. /r is more thorough but slower.

Will formatting the drive fix the error?

Formatting will erase the MFT and create a new one, which will fix the error. However, it will also erase all data on the drive. Only format after you’ve exhausted all recovery options and have backed up what you can.

Can I use the drive after fixing the error?

Yes, but with caution. If the error was caused by bad sectors, the drive may be unreliable. Monitor it closely, back up frequently, and consider replacing it if you notice more errors.

Does this error mean my hard drive is dying?

Not necessarily. It can be caused by a one-time power failure or improper ejection. However, if the error recurs or is accompanied by clicking noises, slow performance, or other SMART warnings, it may indicate a failing drive.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.