APFS
APFS Volume Not Mounting
Recover files before changing APFS structures.
An APFS volume can be present but unmountable when volume metadata, container records, or encryption state cannot be opened normally. Checking system logs with the Console app can reveal the specific mount failure reason, which helps determine whether a scan or professional service is the right next step.
First: do not make the source worse
Treat this as a recovery situation before you treat it as a repair task. The priority is to preserve readable data and avoid new writes to the affected device.
- Do not erase the APFS volume to make it mountable.
- Do not change the volume role to force a mount.
- Do not run First Aid repeatedly on the unmountable volume.
- Do not save recovered files back into the same APFS container.
Scan and preview first
Refindo can scan a detectable APFS device or volume and preview recoverable files without modifying the source.
Likely causes
- APFS volume metadata corruption.
- Container mapping or snapshot-related inconsistency.
- Unsafe removal, power loss, or failed macOS update.
- SSD TRIM and overwrite activity after deletion or formatting.
Read-only recovery workflow
- Keep the APFS device connected and grant Refindo full disk access.
- Open Refindo and select the unmounted APFS volume or its container.
- Run Quick Scan, then Deep Scan when volume metadata is damaged.
- Preview recoverable files and save them to a separate destination.
When to stop self-recovery
- Disk Utility reports hardware errors or the device disappears during scans.
- The unmountable volume holds the only copy of critical work.
- Encryption credentials for the volume are unavailable.
- Files were deleted on an SSD where TRIM may have cleared blocks.
Related recovery guides
What You Need to Know
Mount Failure Log Locations
When an APFS volume fails to mount, macOS logs the reason in the system log accessible through Console.app or the log command. Search for "mount" or "apfs" in the log stream around the time of the failure. Common entries include metadata checksum mismatches, encryption unlock failures, and volume role conflicts that explain why the mount was refused.
Volume Role Impact on Mounting
Each APFS volume has a role property such as System, Data, Recovery, or no role. macOS treats volumes differently based on their role. A volume with a System role requires signed system files and sealed snapshots. If the role metadata is corrupted or misassigned, macOS may refuse to mount an otherwise intact volume.
Frequently Asked Questions
Should I erase the APFS volume?
No. Erasing creates new structures and can reduce recovery options.
Can an unmounted APFS volume be scanned?
Yes, when the device is detectable and readable enough for a scan.
Does TRIM affect APFS recovery?
Yes. On SSDs, deleted blocks may be cleared quickly after TRIM.
Where can I find APFS mount error messages on Mac?
Open Console.app and filter for "apfs" or "mount" messages. You can also run "log show --predicate 'subsystem == "com.apple.filesystems.apfs"' --last 1h" in Terminal.
Can changing the volume role fix a mount failure?
Manually changing the volume role is risky and can make things worse. It should only be attempted after data has been recovered or backed up.