hdiutil fails to unmount with error 49153

[dom9inic]

I’m just getting started with InstaDMG (late to the party I know) and I’m running up against the problem in the subject line.

Info:

Creating a Tiger train of 10.4.11.
External Drive hosting 10.4.11 with a second partition for image creation, attached to a MacMini for post flight ASR restoring.

I’ve relocated my tmp folder to the Imaging partition as the external drive 10.4.11 partition is too small.

So far just testing a 10.4.0 install dmg with all Apple updates and Office 2008 pkgs. Everything installs and then this:

[code]09:49:12 ######Creating the deployment DMG and scanning for ASR######
Rename the deployment volume: InstaDMG
Create a read-only image
hdiutil: couldn’t unmount “disk3” – error 49153
Scanning image for ASR: ./OutputFiles/08-09-22.dmg
ASR image scan complete
09:49:18 ######Cleaning up######
Ejecting images
rmdir: true: No such file or directory
Removing scratch DMG
09:49:19 ######InstaDMG Complete######[/code]

The logs are no more help than this output here. Is it the relocation of the tmp folder? Any ideas?

[knowmad]

it seems Google is getting faster at indexing because a quick search for ‘hdiutil error 49153’ turns up this discussion at the top of the list ( [url]http://tinyurl.com/3jyb7x[/url] ) but moving on from that starting point I find:
([url]http://www.maclife.com/forums/topic/78898[/url]) this fellow who was doing some coding and came across the same error, he found that he could force the disk to unmount using [code]sudo chroot /Volumes/10-4-base/[/code] which you might want to play with but it still does not answer the question as to why this is happening and I have the feeling won’t really fix your issue…..

Which brings me to a question – is your image usable? ie are you just annoyed and worried at the error or is there a real issue of no image/non-usable image?

back to our search for a solution (I am avoiding work right now)
hmmmm, i found many references to the error, and all seem to agree, it refers to a disk or image that cannot be unmounted because it is missing or damaged. SO, i think we need to see how you shifted your temp directory….. or maybe some other path is incorrect…..
basically, more details please.
knowmad

[dom9inic]

Thanks for responding knowmad, and I did do some googling before posting, but found nothing fitting my problem. Also, as a beginner to InstaDMG I was unsure if I was even attempting the procedure correctly.

So more information needed. I’ve run instadmg.bash a few times and I never get an asr image file – presumably because it is failing to create the read-only image in the first place.

The tmp folder I simply created inside the InstaDMG_1.4b4 folder with the same folder permissions as all the others in that directory. I then hand edited the instadmg.bash to point to that folder as the TEMP_LOCATION variable.

[code]TEMP_LOCATION=”./tmp”[/code]

Should I give a full path here? Don’t think so as it is definitely using this folder when I run the script. That’s the only modification I’ve made to the script.

Not sure what other information is needed. The image creation partition is mounted with the Ignore Permissions on this Volume checked, but I don’t see why that would interfere here.

I think I shall try building the image with just the base OS DVD, then if that works, move onto including the Apple Updates etc etc.

Thanks for the response.

[abitson]

[code] Base OS installed
Compacting and saving cached image to: ./Caches/BaseImageCache/E9D893DC:aeef94fee9465470e813d9fce936ea1cd83434c7.dmg
hdiutil: couldn’t unmount “disk4” – error 49153
Remounting the image with a shadow file (/tmp/instaDMGTemp.Dl4wKs.sparseimage)
hdiutil: mount failed – Resource temporarily unavailable
16:01:38 ######Beginning Update Installs from ./InstallerFiles/BaseUpdates######
16:01:38 ######Beginning Update Installs from ./InstallerFiles/CustomPKG######
Installing createUser.pkg from ./InstallerFiles/CustomPKG/01
Installing createUser…..
Installing createUser.pkg from ./InstallerFiles/CustomPKG/02
Installing createUser…..
Installing createUser.pkg from ./InstallerFiles/CustomPKG/03
Installing createUser…..
16:02:01 ######Correcting some generic installer errors######
Correcting symlinks that point off the disk
Closing programs that have opened files on the disk
Deleting Extensions.mkext cache file
Deleting cache files created during installations
16:04:39 ######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 – Resource temporarily unavailable
Scanning image for ASR: ./OutputFiles/08-09-29.dmg
ASR image scan complete
16:04:45 ######Cleaning up######
Ejecting images
rmdir: true: No such file or directory
Removing scratch DMG
16:04:46 ######InstaDMG Complete######
[/code]

Exact message directly from a fresh start of InstaDMG image creation. Same error as above, and i’m also new at this. I’ve been trying to get images running and keep running into this problem. I’m also NOT getting any image in the output files. It’s empty.

Andrew
————
ACMT

[Tense]

I know it’s an old post. But…. has any one found a solution to this? I still can’t. I have the same error when trying to create the IMG

[code]Base OS installed
Compacting and saving cached image to: ./Caches/BaseImageCache/E9D893DC:aeef94fee9465470e813d9fce936ea1cd83434c7.dmg
hdiutil: couldn’t unmount “disk4” – error 49153
Remounting the image with a shadow file (/tmp/instaDMGTemp.Dl4wKs.sparseimage)
hdiutil: mount failed – Resource temporarily unavailable
14:02:12 ######Beginning Update Installs from ./InstallerFiles/BaseUpdates######[/code]

THEN…. nothing in the output folder.

Thanks.

I have searched and search. Can’t find a solution.

[foilpan]

i just got the same error running the latest instadmg build on a fully loaded os x server 10.5.6. after the instadmg process finished and didn’t output a dmg, i forcefully unmounted any disk images it had mounted and re-ran it. it seemed to complete the second time.

the build includes an applications disc that came with the new macbook pros. that image didn’t seem to unmount properly.

[randygordon]

I have had this problem and can confirm that Symantec Antivirus was the cause.
If you are using SAV disable auto-protect and try again.

[jtoher]

Hi

I get similar problems, if any of the mounted volumes on my build machine have the same name as the root filesystem for the ASR image. In the instadmg.bash script, I have set ASR_FILESYSTEM_NAME=”Macintosh” and to avoid any confusion I also have ASR_TARGET_VOLUME=/Volumes/Macintosh. In my case, if any of the volumes on the build machine are called Macintosh, the script fails. Everything is fine when I make sure all mounted volumes on the build box are named to avoid duplicates.

I also restart the build machine after the script has run successfully, to avoid later complaints from mount.

J.

[foilpan]

interesting… neither of those situations (SAV nor duplicate mount names) applied to me earlier, but i still got the error.

i’ll try again at some point in a fresh build environment and report back.

[knowmad]

oddly enough I had reason to use an older copy of the script tonight and GOT the error for the first time.
I noticed something I had never seen before, an instadmg folder in /tmp with garage band receipts in it… weird….
Good thing I wont be using this old version of the script anymore(don’t ask, its not worth it)

[Author]

Posts