'Disk Not Ejected Properly' on Mac? Here's What to Do Next Time

You walk back to your desk after lunch, wiggle the mouse, and there’s a notification waiting: “Disk Not Ejected Properly. Eject [drive] before disconnecting or turning it off.” Except you didn’t disconnect anything. The drive’s cable is still plugged in. Now you’re wondering whether the files you copied this morning are intact.

This warning is macOS noticing the drive vanished from its bus without going through the orderly shutdown sequence. Sometimes that’s harmless, sometimes it’s a sign of a real problem.

What the warning actually means

macOS expects every drive disconnect to follow this sequence:

1. The user clicks Eject (or runs diskutil eject).
2. The OS flushes any unwritten data from RAM caches to the disk.
3. The OS unmounts the volume cleanly.
4. The OS signals the drive’s firmware that it’s safe to power down.

If the connection drops between steps 1 and 4 — even if you didn’t touch anything — macOS shows the warning. The exact text:

“Disk Not Ejected Properly. Eject [Volume Name] before disconnecting or turning it off.”

It’s the same warning whether you actually yanked the cable, or the drive’s connection blipped for half a second.

What probably caused it (when you didn’t touch the drive)

If you definitely didn’t unplug anything, suspect one of these:

1. Loose USB-C or USB-A cable. The most common cause by far. Cables work loose from sleeve case ports, dock vibrations, or just gravity on a desk.
2. The Mac slept and the drive’s bus didn’t survive. External drives often disconnect during sleep. macOS shows the warning when the Mac wakes.
3. A USB-C hub overheated and reset. Cheap hubs do this under load. The drive briefly disappears.
4. The drive’s enclosure went into power-save mode. Many bus-powered SSDs spin down after 10 minutes of inactivity, and re-mounting can register as a fresh connection.
5. A failing cable. Especially USB-C cables — the connector pins wear out.
6. Power blip on the drive. Bus-powered drives near their power budget brown out under load.
7. Drive firmware issue. Some Samsung T5/T7 SSDs and Sandisk Extreme drives have well-known disconnection bugs that need firmware updates.

Diagnose AND clean in one appSweep finds the buildup behind the error and clears it. Try Sweep free →

Is your data safe?

Probably yes — but verify.

1. Reconnect the drive. It should mount automatically.
2. Run Disk Utility First Aid. Select the volume, click First Aid. This checks for filesystem inconsistencies the unclean disconnect might have caused.
3. Spot-check important files. Open a recent document, play a recent video, scrub through photos.

If First Aid passes and your recent files open, you’re fine. The journaled filesystems macOS uses (APFS, HFS+ Journaled) are designed to survive sudden disconnects without corruption — the journal replays on reconnect.

The risk window is narrow but real: any file being written at the moment of disconnect is potentially truncated or corrupt. If you were mid-Lightroom export or rendering a Final Cut project to that drive, those specific files are suspect.

Find the root cause

A single warning is noise. Repeated warnings need investigation.

Check Console.app for the disconnect

Open Console (Applications → Utilities → Console.app). Click your Mac in the sidebar. Search for the volume name or “USBMSC”. Right around the warning’s timestamp you’ll see entries like:

• “USB device disconnected”
• “DiskArbitration: device removed”
• “ATA device terminated”

The seconds-before context tells you whether the disconnect coincided with a sleep event, a USB enumeration, or a power state change.

Test with a different cable

The single highest-yield experiment. USB-C cables especially are not all equal — Thunderbolt 3 cables, USB 3.2 cables, and USB 2 cables all fit the same port and behave differently. Try a known-good cable from a different drive.

Test on a different port

Bypass the dock or hub. Plug directly into the Mac. If disconnects stop, your hub or dock is the culprit.

Check for firmware updates

Samsung, SanDisk, Crucial, and OWC all ship Mac firmware updaters. Check the manufacturer’s support site by your drive’s exact model. Several drive models have had firmware fixes specifically for disconnect bugs.

Stop the warnings during sleep

If the warnings only appear after the Mac sleeps, it’s because external drives drop during sleep on most Macs. Two ways to address it:

1. Eject before sleeping. Right-click the drive in Finder → Eject before closing the lid.
2. Prevent sleep while drives are mounted. System Settings → Lock Screen → set “Turn display off after” to a long interval, or use caffeinate -s in Terminal during long jobs.
3. Disable “Put hard disks to sleep when possible” — System Settings → Battery → Options. Helps for spinning drives.

The warnings are mostly cosmetic for sleep-induced disconnects, but they nag you and they do mean macOS couldn’t flush caches cleanly.

Skip the manual huntSweep clears the cruft that triggers most of these errors — caches, logs, leftover daemons. Download Sweep free →

Fix a drive that mounts read-only after a bad disconnect

Sometimes a forced disconnect leaves the volume mounted read-only as a protective measure.

1. Eject and reconnect.
2. Disk Utility → First Aid. Let it complete fully.
3. If First Aid fails to repair: diskutil verifyVolume /Volumes/<name> in Terminal. The detailed output tells you what’s wrong.
4. If verification reports unrecoverable errors and the drive is FAT/ExFAT formatted, plug it into a Windows machine and run chkdsk /f. macOS can’t repair FAT-family filesystems as thoroughly.
5. If repair fails entirely, copy what you can off the drive, then reformat (Disk Utility → Erase). You’ll lose anything that wouldn’t copy.

When the drive is the problem

A drive that disconnects repeatedly across cables, ports, and Macs is failing or has a firmware issue.

• SMART status check. Disk Utility → View → Show All Devices → click the physical drive (not the volume) → check S.M.A.R.T. status. “Failing” means replace it now.
• Read errors during First Aid. Multiple “could not read sector” messages means the drive is dying.
• Unusual heat. Bus-powered SSDs that get too hot to touch are throttling and at the end of their thermal headroom.

Spinning hard drives that click are mechanically failing. Stop using the drive immediately and copy data off via a single-pass Finder copy if it’ll mount, or with ddrescue if it won’t.

What about the Mac itself?

If multiple different drives all show the warning on the same Mac, suspect:

• A specific USB-C port. Test each port individually. Apple Silicon Macs occasionally have one port die from electrical damage.
• System Management Controller weirdness. On Intel Macs, an SMC reset (different procedure for each model — check Apple Support) sometimes resolves USB enumeration glitches.
• A failing logic board. Rare, but consistent USB problems across all ports point here. Apple Support is the right call.

Prevent it from happening again

• Always eject before pulling cables, sleeping the Mac, or unplugging your dock.
• Use cables that came with the drive or known-good replacements.
• Keep important work on at least two drives so a worst-case corruption isn’t catastrophic.
• For Time Machine drives that show this warning often, consider switching to a wired Time Capsule or a NAS — they’re not subject to the same disconnect issues.

The warning is mostly a nag, but it’s a useful nag. Take it as a prompt to verify your files and check your cables.