Path is not a directory & Recovery HD

27 views
Skip to first unread message

Andy Cunningham

unread,
Dec 4, 2012, 4:01:15 PM12/4/12
to instad...@googlegroups.com

All:

I am having a hell of a time getting InstaDMG to complete a run on 10.8.2, creating a 10.8.1 image. It keeps failing after installing all of my packages with the following:

Working on folder 013 (11:49:08)
Installing iPhoto9.4Update.pkg
Dec 3 11:49:09 a201353.local installer[42106] : Product archive /Volumes/Storage/instadmg/InstallerFiles/CustomPKG/013/iPhoto9.4Update.pkg trustLevel=501
Package name is iPhoto Update
Installing at base path /private/tmp/idmg.KoCA/idmg_mp.ENc3/Macintosh HD
PHASE:Preparing for installation…
Dec 3 11:49:10 a201353.local installer[42106] : -[IFDInstallController(Private) _buildInstallPlan]: location = file://localhost
STATUS:
%100.000000
PHASE:The software was successfully installed.
The install was successful.
Folder 013 done (11:49:14)
Working on folder 014 (11:49:14)
###### There were no items to install in: /Volumes/Storage/instadmg/InstallerFiles/CustomPKG/014 ######
11:49:14 ###### Cleaning up ######
Ejecting images
"disk2" unmounted.
"disk2" ejected.
Unmounted the Target Disk image from /private/tmp/idmg.KoCA/idmg_mp.ENc3/Macintosh HD
###### Internal error: tried to eject an image from /private/tmp/idmg.KoCA/idmg_mp.ENc3/Macintosh HD/../Recovery HD but that path is not a directory ######
rmdir: /private/tmp/idmg.KoCA/idmg_mp.ENc3/Macintosh HD/../: No such file or directory
Deleting scratch DMG

Notice that the failure is around unmounting the Recovery HD. The path that it is using seems odd to me. Why point to “…idmg_mp.ENc3/Macintosh HD/../Recovery HD” instead of “…idmg_mp.ENc3/Recovery HD”? As to why Recovery HD is not being recognized as being a folder… no idea.

At any rate, I would really like to get this sorted out. Any advice appreciated!

-Andy

Kurt Tappe

unread,
Dec 5, 2012, 12:34:28 AM12/5/12
to instad...@googlegroups.com
Does the build work if you remove the iPhoto update package? Or, more importantly (based on my experience), are any of your installers .dmg's? Especially .dmg's created with Composer.  Those tend to not unmount properly and/or screw up the unmounting of other images such as the ones InstaDMG uses for the build.  Start commenting out portions of your catalog(s) until you find the culprit, but start with any .dmg's. If Composer-generated .dmg's, convert them in Composer to .pkg's and see if that helps.

-Kurt

--
You received this message because you are subscribed to the Google Groups "InstaDMG-Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/instadmg-dev/-/xfw9UsTxKn8J.
To post to this group, send email to instad...@googlegroups.com.
To unsubscribe from this group, send email to instadmg-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/instadmg-dev?hl=en.

Andy Cunningham

unread,
Dec 5, 2012, 11:23:26 AM12/5/12
to instad...@googlegroups.com
Thanks Kurt and Josh for the advice; it ended up that the process was failing because of an empty folder in the workflow. Removing it allowed the build to complete without any issues. Yay!

--Andy
Reply all
Reply to author
Forward
0 new messages