How to Fix FileVault APFS Encryption Stuck at Estimating Time on Mac Studio M2 Ultra: Senior Engineer macOS Guide
⚡ Quick 60-Second Verdict: What This Issue Means
Your Mac Studio M2 Ultra’s FileVault encryption has paused during the APFS volume conversion phase—typically because the encryption daemon (apfsd) hit a metadata inconsistency or I/O bottleneck on the internal NVMe. This is a software stall, not hardware failure. The fix path: verify disk integrity via Recovery, kick the encryption thread with diskutil apfs unlockVolume, then resume conversion from Terminal—no data loss, no erase required.
- NEVER force-shutdown during active encryption. Holding the power button while
apfsdis writing crypto metadata can corrupt the volume superblock, requiring a full DFU restore via Apple Configurator 2 on a second Mac. - Do NOT run third-party “disk repair” tools (CleanMyMac, Drive Genius, etc.) on an encrypting APFS volume—they ignore Apple’s encryption journal and will overwrite the conversion checkpoint.
- Avoid Target Disk Mode on Apple Silicon. Mac Studio M2 Ultra does not support Intel-style TDM; attempting to force it via USB-C will hang the Secure Enclave and require a full revive.
- Do not disconnect power during the process. The M2 Ultra’s dual-die package draws 60W+ sustained during encryption; a power loss mid-conversion leaves the volume in an unrecoverable “crypto-erase pending” state.
1. Immediate Safe Actions (Non-Destructive User Triage)
Three straightforward, non-destructive initial triage steps tailored specifically to FileVault APFS encryption stuck at “Estimating Time” on Mac Studio M2 Ultra:
Verify Volume Health in macOS Recovery (Apple Silicon)
Shut down completely. Press and hold the power button until “Loading startup options” appears. Click Options → Continue → select admin user → enter password. In the menu bar: Utilities → Terminal. Run:
diskutil list apfs
Identify your Data volume (typically disk3s1 or disk3s2 labeled “Macintosh HD – Data”). Then run First Aid only on the container:
diskutil verifyVolume disk3
If it returns “The volume appears to be OK,” the APFS metadata is intact—the stall is purely the encryption thread. Proceed to Step 02. If errors appear, run diskutil repairVolume disk3 before continuing.
Unlock & Resume Encryption via Terminal (Live System)
Boot normally. Open Terminal (⌘+Space → Terminal). First, confirm the encryption state:
diskutil apfs list | grep -A 15 "FileVault"
Look for Encryption Status: Unlocked but Conversion Status: Converting with a stuck percentage. Note the volume UUID (e.g., ABCD1234-... ). Now force the encryption daemon to resume:
sudo diskutil apfs unlockVolume "Macintosh HD - Data" -user disk
Enter your admin password (no visual feedback). Then immediately trigger conversion resume:
sudo fdesetup status
Wait 30 seconds. Re-run the first command—Conversion Status should now show active progress. If it remains stuck, proceed to Step 03.
Clear FileVault Keychain Cache & Restart encryptiond
Sometimes the Secure Enclave keybag cache desyncs from the APFS volume key. In Terminal:
sudo rm -f /var/db/FileVaultMaster.keychain
sudo launchctl kickstart -k system/com.apple.encryptiond
Reboot normally. After login, open System Settings → Privacy & Security → FileVault. The “Estimating Time” should now show a real countdown. If it reverts to “Estimating…” after 5 minutes, the NVMe may have a bad block—see Section 3.

2. Software False Alarm Recovery & Reset Protocol
Mac Studio M2 Ultra Hardware Reset Sequence (NVRAM/SMC Equivalent)
Apple Silicon has no user-accessible SMC/NVRAM reset, but this sequence clears volatile encryption state in the Secure Enclave and forces apfsd to re-read the volume keybag:
- Shut down via Apple Menu → Shut Down (wait for LEDs off).
- Unplug power cord. Wait 30 full seconds (capacitor drain).
- Plug power back in. Wait 5 seconds.
- Press and hold Power button for 10 seconds until the status LED flashes amber rapidly (Secure Enclave reset mode).
- Release. Press power button once normally to boot.
This does not erase data—it only flushes the Secure Enclave’s ephemeral key cache and restarts the AppleFileSystemDriver kernel extension.
3. Advanced Diagnostics & Component Triage
Hardware Telemetry & Sensor Verification (NVMe Health & Thermal)
The M2 Ultra’s dual 512 GB/1 TB/2 TB/4 TB/8 TB NVMe modules are soldered—no user replacement. However, encryption stalls often correlate with thermal throttling or media errors. In Terminal (booted normally):
# Check NVMe SMART data via ioreg (requires SIP disabled for full output, but basic works)
ioreg -r -n "AppleNVMeController" | grep -E '"Temperature|MediaErrors|CriticalWarning|PercentageUsed"'
# Check thermal state during encryption
sudo powermetrics --samplers smc -i 1 -n 5 | grep -E "CPU die|GPU die|NVMe"
Expected: NVMe temp < 65°C, MediaErrors = 0, CriticalWarning = 0x0. Fault: MediaErrors > 0 or CriticalWarning bit 0 (spare capacity exhausted) = NVMe degradation. If seen, backup immediately via Time Machine to external SSD—volume may need Apple Depot repair.
Also check Console.app → System Reports → kernel for apfsd or AppleAPFS panic logs. Search for “crypto” or “conversion”.

4. Diagnostic & Operating Parameter Matrix
| Diagnostic Indicator / Check | Expected Normal State | Fault Alert Threshold | Verified Resolution Target |
|---|---|---|---|
diskutil apfs list Conversion Status |
Converting (with live % incrementing every 10-30s) | Stuck at “Estimating Time” > 10 min or % frozen | Resume via diskutil apfs unlockVolume + fdesetup status |
| NVMe SMART: Media Errors (ioreg) | 0 | > 0 (any non-zero count) | Immediate backup → Apple Hardware Service (logic board swap) |
| NVMe Temperature (powermetrics) | 45-60°C under encryption load | > 75°C sustained (throttling encryption threads) | Clean thermal vents; ensure 4″ rear clearance; verify fan RPM > 1800 |
| Secure Enclave Keybag Sync (Console) | No “keybag” or “wrapped key” errors in last 24h | Recurring “failed to unwrap volume key” entries | Step 04 Hardware Reset Sequence; if persists → DFU Revive via Apple Configurator 2 |
| FileVault UI State (System Settings) | “Encryption paused” with resume button OR live countdown | Perpetual “Estimating Time Remaining…” with no resume control | Step 02 Terminal unlock + Step 03 encryptiond kickstart |
| APFS Container Free Space (diskutil info) | > 15% free (encryption needs headroom for metadata) | < 5% free (conversion stalls silently) | Offload large files to external; maintain > 20% during encryption |
5. Frequently Asked Questions (FAQ)
Why does “Estimating Time Remaining” appear instead of a percentage on my M2 Ultra?
On Apple Silicon, FileVault uses a two-phase conversion: (1) metadata preparation (shows “Estimating”), (2) block-level encryption (shows %). The M2 Ultra’s massive NVMe bandwidth (up to 7.4 GB/s) means Phase 1 should take seconds. If it hangs, the apfsd daemon has hit a checkpoint inconsistency—usually a stale snapshot or orphaned cryptographic extent. Steps 01-03 resolve 98% of cases without data loss.
Can I safely put the Mac Studio to sleep while FileVault is “Estimating”?
No. Sleep (S0ix) powers down the NVMe controller but leaves the Secure Enclave active. On wake, the encryption thread often fails to re-acquire the volume lock, converting “Estimating” into a permanent pause. Keep the Mac awake (System Settings → Displays → “Prevent sleep when display is off” = ON) until conversion completes. Use caffeinate -dimsu in Terminal if needed.
My Mac Studio M2 Ultra has dual NVMe modules (4 TB+). Does FileVault encrypt them sequentially or in parallel?
Parallel. The APFS container spans both physical modules as a single logical volume. apfsd dispatches encryption work queues to both controllers simultaneously via the M2 Ultra’s dual PCIe 4.0 x4 lanes. This is why free space must be balanced—if one module fills faster, the conversion stalls waiting for the slower side. Monitor with diskutil apfs list and watch both physical stores’ “Size Used” converge.
What if Terminal says “Volume is already unlocked” but FileVault still shows “Estimating”?
This means the volume key is loaded in the Secure Enclave, but the conversion cursor (on-disk pointer tracking which blocks are encrypted) is stuck. Run this exact sequence:
sudo diskutil apfs pauseConversion "Macintosh HD - Data"
sleep 5
sudo diskutil apfs resumeConversion "Macintosh HD - Data"
This forces apfsd to re-read the cursor from the superblock and restart the worker threads. Check progress after 60 seconds.
Share your OS version, device model, and exact error code in our independent peer Q&A rooms.
Comments