How to Fix Disk Not Ejected Properly Notifications After Sleep on Mac mini M4 Pro: Senior Engineer macOS Guide
⚡ Quick 60-Second Verdict: What This Issue Means
Your Mac mini M4 Pro is aggressively cutting power to USB/Thunderbolt controllers during sleep to save energy, but the storage daemon (diskarbitrationd) and IOKit power assertions aren’t coordinating the handoff cleanly—so drives vanish before macOS can unmount them. The fix is a targeted sequence: disable “Put hard disks to sleep” for external drives, tune pmset hibernation mode to keep the USB rail alive, and ensure your drive enclosures have current firmware—all doable in under 10 minutes with zero data risk.
- Never yank a drive cable while the Mac mini’s status light is pulsing (sleep)—the controller may still be flushing write caches; wait for the light to go solid or off.
- Do not disable System Integrity Protection (SIP) to hack IOKit kexts; Apple’s signed power-management drivers are the only supported path on Apple Silicon.
- Avoid third-party “sleep blocker” apps that hammer
caffeinate—they prevent deep sleep, cook the SoC, and void thermal throttling safeguards on M4 Pro. - Do not force-format a drive to APFS “Case-sensitive” or “Encrypted” mid-troubleshoot—encryption key rotation during sleep/wake is a known trigger for ejection failures.
1. Immediate Safe Actions (Non-Destructive User Triage)
Three straightforward, non-destructive initial triage steps tailored specifically to Disk Not Ejected Properly notifications on Mac mini M4 Pro:
Disable “Put Hard Disks to Sleep” for External Volumes
macOS Sonoma & Sequoia apply the “Put hard disks to sleep when possible” checkbox globally, but the M4 Pro’s USB4/TB4 controllers interpret this as permission to power-gate the entire downstream port hierarchy. Open System Settings → Energy Saver (or Battery on portables, but Mac mini shows Energy Saver). Uncheck “Put hard disks to sleep when possible”. Immediately test: put the Mac to sleep ( → Sleep), wake after 30 seconds, and verify no “Disk Not Ejected Properly” banner appears. This single toggle resolves ~60 % of cases on M4 Pro because it keeps the USB PHY in U0/U1 active state instead of dropping to U3 suspend.
Set Hibernation Mode to 0 (Sleep Only, No Safe Sleep)
The M4 Pro defaults to hibernatemode 3 (safe sleep: RAM contents written to SSD before deep sleep). On Apple Silicon, the write-to-SSD path competes with the USB4 retimer for memory bandwidth, causing the storage daemon to miss the unmount deadline. Open Terminal and run:
sudo pmset -a hibernatemode 0
sudo pmset -a standby 0
sudo pmset -a autopoweroff 0
Enter your admin password (no echo). Verify with pmset -g custom. This keeps the Mac in pure RAM sleep (mode 0)—the USB controllers stay enumerated, and drives never see a bus reset. Re-test sleep/wake cycle. Note: Battery drain is irrelevant on Mac mini; this is safe and recommended for desktop Apple Silicon.
Update Drive Enclosure & Dock Firmware via Manufacturer Utility
Most “Disk Not Ejected” alerts on M4 Pro trace to JMicron (JMS583), ASMedia (ASM2464PD), or Realtek (RTL9210) bridge controllers that mishandle USB4/Thunderbolt 4 link training after exit from U3. Identify your enclosure’s bridge chip: System Report → USB → [Your Device] → Device Speed / Chipset. Visit the vendor site (OWC, CalDigit, Sabrent, UGREEN, etc.) and run their macOS firmware updater—not a Windows .exe via Parallels. Power-cycle the enclosure (unplug AC/DC brick for 15 s) after flashing. This aligns the bridge’s LTSSM (Link Training and Status State Machine) with Apple’s updated USB4 host router firmware in macOS 14.5+/15.0+.

2. Software False Alarm Recovery & Reset Protocol
Mac mini M4 Pro Hardware Reset Sequence (SMC/NVRAM Equivalent)
Apple Silicon has no user-accessible SMC or NVRAM reset, but the Power Cycle + Secure Enclave Re-key sequence clears volatile power-management registers in the PMGR (Power Manager) and forces the USB4 retimers to re-enumerate on next boot. Perform exactly:
- Shut down via → Shut Down (wait for status LED off).
- Unplug AC power cord from Mac mini (not just the strip). Wait 30 full seconds—this drains the PMGR’s 3.3 V always-on rail.
- Plug AC back in. Immediately press and hold the power button for 10 seconds until the status LED flashes amber rapidly (DFU/Revive indicator), then release.
- Press power button once normally to boot.
This sequence forces the Secure Enclave to regenerate ephemeral keys for the USB4/Thunderbolt security policy and resets the PMGR’s “sleep assertion” bitmap. Run Steps 01–03 again after this reset if the issue persisted.
3. Advanced Diagnostics & Component Triage
Hardware Telemetry & Sensor Verification
Open Console.app → select your Mac mini in the sidebar → search subsystem:com.apple.iokit and category:power. Filter for the last sleep/wake cycle (timestamp matches lid/ menu sleep). Look for these exact log signatures:
IOPMrootDomain: systemWillSleepfollowed byIOUSBHostInterface::setPowerState(0)beforediskarbitrationd: disk_unmount→ Race condition confirmed.AppleUSBHostPort::setLinkState(U3)withkIOUSBPortStatusChangeon wake → Bridge controller failed LFPS handshake.kernel: (AppleUSBHostMergeProperties) USB device not responding to SetAddress→ Enumeration collapse; firmware update required (Step 03).
Simultaneously, run log show --predicate 'subsystem == "com.apple.iokit"' --style syslog --last 1h > ~/Desktop/usb_sleep.log in Terminal. Attach this log if you open a MappleCare Genius Bar case—it lets engineers correlate PMGR assertions with USB4 retimer register dumps.

4. Diagnostic & Operating Parameter Matrix
| Diagnostic Indicator / Check | Expected Normal State | Fault Alert Threshold | Verified Resolution Target |
|---|---|---|---|
| Energy Saver: “Put hard disks to sleep” | Unchecked (external drives) | Checked → drives spin down in < 2 min | Unchecked + sleep/wake test passes 5× |
| pmset hibernatemode | 0 (RAM sleep only) | 3 (safe sleep) or 25 (standby) | 0 confirmed via pmset -g |
| USB4 Retimer Firmware (JMicron/ASMedia/Realtek) | Latest vendor release ≥ 2024-Q3 | Pre-2024 or “Unknown” in System Report | Flashed & power-cycled; no U3 errors in Console |
| Console: IOPMrootDomain sleep assertion order | disk_unmount before setPowerState(0) |
Reverse order or missing unmount | Correct order logged for 3 consecutive cycles |
| Drive Format / Partition Scheme | APFS on GUID, non-encrypted or FileVault only | APFS Case-sensitive, ExFAT, or 3rd-party encryption | Reformat to standard APFS + retest |
| Thunderbolt/USB Cable Certification | Intel/USB-IF certified 40 Gbps (TB4) or 20 Gbps (USB 3.2 Gen 2×2) | Passive > 0.8 m, uncertified, or “charging only” | Swap to 0.8 m TB4-cert cable; errors cease |
5. Frequently Asked Questions (FAQ)
Why does this only happen after sleep, not a cold boot?
During cold boot, the M4 Pro’s PMGR brings up the USB4 retimers in a deterministic sequence: power rail → reference clock → LTSSM training → enumeration → diskarbitrationd mount. Sleep/wake skips the cold-boot sequencer and relies on runtime power management assertions to keep the link alive. If the “disk sleep” assertion fires before the “unmount” assertion, the retimer drops to U3 (suspend) while the file system still has open handles—hence the ejection notice on wake. The fixes above re-order those assertions.
Can I just use a powered hub to solve this?
A Thunderbolt 4 / USB4 certified powered hub (CalDigit Element Hub, OWC Thunderbolt Hub, Belkin Dock Pro) often helps because it presents a single, stable upstream link to the Mac and manages downstream port power independently. However, if the hub’s own bridge firmware is old, it merely moves the problem downstream. Update the hub firmware first (Step 03), then connect drives to the hub. Avoid cheap USB-A hubs—they lack LTSSM management and worsen the race.
Will disabling FileVault on the external drive fix it?
Only if the drive uses third-party encryption (VeraCrypt, BitLocker via macFUSE, etc.). Native APFS FileVault is handled by the Secure Enclave and coordinates cleanly with sleep assertions. Third-party filter drivers often block the unmount callback during the 500 ms sleep window. If you must use third-party encryption, keep the drive mounted but add a caffeinate -d -i -m -s -t 3600 wrapper script triggered by a LaunchAgent on sleep (via SleepServices), but this is a last resort—reformatting to native APFS encryption is cleaner.
Does this affect the internal SSD or only external drives?
Only external drives. The M4 Pro’s internal NAND is managed by the Apple Storage Controller (ASC) over a dedicated PCIe lane with its own power domain (PMGR rail VDD_NAND). It never enters U3 suspend; it uses Apple’s proprietary low-power states (L1.2 / L0s) that are fully synchronized with the sleep sequencer. The “Disk Not Ejected Properly” banner will never reference the internal Macintosh HD volume—only USB/Thunderbolt volumes.
Share your OS version, device model, and exact error code in our independent peer Q&A rooms.
Comments