-
All replies
-
Helpful answers
-
Jan 23, 2013 10:14 AM in response to KaelCormacby Eustace Mendis,Next time that happens try relaunching the Finder: command + option + esc, select Finder, then click on Relaunch.
-
-
Jan 23, 2013 11:21 AM in response to KaelCormacby Eustace Mendis,Did you try Repair Disk?
Applications / Utilities / Disk Utility. Select the external drive and request "Repair Disk".
-
Jan 23, 2013 11:28 AM in response to KaelCormacby KaelCormac,When I tell finder To relaunch it takes away my icons and only shows a blank desktop. I can get to the "dock" and open programs from there but finder is still not responding. And I still have the shutdown issue.
-
Jan 23, 2013 11:32 AM in response to Eustace Mendisby KaelCormac,I will try this next, but I'm pulling some files off in case it goes screwy. I'm finding that as soon as I transfer a file, finder stops responding (I can only assume because of the hard drive). Then I have to shutdown the computer (with the power button) and unplug the hard drive in order for a working boot up.
-
Jan 23, 2013 11:36 AM in response to KaelCormacby Eustace Mendis,Do this only if Repair Disk does not work.
Go to Users / yourself / Library / Preferences.
Find the file called com.Apple.Finder.plist, and put it in the trash. But do not empty the trash, just in case.
Now restart. That file will be recreated. If the problem is a corrupted preferences file, this should solve it.
-
Nov 25, 2015 8:36 AM in response to Eustace Mendisby hgmod0000,This is an old question, but the reason you are getting the error message is because your disk is actually in use. Try opening Console.app with your disk attached, then click your eject button. You should see the request to unmount several times in your console log, then you will see it fail with an explanation that it was in use by <foo> process. You can find out more about that that process by running `sudo lsof | grep -i <volume_name>`. Most likely the service using your disk is mds-related(spotlight indexing, or other meta-data tasks).
Once you know which service is preventing your drive from ejecting, you will have a better idea of what is "wrong"(if anything). Finder itself is behaving as it should though, and letting you know that it failed to eject the drive because another process using it was not finished.