If this happens, we just need to close the file in question and try again eject the disk. If we have any file stored on the disk open in any app, macOS may prevent us from ejecting the disk so we don’t lose any of our data. It means that we are trying to eject the disk that is currently in use. Volume Elements on disk4s1 failed to unmount: dissented by PID 16314 (/System/Library/Frameworks/amework/Versions/A/Frameworks/amework/Versions/A/XPCServices/QuickLookUIService.xpc/Contents/MacOS/QuickLookUIService)
Umount(/Volumes/Diskname): Resource busy - try 'diskutil unmount'Īnd the same with the diskutil unmount command recommended in previous error message: This article is intended for advanced users (when the “QuickLookUI” process is not the cause) and/or for coder’s funĪfter several attempts, I tried to use the umount command in the Terminal app, and get the same error: It describes how to do almost the same thing using the Activity Monitor application, instead of using commands in the Terminal. The disk 'Elements' wasn't ejected because one or more programs may be using it.įor regular users, I recommend reading another article about this issue.
The volume can't be ejected because it's currently in use.
But to my surprise when pressing the ‘eject’ button Finder warns me with the following error messages: After working with an external hard drive (further simply - disk) I want to cleanly unmount it.
