What to Do When macOS Won’t Let You Unmount a Volume
When all else fails, the next step is to identify what’s using files on that volume or disk, so you can decide whether to force quit that process in Activity Monitor. Don’t do that blindly, as you could end up killing processes that your Mac does need to run.
[…]
If you’d rather use an app, then my personal favourite is Sloth from here. Although it’s not notarized, it does everything that I’d want in terms of matching
lsoforfuser’s features. Most importantly, if you click its padlock at the lower right and authenticate, it will show all processes running as root.
I like Sloth, but it’s annoying to have to authenticate each time I use it. There’s a preference to have it prompt at launch so that at least you don’t have to click the little padlock icon each time (or forget to click it and get incorrect results).
In practice, I almost never had problems with volumes that wouldn’t eject before Sequoia, and now it happens multiple times per day. The culprits are always mds (Spotlight) and revisionsd (file versioning) so there seems to be nothing to do except Force Eject.
See also: TidBITS-Talk.
Previously:
3 Comments RSS · Twitter · Mastodon
One drive of mine refuses to eject every single time. I've tried every method to figure out which program has which file open and there are never any files open. Never happened before Sequoia. I suspect it's a bug with the Finder.
I often check if it's QuickLook: lsof /Volumes/My_Drive
Then: killall -KILL QuickLookUIService
Always works.
