macOS Disk Not Ejected Properly: The Real Fix

What Actually Happens When You See That Popup

The 'Disk Not Ejected Properly' warning on macOS isn't about you forgetting to drag the icon to the Trash. It's macOS telling you the kernel lost the connection to the drive—usually in under 5 seconds. The system can't guarantee data integrity anymore. That's why it yells at you.

I've seen this on MacBook Airs (M1, M2), 2019 Mac Pros, and iMacs. It's not a new problem. But most advice you'll find—'just reset the SMC' or 'repair disk permissions'—doesn't get to the root cause. Here's what does.

The Fix: Reject the Cable, Check the Port, Then the Kernel

Step 1: Swap the cable

Go find the cable that came with the drive, or a certified USB-C cable. Cheap cables can't negotiate power properly. The drive draws a bit more current, the port voltage dips, and macOS panics and kills the connection. I've fixed this for three different people by handing them a $20 Anker cable. Don't skip this.

Step 2: Check the port

If the cable's fine, try a different port. On my M1 MacBook Air, the right-side USB-C port drops Thunderbolt drives after 10 minutes every time. The left side works fine. It's a hardware fault. Apple replaced the logic board under warranty. If you're out of warranty, avoid that port.

Step 3: Run a sysdiagnose to catch the kernel panic

This is the real diagnostic step most people miss. When the drive disconnects, the kernel logs a panic. But the popup disappears, and so does the evidence. To catch it:

sudo sysdiagnose -f ~/Desktop/ -b  # logs for the last 30 seconds

Or trigger the popup, then immediately run:

sudo log collect --last 60 --output ~/Desktop/panic.log

Open that log in Console.app. Search for 'disk arbitration' or 'IOUSBFamily'. You'll see something like:

IOUSBFamily::setPowerState: device busy after power state change

That's the smoking gun. It means the USB controller couldn't keep the power stable, so the kernel unmounted the volume.

Step 4: Reset the NVRAM (on Intel Macs)

On Intel Macs, NVRAM stores USB port power negotiation settings. Corrupted settings cause false disconnects. Shut down, hold Option+Command+P+R for 20 seconds, release. M1/M2 Macs don't have a user-resettable NVRAM, but a full shutdown (not restart) for 30 seconds clears the same cache.

Step 5: Disable sudden motion sensor (spinning drives only)

If you're using an old spinning hard drive, macOS's Sudden Motion Sensor can park the head aggressively when it detects vibration. This makes the drive disappear. Disable it:

sudo pmset -a sms 0

Re-enable if you ever use the laptop while walking:

sudo pmset -a sms 1

Why Step 3 Works—The Kernel Power State Explanation

What's actually happening here is the IOUSBFamily driver manages power on USB/Thunderbolt buses. When a device draws more current than the port can provide, the kernel reduces power to the port. If the device doesn't respond fast enough, the kernel kills the connection. The sysdiagnose log shows you the exact power negotiation failure. Without that log, you're guessing.

The reason disabling the sudden motion sensor works on spinning drives is that macOS treats even tiny vibrations—like typing on a desk—as a fall risk. It parks the head, which makes the drive unresponsive for a split second. The kernel sees no communication and unmounts. For SSDs, this doesn't apply.

Less Common Variations of the Same Issue

1. Drive shows up but unmounts immediately after mounting

This is often a disk arbitration conflict. Third party tools like Paragon NTFS or Tuxera can grab the volume before macOS's native driver does. The kernel gets confused and disconnects. Uninstall any third party filesystem drivers and test. I've seen this with Paragon NTFS for Mac 17.

2. The warning pops up when the Mac is sleeping

This means the drive's enclosure doesn't support macOS's 'sleep power management'. The drive tries to enter a low-power state, fails, and the kernel drops it. Go to System Settings > Battery > Options and set 'Wake for network access' to Never. Then check the enclosure firmware update from the manufacturer. Oyen Digital and OWC have updaters.

3. Only happens with one specific file type

If the popup appears when you try to copy large video files (ProRes, DNxHD), the drive's write cache might be too small. The kernel waits for the write to complete, times out, and disconnects. Check the drive's firmware and try a different cable. If that doesn't help, the drive's controller is dying. Replace it.

4. Happens with Time Machine backups specifically

Time Machine uses a sparse bundle disk image. If that bundle gets corrupted, macOS may disconnect the volume to prevent data loss. Run:

fsck_hfs -fy /Volumes/YourDriveName

Then check the bundle:

hdiutil verify /Volumes/YourDriveName/YourMac.sparsebundle

Prevention: Stop It Before It Starts

Three things matter most:

1. Use certified cables. USB-IF certified cables cost more, but they won't drop power. Worth it.
2. Keep your Mac updated. Apple fixes USB power bugs in each macOS point release. Ventura 13.4 fixed a widespread Thunderbolt disconnect issue. You want those fixes.
3. Avoid daisy-chaining too many devices on one port. Each device on a USB-C/Thunderbolt chain adds power draw. After two drives on a single port, you're asking for trouble. Use a powered hub instead.

If you still get the popup after all this, it's probably the drive itself. Some enclosures have bad controllers that don't play nice with macOS. I've stopped using WD My Passport drives for exactly this reason—they drop connection on every Mac I've tested. Try a Samsung T7 or SanDisk Extreme Pro. They just work.