Inside the lab follow MDrepairs on YouTube, TikTok & Instagram - visit our YouTube channel ↗

APFS File System Corruption: Can Your Data Be Recovered?

Our founder and lead technician, Joseph Montanti, handles cases personally.

Yes, data can usually be recovered from a corrupted APFS volume. APFS corruption happens when the file system's internal metadata gets damaged, broken, or becomes inconsistent. Your files are still sitting on the physical storage. The drive just can't organize or locate them anymore. Think of it like a library where someone shredded the card catalog. The books are still on the shelves. You just lost the map to find them. The actual file data can remain intact underneath broken metadata.

The tricky part? APFS is Apple's proprietary file system. It replaced HFS+ back in 2017 with macOS High Sierra, and Apple publishes an APFS Reference describing its disk structures. Reconstructing damaged APFS structures can still be difficult. Not impossible. Just harder. The tools are more specialized, the failure modes are more complex, and there are fewer people who truly understand the file system's internal structure.

If you're staring at a Mac that won't boot, Disk Utility is throwing errors, or your external drive suddenly shows up as unreadable, don't panic yet. And definitely don't start reformatting things. Get a free quote from our lab before you make it worse.

On this page

What Is APFS and Why Does It Corrupt?

APFS stands for Apple File System. Apple built it from the ground up to replace HFS+, which had been around since 1998. HFS+ was designed for spinning hard drives and small storage volumes. By 2017, Apple needed something built for SSDs, encryption, and modern storage demands. APFS was the answer.

Here's what makes APFS different from older file systems:

  • Copy-on-write (CoW) architecture. When APFS modifies data, it doesn't overwrite the original. It writes the new version to a different location first, then updates the pointer. In theory, this protects against corruption during crashes. In practice, it works most of the time. Not always.
  • Space sharing. Multiple APFS volumes can share the same physical partition (called a "container"). Your Macintosh HD and Macintosh HD - Data volumes both live in one container. If the container metadata corrupts, both volumes go down.
  • Native encryption. APFS supports full-disk encryption at the file system level. Every Mac with a T2 chip or Apple Silicon encrypts the SSD by default. This is great for security. It's terrible for data recovery if the encryption keys get lost.
  • Snapshots. APFS takes automatic snapshots before macOS updates. These snapshots are incremental copies of the file system state. Sometimes a corrupted volume can be rolled back to a healthy snapshot. Sometimes the snapshot metadata itself is corrupted.
  • Clones and extents. APFS uses a complex B-tree structure to track where file data physically lives on the drive. Files can be cloned (share the same physical blocks) and extents (contiguous data chunks) can be scattered across the volume.

So why does it corrupt? The copy-on-write design is supposed to prevent corruption, but it doesn't cover every scenario. If power cuts out mid-write, the file system might end up with orphaned blocks, broken B-trees, or inconsistent container metadata. If the SSD controller has a firmware bug, it might report a write as complete when it wasn't. If a macOS update goes sideways, the file system conversion or modification can leave things in a half-finished state.

APFS is a solid file system. But it's not bulletproof. And when it breaks, the damaged metadata can be difficult to reconstruct.

Symptoms of APFS Corruption on Your Mac

APFS corruption doesn't always look the same. Sometimes it's dramatic. Sometimes it's subtle and gets worse over weeks before you notice.

Your Mac Won't Boot

This is the big one. You press the power button, see the Apple logo, maybe a loading bar, and then nothing. Or you get a prohibitory symbol (circle with a line through it). Or the loading bar gets to about 80% and hangs forever. All of these can point to APFS corruption on the system volume.

macOS Sequoia (macOS 15) and Sonoma (macOS 14) both use a signed system volume (SSV) that's cryptographically verified at boot. If any part of that volume is corrupted, macOS refuses to load. It won't even try to limp along with damaged files. It just stops.

Disk Utility Shows Errors

You boot into Recovery Mode (Command+R on Intel Macs, hold power on Apple Silicon), open Disk Utility, and see error messages like:

  • "The volume was found corrupt and needs to be repaired"
  • "Invalid B-tree node size"
  • "Keys out of order"
  • "Object map is invalid"
  • "The container superblock is invalid"
  • "First Aid found corruption that needs to be repaired"

Some of these can be fixed by First Aid. Many can't. The worst ones involve the container superblock or the object map, because those are the master structures that everything else depends on.

Files Disappearing or Showing Zero Bytes

Your Mac boots fine, but files are missing from folders. Or they show up with the right filename but zero bytes. Or you try to open a file and get "The document could not be opened" errors. This usually means the file system's catalog B-tree has become inconsistent. The directory entries exist but they're pointing to wrong or missing extent records.

External Drive Not Mounting

You plug in your external SSD or hard drive and it doesn't show up in Finder. You open Disk Utility and the drive appears but the volume is grayed out. Or you see the container but no volumes inside it. This is extremely common with bus-powered drives that get disconnected without proper ejection.

Important: If your external drive isn't mounting, don't click "Initialize" or "Erase" when macOS prompts you. That dialog box is not trying to help you recover data. It's trying to wipe the drive and start fresh. Click "Ignore" or just close the dialog.

Kernel Panics During File Access

Your Mac randomly crashes with a kernel panic when you try to access specific files or folders. The crash log references APFS or storage-related kernel extensions. This often indicates corruption in the file system's space manager or allocation bitmap, where the drive thinks free space and used space overlap.

Common Causes of APFS File System Corruption

Understanding what caused the corruption helps us figure out how to recover the data. Different causes lead to different types of damage, and some are much more recoverable than others.

Power Loss During Writes

A MacBook battery dies mid-operation. An external drive gets unplugged while files are being written. A desktop Mac loses power during a Time Machine backup. APFS's copy-on-write design handles this better than HFS+ did, but it's not perfect. The container superblock, the checkpoint structures, or the space manager can all end up in an inconsistent state if power drops at exactly the wrong millisecond.

Laptops are partially protected because macOS uses power management to prioritize completing writes. But if the battery is degraded and shuts off abruptly instead of going through a graceful shutdown, all bets are off.

Failed macOS Updates

macOS updates modify the APFS volume structure. Major version upgrades (like going from Ventura to Sonoma, or Sonoma to Sequoia) can reorganize volumes, update the signed system volume, and change the container layout. If an update fails partway through, due to power loss, insufficient storage, or a bug, the file system can end up half-converted.

SSD Wear and Controller Failures

Every SSD has a finite number of write cycles. As NAND flash cells wear out, they start producing read errors. The SSD controller handles this transparently, up to a point, by remapping bad blocks and using error correction. But when too many cells degrade, the controller can't keep up. Data gets silently corrupted. Reads return garbage. The file system metadata stored on those worn cells becomes unreadable.

Apple's internal SSDs generally have excellent endurance ratings. But they're not immune. A 2018 MacBook Pro that's been used heavily for seven years has had a lot of write cycles. If the SSD's health is declining, APFS corruption is often the first visible symptom.

According to Apple's support documentation on Mac startup issues, First Aid from Recovery Mode is a repair option. If this drive holds your only copy, make a full drive copy or recover your files to another drive before repairs. Step 5 below covers copying readable files through another Mac.

Third-Party Software Conflicts

Some third-party software interacts with APFS in ways that can cause problems. Disk cloning tools, partition managers, and bootcamp utilities sometimes make assumptions about APFS structure that aren't accurate.

Virtualization software can also cause issues. Running Parallels or VMware with a virtual machine stored on an APFS volume creates a lot of small, rapid writes. If the VM crashes mid-write, the underlying APFS volume can get damaged.

Hardware Issues Beyond the SSD

Bad RAM can cause APFS corruption. If corrupted data in memory gets written to disk, the file system metadata on disk becomes corrupted even though the SSD itself is fine. Similarly, a failing USB cable on an external drive can cause incomplete or garbled writes that look like file system corruption.

APFS Internal Structure (and Why It Matters for Recovery)

You don't need a computer science degree to follow this. But understanding the basics of how APFS organizes data will help you understand why some corruption is fixable and some isn't.

The Container Layer

APFS uses a two-layer system. The outer layer is the container (also called the APFS partition). A container occupies a physical partition on the drive. Inside that container, you can have multiple volumes that share the same pool of storage space.

On a typical Mac, the APFS container holds at least two volumes:

  • Macintosh HD (the read-only system volume)
  • Macintosh HD - Data (your user files, applications, settings)

macOS Catalina split these into separate volumes in 2019. Before that, everything lived on one volume. The system volume is now cryptographically signed and sealed. You can't modify it at all during normal operation. Your actual data lives on the Data volume.

The Container Superblock

The container superblock is the most critical structure in APFS. It's the master record that tells the system where everything else is located. It contains pointers to the space manager, the object map, the volume records, and the checkpoint structures. If the container superblock is corrupted, the entire container and all its volumes become inaccessible.

The good news: APFS keeps multiple copies of the container superblock at known locations. If the primary copy is damaged, recovery tools can sometimes find and use a backup copy. Apple also maintains checkpoint records (previous states of the superblock) that can be used to roll back to a consistent state.

B-Trees Everywhere

APFS uses B-tree data structures extensively. The file system catalog (which maps filenames to their data locations) is a B-tree. The extent records (which track where file data physically lives on the disk) are stored in B-trees. The object map (which translates virtual object IDs to physical disk locations) is a B-tree.

When a B-tree node gets corrupted, the tree can become "unbalanced" or have keys out of order. This can make entire branches of the tree inaccessible. If the root node of the catalog B-tree is damaged, the volume looks empty even though all the file data is still on the disk.

Why This Matters for Recovery

The level of corruption determines the recovery approach:

Corruption Level What's Damaged Recovery Difficulty
Level 1: Minor Individual file catalog entries, directory records First Aid can often fix this
Level 2: Moderate B-tree nodes, extent records, space manager Needs specialized tools, high success rate
Level 3: Severe Container superblock, object map, volume headers Requires manual reconstruction, moderate success
Level 4: Critical Superblock + encrypted volume + no backup keys Extremely difficult, sometimes impossible

The file data is intact on the disk. We just need to rebuild or bypass the damaged metadata structures to access it.

DIY Steps: What You Can Safely Try First

Before you call a professional, there are a few things you can try yourself. Use the repair steps below after making a drive copy or recovering your files.

Step 1: Boot into Recovery Mode

1 Access Recovery Mode

Intel Macs: Restart and hold Command+R until you see the Apple logo or a spinning globe.

Apple Silicon Macs (M1/M2/M3/M4): Shut down completely. Press and hold the power button until you see "Loading startup options." Click Options, then Continue.

If Recovery Mode won't load from the internal drive, try Internet Recovery: Command+Option+R on Intel Macs. For Apple Silicon Macs, follow the startup-options steps above.

Step 2: Run First Aid in Disk Utility

2 Run First Aid

Open Disk Utility from the Recovery Mode menu. In the sidebar, start with the last volume in your APFS container. Click First Aid, then Run. Let it complete. Work upward through the other volumes.

Then run First Aid on the container, followed by the physical storage device.

What to look for: If First Aid says "The volume appears to be OK" after repairs, try restarting. If it says "Corruption was found that needs to be repaired" but can't fix it, you need professional help.

Step 3: Try fsck_apfs from Terminal

3 Use fsck_apfs

From Recovery Mode, open Terminal (Utilities > Terminal). Run:

diskutil list

Find your APFS container identifier (looks like disk2s1 or similar). Then run:

fsck_apfs -y /dev/diskXsY

Replace diskXsY with your actual container device. The -y flag tells it to automatically attempt repairs. Use it on your working copy or after recovering your files.

Warning: If fsck_apfs cannot repair the file system, move on to the recovery options below.

Step 4: Check for Snapshots

4 Roll Back to a Snapshot

APFS creates snapshots automatically before macOS updates. If the corruption happened recently, there might be a pre-corruption snapshot available. From Terminal in Recovery Mode:

diskutil apfs listSnapshots diskXsY

If you see snapshots from before the corruption started, you might be able to restore from one. This is a complex process, though, and you should research the exact commands for your macOS version before attempting it. A wrong command here can delete the snapshots you're trying to use.

Step 5: Try Target Disk Mode / Mac Sharing Mode

5 Connect to Another Mac

Intel Macs: Boot into Target Disk Mode by restarting and holding the T key. Connect to another Mac via Thunderbolt or USB-C cable. The corrupted drive will appear as an external volume on the healthy Mac.

Apple Silicon Macs: Use Mac Sharing Mode instead. Shut down, hold the power button, select Options, then go to Utilities > Share Disk. Connect to another Mac via cable.

Sometimes a corrupted APFS volume that won't boot can still be read as an external volume on another Mac. If it mounts, immediately copy your important files to a different drive. Don't try to repair it. Just get the data off first.

Stop if: You hear clicking or grinding noises from a hard drive (Fusion Drives have a physical disk component). You see input/output errors repeatedly in Terminal. Disk Utility shows the drive as "Uninitialized" or doesn't show it at all. These symptoms suggest hardware failure, not just file system corruption, and continued attempts can cause permanent data loss.

When DIY Fails: Professional APFS Data Recovery

If First Aid can't fix it, fsck_apfs can't fix it, and the drive won't mount on another Mac, you're looking at professional recovery. Here's what that actually involves. No mystery, no magic. Just specialized tools and a lot of experience.

Imaging the Drive First

The first thing we do is create a bit-for-bit image of the entire drive. We never work on the original. Every read from a damaged drive risks making the damage worse, especially with SSDs where the controller might decide to garbage-collect or TRIM data during the imaging process. We use hardware write-blockers to prevent any writes to the source drive during imaging.

For modern encrypted phones and computers, recovery normally depends on restoring the original hardware sufficiently to unlock and extract the data. Removing storage does not bypass hardware-bound encryption. Supported older unencrypted devices are a separate case, and must be identified individually. On T2 and Apple silicon internal storage, preserving the original hardware encryption path is essential even when FileVault was not enabled.

Parsing the APFS Structures

Once we have a complete image, we use specialized tools to parse the APFS structures manually. This isn't like running a consumer recovery app. We're looking at the raw hex data, examining container superblocks, walking B-tree structures, and identifying which metadata is damaged versus which is intact.

See the documentation for R-Studio and TestDisk/PhotoRec.

Rebuilding Metadata

In many cases, the actual corruption is limited to a small portion of the metadata. The container superblock might be damaged, but the backup copies or checkpoints are intact. The catalog B-tree might have a few corrupted nodes, but the majority of the tree is fine. We can often reconstruct the missing pieces by cross-referencing redundant structures within APFS.

APFS stores a lot of redundant information. Object IDs, extent references, inode records. Even when one structure is destroyed, others contain enough information to rebuild a map of where files live on the disk.

Raw Data Carving (Last Resort)

If the APFS metadata is too damaged to reconstruct, we fall back to raw data carving. This means scanning the raw disk image for file signatures (file headers and footers) and extracting files based on their content rather than their file system entries. You lose filenames, folder structure, and modification dates. But you get the actual data back.

Raw carving works well for common file types like photos (JPEG, HEIC, PNG), videos (MOV, MP4), documents (PDF, DOCX), and databases (SQLite). It works poorly for file types without distinctive headers or for files that are heavily fragmented across the disk.

APFS Encryption and Recovery: The T2/M-Series Problem

This is where apfs corruption data recovery gets genuinely complicated. Apple's hardware encryption is powerful. That's the problem.

How APFS Encryption Works

Every Mac with a T2 security chip (2018 and later Intel Macs) or Apple Silicon (M1 and later) encrypts the internal SSD by default. Always. Even if you never turned on FileVault. The encryption is hardware-level, handled by the Secure Enclave on the T2 or the M-series chip. Data is encrypted with AES-256 before it's written to the NAND flash and decrypted on the fly when it's read.

The encryption keys are tied to the specific T2 or M-series chip on that specific logic board. This is a critical detail. A failed logic board does not always mean the T2 or M-series chip has failed. Repairing the original board can sometimes restore access to its encrypted storage.

What This Means for Recovery

If the APFS corruption is purely a file system issue and the hardware (logic board, T2/M-series chip) is working, encryption isn't a problem. The chip can still decrypt data normally. We boot into Recovery Mode, image the decrypted volume, and work from there.

If the logic board is dead, the situation changes dramatically:

  • T2 Macs (2018-2020 Intel): The SSD is a removable module on some models, but the data is encrypted with keys stored on the dead T2 chip. Without a working T2, the data is unreadable. Logic board repair can sometimes restore access if the T2 chip itself isn't the component that failed.
  • Apple Silicon Macs (M1 and later): Some Apple Silicon Macs have removable storage modules. Removing them doesn't bypass the Mac's hardware encryption. And the encryption keys are in the M-series chip. If that chip is dead, the data is gone. Period. There is no backdoor, no master key, no workaround. Apple designed it that way intentionally.
Critical warning: If your Mac's logic board is failing (random shutdowns, display issues, no power), get the data off immediately while the board still works. Once the T2 or M-series chip dies completely, professional recovery of encrypted data becomes nearly impossible. Back up NOW. Don't wait.

FileVault Adds Another Layer

FileVault is Apple's user-facing encryption feature. On T2 and Apple Silicon Macs, it doesn't actually add a new layer of encryption (the hardware encryption is always on). What FileVault does is require your login password or recovery key to unlock the encryption keys at boot time.

If FileVault is on, you need either your password or your FileVault recovery key to access the data during recovery. If you've lost both, and you didn't store the recovery key with Apple (iCloud), the data is permanently inaccessible. We can't crack FileVault. Nobody can, at least not with current technology.

On older Macs without T2 chips (pre-2018), FileVault uses software-based encryption. Recovery is more feasible in these cases because the encryption keys are derived from your password, which can be attempted with brute force if you remember part of it.

Fusion Drive APFS Corruption: Double the Trouble

Apple's Fusion Drive combines a small SSD (usually 24GB or 128GB) with a traditional hard drive (1TB, 2TB, or 3TB) into a single logical volume. macOS manages data placement automatically, keeping frequently used files on the fast SSD and less-used files on the spinning disk.

Here's the problem: when Apple switched Fusion Drives to APFS (starting with macOS Mojave), both the SSD and the HDD became part of a single APFS container. The APFS metadata and container structures are primarily stored on the SSD portion. Your actual file data is spread across both drives.

Why Fusion Drive APFS Corruption Is Worse

If the SSD portion fails or corrupts, you lose access to the APFS metadata for the entire Fusion Drive. Even though file data might still be sitting on the hard drive, the file system can't locate any of it because the map (metadata on the SSD) is gone.

And it gets worse. If the Fusion Drive "splits" (the SSD and HDD stop being recognized as a pair), macOS often tries to "help" by offering to reformat one or both drives. If you accidentally click the wrong button, that data is overwritten.

Recovering from a Split Fusion Drive

We can usually recover data from a split Fusion Drive, but it requires manually reconstructing the relationship between the SSD and HDD components. We image both drives separately, then use specialized tools to map the APFS extent records (from the SSD image) to the file data blocks (on the HDD image). It's time-consuming work, but the success rate is high as long as neither drive has been reformatted.

If you have a Fusion Drive iMac and it's acting strange, check out our hard drive data recovery page for more about what we do with mechanical drives.

Recovery Success Rates and Costs

Honest numbers from our lab. No inflated statistics, no misleading claims.

Success Rates by Corruption Type

Scenario Typical Success Rate Notes
Minor APFS corruption (First Aid partially repairs) 95%+ Often recoverable at home with proper tools
Moderate corruption (B-tree damage, volume won't mount) 85-90% Needs professional tools, excellent prognosis
Severe corruption (container superblock damaged) 70-80% Requires metadata reconstruction
Encrypted + logic board failure 30-50% Depends on whether T2/M-chip can be revived
Fusion Drive split 80-85% Good if neither drive was reformatted
SSD hardware failure + APFS corruption 50-70% Depends on NAND chip health and TRIM status

What Does APFS Recovery Cost?

Professional APFS data recovery typically falls in these ranges:

  • Software-level corruption only (drive is healthy): $300 to $800. This covers cases where the physical hardware is fine but the file system is damaged. Imaging is straightforward, and recovery involves parsing and reconstructing APFS structures.
  • SSD hardware issues + APFS corruption: $800 to $1,500. When the SSD controller or NAND chips are failing, we need to work around hardware problems before we can even start the file system recovery.
  • Logic board repair for T2/Apple Silicon access: $500 to $1,200 for the board repair, plus the data recovery cost. This is for cases where we need to fix the logic board to access the encryption keys before we can decrypt and recover the data.
  • Fusion Drive recovery: $400 to $1,000, depending on whether the HDD portion also has physical damage.

The $100 diagnostic is credited toward a successful recovery and is non-refundable once diagnostics start. Donor drives or replacement parts you approve are non-refundable once ordered, even if recovery fails. You review and approve the estimate before recovery work starts.

How to Prevent APFS Corruption

Prevention is always cheaper than recovery. Here's what actually works.

Use Time Machine (Seriously)

Time Machine is built into macOS. It's free. It backs up your entire system, including APFS snapshots and all your files. Buy a $60 external hard drive, plug it in, turn on Time Machine. That's it. If your APFS volume corrupts tomorrow, you restore from backup and lose maybe a day's work instead of everything.

Time Machine backs up to HFS+ or APFS on the backup drive. Even if your main drive's APFS corrupts, the backup drive is independent. Different volume, different container, different APFS structures.

Eject External Drives Properly

This sounds basic. It is basic. macOS buffers writes to external drives. When you yank the cable without ejecting, those buffered writes never complete, and the file system metadata becomes inconsistent.

Right-click the drive in Finder, click Eject. Wait for it to disappear from the sidebar. Then unplug. Every single time. No exceptions.

Keep macOS Updated

Apple regularly releases APFS bug fixes in macOS updates. Some of these fix corruption bugs that you don't even know exist until they bite you. Use Software Update to get the latest updates compatible with your Mac.

Don't skip updates. But also don't install major updates (like going from Sonoma to Sequoia) on day one. Wait a week or two for the early adopters to find any serious bugs. And always back up before updating.

Monitor SSD Health

macOS doesn't make this easy, but you can check your SSD's health from Terminal:

diskutil info disk0 | grep "SMART Status"

If it says "Verified," no SMART failure is reported, but that doesn't rule out a failing drive. If it says "Failing," back up everything immediately and plan to replace the drive.

For more detailed SMART data on external drives, third-party tools like DriveDx can show wear level, bad block counts, and temperature history.

Use a UPS for Desktop Macs

If you have a Mac mini, Mac Studio, Mac Pro, or iMac, plug it into an uninterruptible power supply (UPS). A basic UPS costs $50 to $100 and gives you 5 to 10 minutes of battery backup during a power outage. That's enough time for macOS to save pending writes and shut down gracefully. It's cheap insurance against power-loss corruption.

Don't Use Cheap USB Hubs

Cheap USB hubs with insufficient power delivery cause data corruption on external drives. The hub can't provide enough power for the drive to maintain stable writes, so writes fail silently. Use the cable that came with the drive. If you need a hub, get one with its own power supply.

Frequently Asked Questions

Can I recover data from a corrupted APFS drive myself?

Sometimes. If the drive mounts on another Mac via Target Disk Mode, you can copy your files to a different drive without professional help. Try First Aid only after copying or recovering them. But if First Aid fails, the drive won't mount, and you can't access it through Terminal, don't keep trying different software tools. Each attempt risks making the corruption worse, especially on SSDs where the controller might start TRIMming data during mount attempts. If your data is important, stop and contact a professional.

Is APFS corruption data recovery harder than HFS+ recovery?

Yes. HFS+ has been around since 1998. Recovery tools for HFS+ are mature, well-tested, and widely available. APFS is newer and more complex (copy-on-write, space sharing, native encryption, snapshots), but Apple publishes an APFS Reference describing its disk structures. The Apple developer documentation on APFS covers the basics; the separate APFS Reference describes the internal structures used in recovery. Third-party developers have reverse-engineered much of it, but there are still edge cases that can surprise even experienced recovery engineers.

Will reformatting fix APFS corruption?

Reformatting creates a fresh, uncorrupted APFS volume. So technically yes, it fixes the corruption. But it also erases all your data. That's not a fix. That's giving up. Only reformat after you've either recovered your data or accepted that the data is gone. And even after reformatting, if the underlying cause was hardware failure (bad SSD sectors, failing controller), the new volume will corrupt too. Fix the hardware problem first.

How long does APFS data recovery take?

At MDrepairs, the standard recovery estimate is 4–6 weeks, though timing may vary by case. The queue, parts, drive condition, imaging and delivery affect the schedule. Diagnosis isn't the same as completed recovery.

Can Apple recover data from a corrupted APFS drive?

No. Apple doesn't offer data recovery services. If you bring a Mac with a corrupted APFS volume to an Apple Store, they'll try First Aid. Reinstalling macOS normally keeps your apps and personal files, but erasing the disk first removes them. Apple's Genius Bar technicians are trained to fix the computer, not to recover data from it. They'll refer you to a third-party data recovery company.

Does APFS corruption mean my SSD is failing?

Not necessarily. APFS corruption can happen on a perfectly healthy SSD due to power loss, software bugs, or failed updates. But if you're seeing APFS corruption repeatedly, or if Disk Utility keeps finding new errors after you've repaired them, that's a strong signal that the SSD might be degrading. Run a SMART check and monitor the drive's health. If the SSD is reporting errors, replace it before you lose more data.

What's the difference between APFS corruption and a dead SSD?

APFS corruption means the file system's organizational structures are damaged, but the physical storage hardware still works. You can usually image the drive and extract data from the image. A dead SSD means the storage hardware itself has failed. The SSD controller, NAND flash chips, or firmware are non-functional. The drive doesn't respond at all, or it responds but returns only errors. A dead SSD may need specialist work on its controller, NAND, or encryption hardware, which is much more complex and expensive than fixing file system corruption.

Get help with data recovery

Bring your device to our Lincroft lab during opening hours, or mail it in.

How to mail your device

The $100 diagnostic is non-refundable once diagnostics start, and donor drives or replacement parts you approve are non-refundable once ordered, even if recovery fails.

Published by MDrepairs

MDrepairs is a data recovery and electronics repair lab in Lincroft, New Jersey. Our founder and lead technician Joseph Montanti films real cases for our YouTube channel, showing tools, repair steps and recovery outcomes.

Keep reading

Data recovery services

Devices recovered at our lab

These rows come from BenchKey, the ticket system we built for our own shop. Customer names, contact details and descriptions are left out.

Stereo microscope at the bench with a keyboard to the right
Behind the microscope in our Lincroft lab are a power supply, soldering station and parts drawers.
4.6 · 345 Google reviews$100 diagnostic, credited toward a successful recovery
Start your mail-in recovery