Did you find a solution? I have the same problem at the moment.

Does the DMG have any spaces in it's name?

Same problem here. Works fine if I package up Final Cut X or Motion, but get the error when trying to package Compressor (no spaces in the name).

To work around it, I am saving it as a PKG instead of a DMG.

@nethers posted:

Error: Command failed with error code (1): '/usr/bin/hdiutil'

Tim, can you post the rest of the log?

Edit: I thought it worked by removing the spaces, it really seemed like it but it failed with the same error again.

I ran across the same issue when trying to build a Google Sketchup 2013 package.
As far as I know the only difference I have made is this is the first package I've made using Mavericks.
Running 8.73.
Tried a permissions repair but it didn't fix anything.

Sorry, I do not recall the solution. It has been a while.

I figured out what it was. I had installed Drive Genius 3 on my work machine and it includes a function that's called DrivePulse. Where it scans you disk for errors live. Or something like that.

I remembered I had difficulties and odd problems with disks in general when that was active so I flipped it off and then Composer started working again. Maybe you have some similar tool or even DrivePulse that's messing it up.

At this point it seems like an issue specific to Mavericks. I tried it on both a clean Mavericks VM as well as a 10.9 physical machine. It's just the OS with Composer installed on it and there aren't any spaces in the package name. Everything failed with hdiutil error. I spun up a new Mountain Lion 10.8 VM with the same config and I was able to build a DMG in Composer 9.2 just fine.

I too have encountered hdiutil errors when exporting packages from Composer on Mavericks. Will let the group know if I discover a workaround.

I just encountered this error for the first time on Mavericks using Composer 9.21. A clean instal of the OS did not help, repairing disk permissions did not help, rebooting did not help, saving to any other location on the hard drive did not help. I was able to build all my other packages just fine with the same configuaration and now suddenly I can't.

Hi all

To rule out if it's a permissions thing, one thing you could try is logging in to the client and root user ( obviously not recommended normally) and see if that works.

I tried the fix posted here : https://jamfnation.jamfsoftware.com/discussion.html?id=4071 and it worked for me. Hope you have the same luck!

which fix please? i can see a couple on here

which fix please? i can see a couple on here

Sorry, the one by franton, to temporarily disable McAfee, allowed me to finish packaging with Composer.

@twrangham You're welcome! However I've since found it's not completely reliable for me. I suspect there's something wrong with that specific computer however as my test mac never does this.

I also encountered this error running composer 8.73 on OS X 10.9.1, if you run the hdiutil command that composer runs in verbose mode you will see error -5341. A quick google search returns this thread https://discussions.apple.com/thread/5667409 suggesting Mavericks throws this error for any package > 100MB the thread provides a workable fix by running the hdiutil command with a -size flag, obviously this wont work directly through composer but you can run the hdiutil command separately to get the same results. For reference command i used to create .dmg package below:

/usr/bin/hdiutil create <target_package>.dmg -srcfolder <composer_dir>/<pkgname>/ROOT -volname <pkgname> -gid 20 -mode 755 -puppetstrings -format UDZ0 -size <pkgsize>M

I will raise a support call with JAMF

Thanks nixonc. I'm seeing the same problem this morning. Though I've been building other images for weeks.
Will pass this thread on to my rep as well.

Seems OK now! Here's what I did (though not all was relevant, you choose):

1. Ran Disk Warrior (no directory damage). Ran Fix Permissions/Check Files & Folders from Disk Warrior (1 minor problem).


2. Rebooted to boot drive, created package source with Composer (no spaces, no periods) and built as DMG, saving it to EXTERNAL FIREWIRE DRIVE. OK!

Happened again! Tried my last posted fix, didn't work. Ran Onyx, worked! PS-I was trying to package Symantec Endpoint Protection 12 when it failed this time, and it worked with a different app (UTS) after running Onyx, so I'm not sure it wasn't something Symantec did, you know those pesky virus programs! (SEP12 is still running, though).

@ccardona1, if you are trying to deploy Symantec Endpoint Protection 12.1.4 you might have a look over at https://jamfnation.jamfsoftware.com/discussion.html?id=9396 for a way that doesn't use composer at all.

Hopefully you aren't running antivirus on your development Mac. :)

Had the same problem using 10.9.2 using Composer 8.73

Disabled On-access scanning on McAfee Security 1.2.0 and I can now create DMG's

So no actual, reliable, fix for this?

Have just got this error, packaging Google Chrome browser, on Mavericks iMac (10.9.2) using Composer v8.73. No anti-virus or other scanning type software running.

Strangely enough I did have some pre-packaged Sources in Composer, so tried one of those (Safari 6.1.1 update) and it created the .dmg fine!

Would love a resolution for this.