Failed To Unmount Due To Error 16
Contents |
Please enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked michaelgilmore Level 1 (5 points) Apple Watch Q:
Hdiutil Detach Failed
I can't unmount any volume I have recently been having problems unmounting failed to unmount due to error 49168 any disk (iPod, Razr, even virtual volumes created by disk images), plugged into my system (10.3.9). I always get unmount error 16 = device or resource busy a message that the volume is in use, even when I know it isn't. The only way to unmount the volume is to restart the system or shut it down completely and
Unmount Error 16 = Device Or Resource Busy Cifs
restart.I've seen similar problems in the forum but none of the advice applies to my specific problem. Any suggestions?dual 800Mhz G4 Mac OS X (10.3.9) 1.2G RAM, 200G hard drivedual 800Mhz G4 Mac OS X (10.3.9) 1.2G RAM, 200G hard drive Posted on Dec 31, 2006 11:20 AM I have this question too Close Q: I can't unmount any volume All
Failed To Unmount Disk Mac
replies Helpful answers by roam, roam Jan 1, 2007 4:18 AM in response to michaelgilmore Level 6 (13,576 points) Jan 1, 2007 4:18 AM in response to michaelgilmore The problem why the OS thinks any mounted volume is in use is a mystery.To avoid restarting try using terminal to unmount the Volume using the hdiutil utilityhdiutil unmount theVolumenamecheckout the manpage for this utility withman hdiutulregardsroam Helpful (0) Reply options Link to this post by michaelgilmore, michaelgilmore Jan 2, 2007 12:01 PM in response to roam Level 1 (5 points) Apple Watch Jan 2, 2007 12:01 PM in response to roam roam,no luck. If I use unmount Michael Gilmores iPod, I get back the message hdiutil: unmount: Only a single file can be specified.If I use eject Michael Gilmores iPod, I get back the messagehdiutil: detach: only a single device name can be specified.If I use hdiutil eject MichaelGilmoresiPod, I get back the message hdiutil: eject failed - No such file or directoryIf I use detach detach Michael Gilmores iPod I get back the message hdiutil: detach: only a single device name can be specified.If I use hdiutil
(USB) hard drive. Today, in the course of doing other things, I noticed that, although I couldn't see it on the desktop, the image failed to unmount partitions cdrom was mounted. I can't see it anywhere except from the CLI when
Fusermount Failed To Unmount
doing an `ls`. I've tried to unmount it, to detach it, to force both operations and to throw sudo fusermount failed to unmount invalid argument at them, but I can't get this volume to go away. The external drive that it actually resides on isn't even plugged in. If I _do_ plug it in and https://discussions.apple.com/thread/794460?start=0&tstart=0 mount the content, it mounts as 'mbp17.mwf 1'. Clearly the system thinks something is mounted, but I can't find a way to unmount it. I've rebooted several times and I've also removed some ACL bits that were set, but nothing seems to work. Is there anything else I can try? rob@mbp17 [Volumes] $ ls total 8 lrwxr-xr-x 1 root admin http://www.shirt-pocket.com/forums/archive/index.php/t-6068.html 1B Jan 26 18:43 Macintosh HD -> / drwxr-xr-x 11 root admin 374B Jan 25 22:48 mbp17.mwf rob@mbp17 [Volumes] $ sudo hdiutil unmount -force mbp17.mwf/ Password: hdiutil: unmount: "mbp17.mwf/" failed to unmount due to error 49153. hdiutil: unmount failed - Resource busy rob@mbp17 [Volumes] $ sudo hdiutil detach -force mbp17.mwf/ hdiutil: detach failed - No such file or directory Any thoughts, hints or suggestions would be much appreciated. dnanian01-26-2010, 09:05 PMSounds to me like it's not a mount point. What happens if you restart your Macc and check /Volumes? robwilkerson01-27-2010, 07:13 AMSounds to me like it's not a mount point. What happens if you restart your Macc and check /Volumes? I've restarted about 12 times (each after trying something new) and the volume (or directory) is always there. I was a little afraid to simply delete it, but perhaps that's worth a try. dnanian01-27-2010, 08:16 AMIf it looks like a folder in Finder (use Go To Folder to get there), delete it. It's a failed mount point converted to a folder. robwilkerson01-28-2010, 06:48 PMIf it looks like a folder in
Payment options Amsys Training FAQs Support Project management Integration Enterprise Development Recruitment About Amsys Events Revise IT White Papers Podcasts Blog Contact OS X & iOS Enterprise Tips, News & Resources Written http://www.amsys.co.uk/2014/05/disk-utility-tip-fix-couldnt-unmount-disk-errors/ by the Amsys Apple Certified Team / Blog / Disk utility tip: Fix 'couldn’t unmount disk' errors Posted on 7th May 2014 by Russell Harris Facebook Twitter LinkedIn Reddit Google++ E-Mail+ Disk utility https://github.com/osxfuse/osxfuse/issues/45 tip: Fix 'couldn’t unmount disk' errors 7th May 2014Russell Harris11 CommentsBlog I have found myself recently experiencing a couple of Macs which would not allow me to repair the directory or permissions in failed to Disk Utility, or erase/partition the drive with an error such as: ‘Disc erase failed couldn't unmount disc' or ‘Disk Erase failed with the error: Couldn’t unmount disk.' Even trying to use Network Deployment tools such as Apple's Netinstall service or DeployStudio have also failed to deploy due to these errors. Normally, any ‘Couldn’t Unmount Disk' error is attributed to circumstances where the boot drive is being failed to unmount modified or is being used by an application or process. So the first thing to do is to startup the Mac from another bootable drive such as an external drive or OS X Recovery. You can then run Disk Utility from there. An external drive or a network drive is preferred if it is the internal hard drive you have an issue with, since the OS X Recovery is a partition on the same physical drive which may not be able to successfully unmount or modify your internal disk. To create your own bootable disk, refer to our blog ‘Creating a Mavericks bootable install disk'. I would strongly recommend at this stage attempting to back up any data that is required before proceeding with the following steps. Some of the following steps are destructive and will lose ALL data on your drive. If you have an external bootable disk, connect this to your Mac and power your Mac up whilst holding down the OPTION/ALT key. Then select the desired external drive from the startup manager screen and press the enter key. If you have used our method above to create a bootable installer, choose ‘Disk Utility' from
Sign in Pricing Blog Support Search GitHub This repository Watch 146 Star 2,592 Fork 152 osxfuse/osxfuse Code Issues 31 Pull requests 0 Projects 0 Wiki Pulse Graphs New issue cannot umount or mount an sshfs volume after ssh connection cut #45 Open kcleung opened this Issue Aug 4, 2012 · 46 comments Projects None yet Labels None yet Milestone No milestone Assignees bfleischer 32 participants and others kcleung commented Aug 4, 2012 I am using OS X 10.8 with osxfuse 2.5 and sshfs 2.4.1. After an sshfs volume is disrupted by the remote ssh tunnel server cutting the connection, I can't unmount the directory: $ umount dir umount: dir: not currently mounted $ls dir ls: dir: Input/output error But I can't remount the volume to the directory again: $sshfs user@server:/dir dir fuse: bad mount point `dir': Input/output error Is this the problem of sshfs, or osxfuse? FUSE for macOS member bfleischer commented Aug 5, 2012 Can you provide step by step instructions to reproduce the issue? Have you checked whether the sshfs process is still running when this happens? What happens if you try to kill it? bfleischer was assigned Aug 5, 2012 FUSE for macOS member bfleischer commented Oct 26, 2012 Closed due to inactivity. bfleischer closed this Oct 26, 2012 evildmp commented Jan 15, 2013 I have a similar issue. A volume mounted across the Internet; my iMac goes to sleep; after waking there's a device in /Volumes: Danieles-iMac-2:Volumes daniele$ umount v029 umount: v029: not currently mounted Danieles-iMac-2:Volumes daniele$ ls ls: v029: Input/output error iMac HD Danieles-iMac-2:Volumes daniele$ Danieles-iMac-2:Volumes daniele$ kill -9 4515 # this is the sshfs-static process Danieles-iMac-2:Volumes daniele$ ls iMac HD v029 Danieles-iMac-2:Volumes daniele$ Danieles-iMac-2:Volumes daniele$ umount v029 umount(/Volumes/v029): Resource busy -- try 'diskutil unmount' Danieles-iMac-2:Volumes daniele$ Danieles-iMac-2:Volumes daniele$ diskutil unmount v029/ Unmount failed for v029/ Danieles-iMac-2:Volumes daniele$ Usually, this does not happen when a machine with mounted remote disks goes to sleep. evildmp commented Jan 15, 2013 Just after that, I idly tried hitting Mount for the volume in MacFusion, and had a kernel panic - actually my second about two days, related to MacFusion/OSXFUSE: Interval Since Last Pan