Skip to content
How to Fix Apple Error 69716: Storage system verify failed: APFS transaction range overlapMappleCare Community ↗
Error 69716 macOS / Disk Utility APFS Snapshot Conflict

How to Fix Apple Error 69716: Storage system verify failed: APFS transaction range overlap

Reference ID: Error 69716 •

1. Overview & Failure Manifestation

Error 69716 manifests during fsck_apfs -n (verify-only) or diskutil verifyVolume operations on APFS volumes containing active snapshots. The exact Console log entry appears as:

kernel: (apfs) apfs_verify_snapshots: transaction range overlap detected: snap_xid=0x1a2b3c4d, fs_xid=0x1a2b3c50, overlap=0x3
kernel: (apfs) apfs_verify_volume: snapshot verification failed (err=69716)
Disk Utility: "Storage system verify failed: APFS transaction range overlaps snapshot transaction."
Finder Alert: "The volume 'Macintosh HD' could not be verified completely. Error: 69716."

Immediate device behavior: The volume remains mounted read-write but enters a verification-degraded state. Time Machine local snapshots (com.apple.TimeMachine.*) become ineligible for new backup captures. The snapshot_util daemon logs APFS_EOVERLAP (0x1108C) to /private/var/log/fsck_apfs.log. No kernel panic occurs; however, diskutil apfs listSnapshots shows affected snapshots with VERIFICATION_FAILED status. The overlap indicates that the filesystem’s current transaction ID (XID) allocation window has collided with a preserved snapshot’s transaction range, violating APFS’s copy-on-write (CoW) isolation guarantee. This typically follows an unclean shutdown during active snapshot coalescence or a metadata journal replay that incorrectly advanced the superblock’s apfs_superblock_t.apfs_last_xid past a pinned snapshot’s apfs_snap_meta_t.snap_max_xid.

2. Silicon & Firmware Architecture Root Cause

At the silicon level, the APFS transaction overlap originates in the Storage Controller Firmware (SCF) on Apple Silicon (M1/M2/M3) or the SSD Controller (NVMe/PCIe) on T2-equipped Intel Macs. The NAND flash translation layer (FTL) manages logical-to-physical block mapping via the Object Map (omap), which tracks every filesystem object’s physical extent. During a snapshot creation (ioctl(APFSIOC_SNAPSHOT_CREATE)), the SCF freezes the current omap root pointer and writes a Snapshot Metadata Tree node to the Snapshot Metadata Volume (a hidden APFS volume at /dev/diskXsY with role APFS_VOL_ROLE_SNAPSHOT_META).

The failure occurs when the Checkpoint Region (two 4 KiB blocks at fixed offsets 0x0 and 0x1000 on the container superblock) is written with an incremented apfs_last_xid that exceeds the snap_max_xid of a pinned snapshot. On Apple Silicon, the ANS2 (Apple NVMe Storage) controller processes write commands via the Submission Queue (SQ) and Completion Queue (CQ) doorbell registers mapped at 0x238000000 (M1) / 0x239000000 (M2). A power-loss event during the Flush Cache (0x10) admin command—specifically between the Checkpoint Write and the Snapshot Metadata Tree Update—leaves the superblock XID advanced while the snapshot’s snap_max_xid remains stale. The Secure Enclave (SEP) does not intervene here; this is purely a filesystem consistency violation in the APFS kext (com.apple.filesystems.apfs) during mount-time verification (apfs_mountfs → apfs_verify_snapshots). The I2C/SPI buses are irrelevant; the pathology is confined to the NVMe command pipeline and the APFS transaction log (jphys) replay logic.

3. Diagnostic Verification & Terminal Commands

Execute the following commands in exact sequence to confirm Error 69716 and isolate the offending snapshot.

# 1. Identify the APFS container and volume UUIDs
diskutil apfs list | grep -E '(Container|Volume|Snapshot)' | head -30

Output fields: Container UUID, Volume UUID, Role (Data/Preboot/Recovery/VM/Snapshot), Snapshot XID.

# 2. Run verbose verification targeting the specific volume (replace diskXsY)
sudo fsck_apfs -n -l -v /dev/diskXsY 2>&1 | tee /tmp/fsck_69716.log

Key log lines to capture:

apfs_verify_snapshots: checking snapshot 0x1a2b3c4d (com.apple.TimeMachine.2024-01-15-120000)
apfs_verify_snapshots: snap_min_xid=0x1a2b3000, snap_max_xid=0x1a2b3c4d
apfs_verify_snapshots: fs_current_xid=0x1a2b3c50, OVERLAP DETECTED (delta=0x3)
apfs_verify_volume: snapshot verification failed (err=69716)
# 3. Dump snapshot metadata tree for the overlapping snapshot
sudo apfs_snapshot_dump -v /dev/diskXsY -s 0x1a2b3c4d 2>&1 | grep -E '(snap_xid|snap_min_xid|snap_max_xid|extent_count)'
# 4. Stream live APFS kernel trace for transaction allocation
log stream --predicate 'subsystem == "com.apple.filesystems.apfs" and category == "transaction"' --info --style syslog

Filter for apfs_allocate_xid returning XIDs within a pinned snapshot’s range.

# 5. Verify checkpoint region integrity (requires SIP disabled or Recovery OS)
sudo nvme admin-passthru /dev/disk0 --opcode=0x09 --data-len=8192 --cdw10=0 --cdw11=0 --cdw12=0 --cdw13=0 --cdw14=0 --cdw15=0 | xxd | head -80

Inspect bytes 0x100-0x107 for apfs_last_xid (little-endian uint64). Compare against snapshot snap_max_xid from step 3.

4. Step-by-Step Resolution Protocols

Phase 1: Rapid Software & Cache Reset (Zero Data Loss)

  1. Boot to macOS Recovery (⌘R on Intel, Power button hold on Apple Silicon).
  2. Open Terminal from Utilities menu.
  3. Execute: diskutil apfs deleteSnapshot diskXsY -uuid <SNAPSHOT_UUID> for only the overlapping snapshot identified in Section 3.
  4. Run: diskutil verifyVolume diskXsY. If clean, reboot to macOS.
  5. In macOS, run: sudo tmutil thinlocalsnapshots / 999999999999 4 to purge orphaned snapshot references.

Success Criteria: fsck_apfs -n returns ** The volume appears to be OK. No data loss; only the corrupted snapshot is removed.

Phase 2: Terminal / Subsystem Pipeline Flush (Command-line Remediation)

  1. In macOS (not Recovery), disable Time Machine: sudo tmutil disable.
  2. Unmount all non-root APFS volumes in the container: diskutil unmountDisk force diskX (fails for root; proceed).
  3. Run the APFS repair binary with transaction log replay forced:
    sudo /usr/libexec/fsck_apfs -y -R /dev/diskXsY
  4. If repair reports Checkpoint region rewritten, immediately run:
    sudo /usr/libexec/fsck_apfs -n /dev/diskXsY
  5. Re-enable Time Machine: sudo tmutil enable.
  6. Trigger a new local snapshot to validate CoW isolation: tmutil localsnapshot.

Note: The -R flag forces apfs_replay_journal to rebuild the transaction ID allocator bitmap (apfs_xid_bitmap_t) from the journal physical (jphys) extents, resetting apfs_last_xid to max(snap_max_xid) + 1 across all valid snapshots.

Phase 3: Hardware / DFU Deep Restoration (Complete Firmware Reflashing)

  1. Connect Mac to a second Mac running Apple Configurator 2 (v2.16+) via USB-C (DFU mode: Power + Touch ID hold 10s, release Power, hold Touch ID 5s).
  2. In Configurator, select device → Actions → Advanced → Revive Device (not Restore). This reflashes the iBoot, Secure Enclave Firmware (SEPFW), and ANS2 Controller Firmware without erasing user partition.
  3. If Revive fails, perform full Restore (erases all volumes). Select Latest macOS IPSW matching the Mac’s Board ID (e.g., Mac14,6 for M2 Pro).
  4. Post-restore, boot to Recovery and run: diskutil apfs createContainer disk0 Macintosh_HD to lay down a fresh APFS container with pristine checkpoint regions.
  5. Restore user data from Time Machine backup (not Migration Assistant) to ensure clean snapshot hierarchy.

Indication for Phase 3: Recurrence of Error 69716 after Phase 2 on two consecutive clean installs indicates ANS2 controller NAND mapping table corruption requiring firmware re-initialization.

5. Technical Specifications & Parameter Matrix

Parameter Nominal Value Failure Threshold Remediation Target
APFS Transaction ID (XID) Width 64-bit (uint64_t) Wrap at 0xFFFFFFFFFFFFFFFF (theoretical) Reset allocator bitmap via fsck_apfs -R
Checkpoint Region Write Interval Every 30 seconds or 4 MB journal Power loss during write (window < 2 ms) ANS2 Flush Cache (0x10) completion timeout: 500 ms
Snapshot Metadata Tree Node Size 4 KiB (matches NAND page) CRC32 mismatch on read (ECC uncorrectable) Re-write via apfs_snapshot_create ioctl
NVMe Submission Queue Depth (ANS2) 1024 entries (M1/M2/M3) Queue full > 10 ms (indicates FTL stall) Controller reset via PCIe Function Level Reset (FLR)
APFS Journal (jphys) Max Extent Count 256 extents per transaction Extent overlap detected by apfs_verify_extents Journal replay truncation at last valid checkpoint
Time Machine Local Snapshot Retention 24 hours or 20% free space Snapshot pinned > 72 hours (blocks XID reuse) tmutil thinlocalsnapshots aggressive purge
Secure Enclave Firmware Version (SEPFW) Per IPSW manifest (e.g., 10.2.1) Version mismatch > 1 rev from bridgeOS DFU Revive updates SEPFW + ANS2 FW atomically
APFS Superblock Checksum Algorithm Fletcher-64 (apfs_fletcher64) Checksum mismatch on mount (panic: “apfs_superblock_checksum”) Checkpoint region rewrite from alternate copy (offset 0x1000)

6. Frequently Asked Questions

Q1: Can Error 69716 occur on a volume with no Time Machine snapshots?
A: Yes. Any APFS snapshot—including those created by diskutil apfs snapshot, tmutil localsnapshot, or third-party backup tools (Carbon Copy Cloner, SuperDuper!)—pins a transaction range. The error is triggered by any snapshot whose snap_max_xid is exceeded by the filesystem’s current apfs_last_xid. Verify with diskutil apfs listSnapshots diskXsY; hidden snapshots (e.g., com.apple.os.update-) are common culprits.
Q2: Does FileVault encryption affect the probability or resolution of Error 69716?
A: FileVault (APFS Volume Encryption, VE) adds an AES-XTS-256 layer but does not alter transaction ID allocation or snapshot metadata structures. The encryption keys are wrapped by the Secure Enclave; the APFS kext operates on decrypted logical blocks. Resolution steps are identical. However, Phase 3 DFU Restore must use an IPSW with matching ApECID to preserve the FileVault keybag; otherwise, the volume becomes cryptographically unrecoverable.
Q3: Why does fsck_apfs -y sometimes report “Volume repaired” but Error 69716 recurs on next verify?
A: fsck_apfs -y without -R only repairs filesystem structures (B-tree nodes, extent refcounts). It does not rebuild the transaction ID allocator bitmap or rewrite the checkpoint region’s apfs_last_xid. The overlapping snapshot remains pinned with a stale snap_max_xid. You must use fsck_apfs -R (replay journal) or delete the offending snapshot to reset the XID ceiling.
Q4: Is there a risk of silent data corruption if Error 69716 is ignored?
Still stuck on Error 69716?

Share your exact OS build and Finder/Console snippet in the OS Updates & Error Codes forum room.

Get Peer Triage →