Failed To Unmount Due To Error 49153
Please enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked Grifforama Level 2 (165 points) Q: Absolutely cannot eject an external drive. Please help. I have an external drive that I cannot unmountI am also trying to unmount from terminal and getting a resource buys error./dev/disk2s2 976101344 655132528 320968816 68% /Volumes/New BackupDave-Griffithss-MacBook:Volumes grifforama$ hdiutil unmount /dev/disk2s2hdiutil: unmount: "/dev/disk2s2" failed to unmount due to error 49153.hdiutil: unmount failed - Resource busyI therefore cannot use diskutility or diskwarrior to fix anything as they both require the volumes to unmount before working.I'm petrified I am about to lose all my music on this drive. Macbook 2GHz Intel Core Duo, Mac OS X (10.6.4) Posted on Sep 16, 2010 6:30 PM I have this question too Close Q: Absolutely cannot eject an external drive. Please help. All replies Helpful answers Page 1 Next by dbsneddon, dbsneddon Sep 16, 2010 6:39 PM in response to Grifforama Level 4 (1,525 points) Sep 16, 2010 6:39 PM in response to Grifforama The system believes the device is in use by something.What are you running at the time you try to unmount it?You mention music, is iTunes active at the time?Have you tried unmounting with no other programs active?Dave Helpful (0) Reply options Link to this post by baltwo, baltwo Sep 16, 2010 6:43 PM in response to Grifforama Level 9 (62,256 points) Sep 16, 2010 6:43 PM in response to Grifforama Since you're familiar with the Terminal app, run this:*lsof /Volumes/"name of ext HD"*that will tell you what's open on the HD. Helpful (0) Reply options Link to this post by Grifforama, Grifforama Sep 16, 2010 7:09 PM in response to baltwo Level 2 (165 points) Sep 16, 2010 7:09 PM in response to baltwo Dave-Griffithss-MacBook:~ grifforama$ dfFilesystem 512-blocks Used Available Capacity Mounted on/dev/disk0s2 233769824 214157192 19100632 92% /devfs 222 222 0 100% /devmap -hosts 0 0 0 100% /netmap auto_home 0 0 0 100% /home/dev/disk2s2 976101344 655130928 320970416 68% /Volumes/New Backup/dev/disk1s2 976101344 874504 975226840 1% /Volumes/BackupDave-Griffithss-MacBook:~ grifforama$ lsof /Volumes/New Backuplsof: status error on /Volumes/New: No such file or directorylsof: status error on Backup: No such file or dire
my disk This topic contains 4 replies, has 2 voices, and was last updated by knowmad 7 years, 7 months ago. Viewing 5 posts - 1 through 5 (of 5 total) Author Posts March 12, 2009 at 6:03 pm #375680 Rusty MyersParticipant I've been building images fine since october last year and just this last week, my image creation failed. Here's what the log says 10:46:24 ######Creating the deployment DMG and scanning for ASR###### Rename the deployment volume: InstaDMG Create a read-only image hdiutil: couldn't unmount "disk4" - error 49153 hdiutil: convert failed - File exists Scanning image for ASR: ./OutputFiles/09-03-12.dmg ASR image scan complete 10:46:36 ######Cleaning up###### Ejecting images Removing scratch DMG 10:46:36 ######InstaDMG Complete###### I thought it may have had something to do with a recent apple update or custom package, so I rolled https://discussions.apple.com/thread/2583829?tstart=0 back to the last working image config. That failed as well. I am looking in the /tmp folder right now and I see three versions of the instaDMGMount.* folders. They all are all full images that seem to have been unlinked to the original disk image and stuck! I'm not sure I'm using the proper terms to describe the issues, hopefully you can follow what I'm saying. They look like alias folders. I tried to eject them, but that's not an option. https://www.afp548.com/forums/topic/hdiutil-couldnt-unmount-my-disk/ Show original takes me to the computer view in finder. Right now I'm rm -R them, but it's taking a while. I know my machine has had some issues with mounted disk images and not ejecting them properly. Should I rebuild my image machine? If I delete these folders, do you think I'll be able to create a new image? Is there something else that the logs point to? Thanks Rusty March 12, 2009 at 8:18 pm #375682 Rusty MyersParticipant I just thought to check activity monitor to see if there was any process stuck that was holding onto the mounts. I force quit three instances of diskimages-helpe (that's not a misspelling, that's how it looked in activity monitor) and I was able to delete the old mounts. I'm starting a new image, and hoping it works this time. Although I don't have much hope for it. I'm thinking about just rebuilding the machine. It's not a big deal, and in fact I can use my last image to do the job, so it will take little time, but it's annoying. Anyway, that's my update. March 13, 2009 at 12:47 pm #375686 Rusty MyersParticipant Back again. I imaged my instadmg machine last night with my last working build. I checked-out the lastest version of instadmg through svn. I copied my base image and custom packages into the new instadmg working folder. I forgot to mention, I am building images on a second internal drive. I store
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://stackoverflow.com/questions/18752257/delay-from-osx-installer Stack Overflow the company Business Learn more about hiring developers or posting ads http://www.mactechnews.de/forum/discussion/Unmount-funktioniert-nicht-291485.html with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Delay from OSX “installer” up vote 0 down vote favorite I have the failed to following script to install a Mac package from terminal: #!/bin/sh if [ -d /Applications/XX.app ]; then hdiutil mount XX.dmg cd /Volumes/XX sudo installer -pkg XX.pkg -target / cd .. hdiutil unmount XX fi Sometimes it works fine, but sometimes it ended up with error: hdiutil: unmount: "XX" failed to unmount due to error 49168. hdiutil: unmount failed - Resource busy Actually, after several seconds, XX becomes unmountable. I realize that failed to unmount this may be due to a delay from "installer", which was not done yet when calling "unmount XX". Is there anyway to synchronize between "installer" and "unmount"? osx installer share|improve this question asked Sep 11 '13 at 22:21 Hailiang Zhang 2,56353161 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted I went through the "installer" command manual and not found a direct solution to avoid this synchronizing issue. The solution I came up with is that, after stepping out of "installer", I will keep query the status from "hdiutil unmount" every other second until a normal termination signal is achieved, i.e.: #!/bin/sh if [ ! -d /Applications/XX.app ]; then hdiutil mount XX.dmg cd /Volumes/XX sudo installer -pkg XX.pkg -target / cd .. flag=1 while [ $flag -ne 0 ] do sleep 1 hdiutil unmount XX flag=$? done fi I know this may not be the best solution, and I look forward to more elegant alternatives. share|improve this answer answered Sep 11 '13 at 23:18 Hailiang Zhang 2,56353161 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest N
voraus?Warum Siri dumm wirktSamsung kauft Siris »Eltern«Tipp: Safari-Tabs sucheniPhone komplett löschenAlle Apple-Dienste vereintStart von Fotos verhindernSiri-Vorschläge deaktivieren15 Jahre Mac OS XiPhone nass geworden?iOS 10: Nachrichten im DetailIn-App-Käufe wiederherstellenWLAN-Probleme beheben Anmelden Forum>Software>Unmount funktioniert nicht Unmount funktioniert nicht Polyester23.08.1019:49Hallo *,ich habe ein Problem mit dem unmounten von einem Laufwerk unter MacOS 10.6.4.Ich mounte mein NAS per AppleScript beim Login automatisch und habe nun das Problem, dass unter /Volumes/ bereits ein Laufwerk mit dem Namen gibt. Leider kann ich das bereits vorhandene Laufwerk nicht mit (sudo) hdiutil unmount -force /Volumes/'Name des Laufwerks' unmounten. Ich bekomme immer den Fehler "hdiutil: unmount: /Volumes/'Name des Laufwerks'" failed to unmount due to error 49153, hdiutil: unmount failed - Ressource ist belegt".Nun habe ich probiert alles Laufwerk und auch mein NAS vom iMac zu trennen und neu zu starten, jedoch erscheint das Laufwerk trotzdem unter /Volumes/Hat einer eine Idee wie ich das Laufwerk unmounten kann?Danke schon einmal im Vorraus!GrußPoly Kommentare FritzBox23.08.1020:36Gehe mal per Finder in den Ordner /Volumes/Das besagte Laufwerk taucht da warscheinlich nicht als Laufwerk sondern als Ordner auf. Diesen einfach in den Papierkorb ziehen. Polyester23.08.1020:39Danke das wars. Kommentieren Diese Diskussion ist bereits mehr als 3 Monate alt und kann daher nicht mehr kommentiert werden. Forum14:06Apple Watch 2 - Wartethread(102)13:49Google Drive verbindet sich nach neustart nicht mehr(0)13:45iPhone 6: Display kaputt(26)12:12Foto Mediatheken vereinen.(2)11:23Grafiker zugegen? Erbitte Tipp zum Thema eps vs. svg...(3)11:14Eingegeben Textkürzel werden in Safari (Sierra) beim Login bei mir nicht mehr ausgefü...(1)10:02iPhone 7 explodiert am Gesicht seines Nutzers(18)09:42Mail vom "iCloud Center"(6)09:09Karten App: Route weitergeben in iOS 10(2)05:24Lohnt noch die Reparatur bei einem iPhone 6?(12)15:05Themenwoche MTN(6)GalerieMy EDC (2)En