You click the eject button in Finder’s sidebar and nothing happens. Or worse, Finder itself has gone unresponsive and the whole sidebar is grayed out. Your drive is stuck, and the one tool you normally use to eject it isn’t cooperating.

This happens more often than Apple would probably like to admit. Finder is a complex application that handles file management, desktop rendering, and window management all at once. When it chokes on something, drive ejection is one of the first casualties.

Why Finder stops responding to eject requests

Finder can stall for several reasons, and most of them have nothing to do with your external drive.

A network volume that went offline can freeze Finder while it tries to reconnect. A folder with thousands of files that Finder is trying to generate previews for can lock things up. Even a corrupted .DS_Store file in the wrong place can cause Finder to spin.

When Finder stalls, it stops processing all user actions, including eject requests. You click the eject icon and nothing happens because Finder never receives the instruction. It’s stuck in a loop somewhere else entirely.

Sometimes Finder appears responsive but still won’t eject your drive. You can click around, open folders, move files. But the eject button does nothing, or you get a brief spinning cursor before it gives up silently. This usually means Finder is processing the eject request but hitting a wall because something is holding the drive open.

Eject from Disk Utility

Disk Utility operates independently from Finder. Open it from Applications > Utilities, or search for it with Spotlight (Command-Space).

Find your external drive in the left sidebar. Select the volume (not the physical disk entry above it) and click the Unmount button in the toolbar. If that works, your drive will disappear from the desktop and you can safely disconnect it.

If you need to unmount all volumes on a multi-partition drive, select the physical disk entry (the top-level item) and click Unmount All.

Disk Utility communicates with the disk management system directly, bypassing Finder’s layer entirely. If Finder is the problem, Disk Utility will often succeed where Finder failed.

Eject from Terminal

Terminal gives you the most direct control. Open it from Applications > Utilities and use the diskutil command:

diskutil unmount /Volumes/YourDriveName

If a regular unmount fails, you can try forcing it:

diskutil unmountDisk force /dev/disk4

Replace disk4 with the correct disk identifier. To find it, run:

diskutil list

Look for your drive’s name in the output. The identifier will be something like disk4 or disk5.

Terminal commands bypass Finder completely. They talk directly to the disk arbitration daemon, which is the system-level service that actually handles mounting and unmounting.

Relaunch Finder

If Finder is the actual problem, relaunching it can clear the jam.

Hold Option, then right-click the Finder icon in the Dock. You’ll see “Relaunch” at the bottom of the menu. Click it.

Alternatively, open Terminal and run:

killall Finder

Finder will restart automatically. Once it’s back, try ejecting your drive again from the sidebar. A fresh Finder session often resolves whatever was blocking the eject request.

Be aware that relaunching Finder closes all Finder windows. If you had specific window arrangements or tabs open, they’ll be gone.

When even these methods fail

If Disk Utility, Terminal, and a Finder relaunch all fail to eject your drive, the problem isn’t Finder at all. Something else on the system is holding files open on that drive.

At this point you need to find out what’s actually using the drive:

lsof /Volumes/YourDriveName

This lists every process with an open file handle on your drive. The output can be dense, but look at the COMMAND column for process names you recognize.

The manual approach works, but it takes time and some familiarity with system processes to interpret the results. Ejecta does this automatically. It monitors your external drives and shows you exactly which processes are blocking ejection, with a button to quit each one. No Terminal, no guesswork, no waiting for Finder to sort itself out.

When your tools fail you, the answer isn’t to force eject or yank the cable. It’s to find out what’s actually going on and deal with it directly.