Home Forums Software InstaDMG InstaDMG 425/443 & Lion 10.7.3 make 563KB DMG

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #381730
    ctan
    Participant

    Hey Y’all,

    Been using InstaDMG for lots of good things for years now, never really had a problem as it always seemed to ‘just work’. Kudos for that. But now I’m running into a problem I haven’t seen posted here yet. I am trying to run either the direct ./instaDMG.bash or the standard instaUp2Date.py (-p …) and I continually get a 563KB DMG file both ways.

    I have tried this on a freshly built MacBook 4,1 and an older MacPro 1,1. Both running 10.7.3.
    I have downloaded the latest versions of InstaDMG (SVN says I am at revision 443, but instadmg says I am running 425)
    I have re-downloaded the Lion installer and re-tested the extracted InstallESD.dmg to confirm it works (it does).

    I have put the InstallESD.dmg into the required folders and it appears to be running (as it does make the DMG), but I get a host of errors when is it under the ##Looking for a Cached Image##. There are lots of “domain/default pair of (/private/tmp/…./…/System/Library/CoreServices/SystemVersion, …) does not exist” errors, including the ProductVersion (twice), ProductBuildVersion, and ProductName.

    Then I get an error…

    ./instadmg.bash: line 665: [: 7: unary operator expected Target OS: ()

    Some benign warnings about 10.5 and the installer deamon-jailing. Instadmg continues on like normal, but way faster (say 2 minutes) and finishes. The DMG is so small it is crazy.

    The MacPro has been used for the past year to pump out the 10.6 instaDMG images with no issues. The MacBook was just imaged just to see if the issue with with the MacPro. Which it doesn’t seem to be.

    If anybody can offer any assistance as to why InstaDMG is acting this way, I would be extremely grateful.

    Thanks in advance.

    -Chris

    #381731
    Allister Banks
    Participant

    Good question! Sounds totally wacky. Could you please post a link to your debug log?

    Allister

    #381735
    ctan
    Participant

    Thanks Allister!

    I uploaded it to my gDocs, here’s the link.

    https://docs.google.com/document/d/1qCevA8FzKXDnV5E1B8DFZAKk98RiWZp_YThsxGoS2_A/edit

    I noticed someone else had the problem also with a Lion USB stick.

    Let me know if you need any other files or want me to try something else.

    And thanks again.

    -chris

    #381736
    ctan
    Participant

    If putting that link was a no-no, I apologize. I can put it in the text of the post,but it seemed a bit long.

    -c

    #381738
    ctan
    Participant

    I just saw the thread “package apocalypse” by yoshi and will try the work-around in the AM. (turning your clock back to Feb).

    #381739
    Allister Banks
    Participant

    Turn back the clock?
    h*tp://twitter.com/golby/status/184811168739762177
    Haven’t done the process myself, but
    1. Convert InstallESD.dmg to read-write
    2. run Greg Neagle’s fixer tool on the two expired-cert packages
    3. Re-convert to read-only
    run as normal
    Profit

    @golby tested it, and it worked. Really, I want to wait until 10.7.4, or a ‘fixed’ 10.7.3 from the MAS. At least SIU is probably broke, too, so I don’t feel as bad. Sorry I don’t have a easier fix.

    Allister

    #381740
    carson
    Participant

    Same issue with 443, but my image ends up at 1.47GB when running the unmodified 10.7 catalog file. Restored to an external drive and it KPs each time I try to boot from it. Logs are here:

    http://dl.dropbox.com/u/2860797/insta_logs.zip

    I’m doing another run now with all updates commented out to see if anything changes.

    UPDATE: I’ve commented out all updates in an attempt to just focus on using the InstallESD.dmg installer for a 10.7.0 base image. I now get a 566KB image file. I think my issue lies with the InstallESD.dmg installer.

    #381741
    ctan
    Participant

    So setting the time back to February 27th (random date in past) worked. I was able to build a working DMG out of InstaDMG and am now trying InstaUp2Date using the vanilla 10.7 catalog (with the 10.7.3 update commented out).

    I considered what you said about converting to a r/w, applying the fix, then converting back. But for making a single disk image for use in DS I figured turning the clock back a month for 1/2 a day would be far easier!

    Hopefully when Apple publishes 10.7.4 this can all be behind us. But until then, I think I’ll go back to the leap day anytime I need to update the Master DMG.

    Thanks for your help and for everyone’s hard work with InstaDMG & InstaUp2Date!

    #381743
    sbrito
    Participant

    No need to convert to read/write. Just run the script on your image and it will create a new updated image. Works beautifully.

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.

Comments are closed