Fix STATUS_FT_READ_RECOVERY_FROM_BACKUP (0x4000000A) in 5 Steps

You're staring at STATUS_FT_READ_RECOVERY_FROM_BACKUP (0x4000000A) and wondering if your drive is dead. It's not. This is actually a normal message from your storage system saying 'Hey, I had to read from the backup copy because the primary copy hiccupped.' That's the whole story. But if you're seeing it as an error in Event Viewer or during a backup job, here's how to shut it up for good.

The Fix: Clean the Disk and Check Redundancy

This error usually pops up in two places: Windows Event Viewer under System logs, or in storage management tools like Intel Rapid Storage Technology. It's not a crash. It's a notification that your RAID or Storage Spaces used the redundant copy to complete a read. Here's the step-by-step fix:

1. Open Event Viewer. Press Win + R, type eventvwr.msc, hit Enter.
2. Go to Windows Logs > System. Look for the error with source ftdisk or storport and event ID 161 or 15. That's the one.
3. Run a disk check on the affected drive. Open Command Prompt as Admin. Type chkdsk C: /f /r (replace C: with the drive letter showing in the error). Press Enter. Say yes to schedule it on next reboot if asked.
4. Restart your computer. Let chkdsk run — it can take a few hours on a big drive. After it finishes, the system boots normally.
5. Check your RAID or Storage Spaces health. Open Storage Spaces in Control Panel or your RAID management app. Look for any degraded drives. If you see a yellow warning, that drive needs replacing. If everything shows healthy, you're good.

After step 5, check Event Viewer again. You should see no new 0x4000000A errors. If you still see them, you've got a flaky drive that needs replacement.

Why This Error Happens

Your storage is fault-tolerant — RAID 1, RAID 5, Storage Spaces with mirroring, that sort of thing. When the system tries to read a sector from one disk and gets a bad result (like a read timeout or a CRC mismatch), it automatically retries the read from the other disk in the mirror or the parity stripe. That's a good thing. It means your data survived. But Windows logs this as a warning (0x4000000A) to tell you a disk had a momentary glitch.

Real-world trigger: You're copying a 50GB video file from your RAID 1 array. Halfway through, one drive takes a split-second longer to respond than usual. The system sees that as a 'read failure' on that sector — not a full crash, just a timing hiccup. So it grabs the data from the second drive, finishes the copy, and logs the event. You never notice the slowdown. But Event Viewer records it.

The real fix here isn't to stop the error from happening — it's to make sure the underlying disk is healthy. Chkdsk finds and marks those bad or slow sectors so the system won't try reading from them again. That's why step 3 is critical.

Less Common Variations

Sometimes you'll see this error in different contexts:

Backup Software Reporting It

If you see 0x4000000A inside a backup log (like from Veeam or Windows Server Backup), it means the backup job read from a replica or backup copy of a volume. That's fine — it's literally what backup software does. You can safely ignore those entries unless they're accompanied by actual data error codes like 0x8007045D (I/O device error) or 0x80070017 (CRC error).

Hyper-V or VM Storage

When running a VM on a CSV (Cluster Shared Volume) or a Storage Spaces Direct cluster, this event can pop up if the hypervisor automatically retries a read from another node's copy of the data. That's by design. It's not a problem unless it happens constantly — like every minute. Then check your network between nodes for packet loss.

Third-Party Disk Tools

Tools like HDTune or CrystalDiskInfo might flag this error as a 'warning' in their logs. If you see it once or twice a week, your disk is fine. If you see it hourly, that disk is on its way out. Replace it.

Prevention Going Forward

You don't need to panic over this error. But you do want to stop it from being a sign of something worse. Here's what I recommend:

• Run chkdsk monthly on all your drives, especially in a RAID setup. Schedule it with Task Scheduler if you're lazy like me.
• Monitor your disk health with SMART data. Use a free tool like CrystalDiskInfo. Look at the 'Reallocated Sectors Count' and 'Current Pending Sector Count'. If either is climbing, replace the drive.
• Keep your storage drivers up to date. Go to your motherboard or RAID controller manufacturer's site. Download the latest driver for your chipset or controller. Outdated drivers can cause false read errors.
• Don't ignore repeated occurrences. One or two 0x4000000A events in a month? Fine. Ten in a day? That drive is failing. Swap it out before it takes your data with it.

That's it. This error is your storage system doing its job — it's not the enemy. But if it becomes chatty, your hardware is telling you something. Listen to it.