Apple Event: May 7th at 7 am PT
I have started up my Macbook from a cloned external drive and can't unmount the internal "Macintosh HD" because it is in use. I have repaired permissions and started in safe mode but this doesn't help.
Thanks
MacBook, Mac OS X (10.7.4)
Run this in the Terminal app to determine which files are opened on the int HD precluding unmounting:
lsof /Volumes/"Macintosh HD"/
Run this in the Terminal app to determine which files are opened on the int HD precluding unmounting:
lsof /Volumes/"Macintosh HD"/
I got this though not sure what to do with it:
lapbuk:~ appla$ lsof /Volumes/"Macintosh HD"/
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Finder 171 appla 21r DIR 14,2 68 6518486 /Volumes/Macintosh HD/.Trashes/501
com.apple 183 appla txt REG 14,2 97728 6277267 /Volumes/Macintosh HD/Applications/BusyCal.app/Contents/PlugIns/BusyCalDockTile.docktileplugin/Con tents/MacOS/BusyCalDockTile
mdworker 212 appla 8r REG 14,2 6148 4622490 /Volumes/Macintosh HD/Users/appla/Library/Application Support/BusyCal/.DS_Store
In the Terminal, run this:
kill -9 171
That should kill the Finder process with PID 171. Then, run the lsof command again. I'm assuming you'll just see:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
com.apple 183 appla txt REG 14,2 97728 6277267 /Volumes/Macintosh HD/Applications/BusyCal.app/Contents/PlugIns/BusyCalDockTile.docktileplugin/Con tents/MacOS/BusyCalDockTile
mdworker 212 appla 8r REG 14,2 6148 4622490 /Volumes/Macintosh HD/Users/appla/Library/Application Support/BusyCal/.DS_Store
If so, then run these:
kill -9 183
kill -9 212
Then, the lsof one again. If nothing comes back, nothing's tying up the HD and you should be able to unmount the Macintosh HD.
Is there any downside to running these commands in terminal that I might regret?
Only that the process associated with those PIDs (process identifier) get stopped. If successful, there shouldn't be any running on the ext HD and you should be able to unmount it.
You don't think I'd post anything that you'd regret, do you?
No, just nervous 🙂
Started with the finder PID, ran the lsof then got 3 other PIDS 159, 188, 250.
I give up
Kill them all and see what happens.
Hello - I'm sure you've fixed this issue now but I thought I'd share with you how I fixed a similar scenario. I tried using baltwo's approach but the infringing application kept on re generating another PID...so I'd kill one, then run the lsof /Volumes/"Macintosh HD"/ in Terminal and another PID had replaced the original...
So - I saw that the infringing app was to do with Photo stream... Funny, as I was operating under an external boot disk and was trying to eject (unmount) the internal drive (Macintosh HD). I went into system preferences (on the boot drive) ----> iCloud -----> Unchecked Photo Streaming ----> and voila! I could unmount the Macintosh HD!
I guess the Boot drive was trying to get the Photo Stream and even though the System Preferences were changed in the Boot Drive, it allowed the HD to quit.
Cheers
can't unmount Macintosh HD
