I’m stressing a bit here…
After one or two dozen builds using the instaUp2Date / instaDMG system, suddenly the process is failing completely at the DMG creation stage – the Terminal is showing the following message:
[code]15:58:00 ######Creating the deployment DMG and scanning for ASR######
Rename the deployment volume: Macintosh HD
Create a read-only image
hdiutil: couldn’t eject “disk4” – erreur 49168
hdiutil: convert failed – Le fichier existe
Scanning image for ASR: ./OutputFiles/10.5 Vanilla.dmg
ASR image scan complete[/code]
And the more detailed pkg log is showing:
[code]15:57:44 ######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
15:58:00 ######Creating the deployment DMG and scanning for ASR######
Rename the deployment volume: Macintosh HD
Volume on disk5s2 renamed to Macintosh HD
Create a read-only image
“disk4” unmounted.
Scanning image for ASR: ./OutputFiles/10.5 Vanilla.dmg
can’t open /Volumes/DMGBuilder/InstaDMG/OutputFiles/10.5 Vanilla.dmg read/write
asr: image scan failed – Fichier ou répertoire inexistant.
ASR image scan complete[/code]
At first it happened with my larger build, and thinking I might have introduced a glitch I tried just building the vanilla file, which is what the following logs are from. I’ve restarted the machine, even reinstalled the OS partition from scratch. Still no go.
I’m going to re-download the newest build of instaDMG and try just the Vanilla file again. Assuming that works I’m going to slowly introduce the packages back into the build system (although that sounds like a lot of time and tediousness, something I wanted to avoid by moving to this kind of system)…
In the interim, perhaps someone knows something I don’t? Or sees something in the logs that I’m too stressed to see right now?
Thanks in advance for any assistance.
.
.
Comments are closed