Home › Forums › Software › InstaDMG › 10.7.3 image does not boot

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • February 27, 2012 at 3:28 pm #381663
    apfeltee
    Participant

    Hello fellow InstaDMG users,

    my 10.7.3 image does not boot. The Apple logo appears on the target machine and the spinning wheel spinns and spinns forever.

    Is anyone experiencing the same thing?

    My build machine is a iMac on 10.7.3, I use the latest InstallESD.dmg (build 11D50) on the latest InstaDMG svn revision (425). The 10.7_vanilla image (unmodified catalog from repository) builds fine without any errors.

    The 10.7 Vanilla.dmg is restored with Disk Utility via Firewire Target Disk Mode on a MacBook Pro Mid 2010. No Errors.

    When I boot the MBP in verbose mode it is stuck at “Resetting IOCatalogue.”

    Any ideas?

    Thanks,

    +t

    February 27, 2012 at 4:03 pm #381665
    Allister Banks
    Participant

    Hey apfeltee,

    I have seen an issue with 10.7.2 DeployStudio NetBoot sets stalling indefinitely on restore when building 10.7.3 on a 10.7.2 machine. Is the MBP you’re using running 10.7.3? Thanks,

    Allister

    February 27, 2012 at 4:24 pm #381666
    apfeltee
    Participant

    Hi Allister,

    thanks for the reply.

    Plain InstaDMG images are used with DS in our environment, but in order to track my issue there is no DS involved here. The MBP was previously deployed with DS and a workflow that installs 10.7.2. But the restore task with Disk Utility should have erased everything, shouldn’t it?

    Thanks,

    +t

    February 27, 2012 at 4:45 pm #381667
    Allister Banks
    Participant

    Hey apfeltee,

    My theory is that, even though the sha1’s between the 10.7.2 and 10.7.3 versions of asr hasn’t changed(which is what DiskUtility should be using under the covers when you’re erasing the destination), somehow restoring (or creating) 10.7.3 images with a machine running 10.7.2 produces a non-working result. At least, all I needed to do to create and restore 10.7.3 images successfully was to make sure the machine (or DS nightly netboot set) I was using was also running 10.7.3.

    Allister

    February 27, 2012 at 5:17 pm #381668
    apfeltee
    Participant

    Hi Allister,

    the machine I created the image with is an iMac running 10.7.3. I used Disk Utility on that machine to restore the MBP via Firewire Target Disk Mode.

    However, I’m erasing the disk of the MBP right now (writing zeros over the whole disk) to prevent any side effects from previous installations and will try again.

    Thanks for the tip with DS. I will create a 10.7.3 DS NetBoot Set when my InstaDMG image finally boots. As an intermediate solution, I install the 10.7.3 Update in my DS workflow. (Issue with this solution is the iTunes and Airport Utility Updates seem to be ignored or not recognized as they pop up in Software Update.)

    +t

    UPDATE: Same thing with erased hard drive. Maybe the problem is I used Disk Utility on 10.7.2 to wipe the disk. Tomorrow I will try again doing all steps on OS X 10.7.3.

    March 2, 2012 at 4:49 am #381678
    ktappe
    Participant

    I am seeing the same behavior [b]but only on older Macs[/b]. I develop our 10.7.3 image using InstaDMG on a 2011 iMac. The image produced by instaUp2Date boots 2011 iMacs, 2011 MacBook Pros, and 2011 MacBook Airs.

    But on 2008 iMacs it produces the non-booting scenario you describe.

    Try this to see if your scenario exactly matches mine: Boot the misbehaving Mac with the shift key held down to induce Safe Boot. On mine this did allow the Mac to boot, though doing so (by design) prevents firstboot.sh from executing. Once the Mac boots to the login screen, reboot it. Then firstboot should execute and you’ll see your image.

    My working theory is that instaUp2Date removes some boot caches that newer Macs’ firmware are able to recreate but older Macs need Safe Boot to be induced to recreate. But I’m not good enough with Python to poke around instaUp2Date.py and disable the cache removal step to prove my theory.

    Allister: Any thoughts on this?
    -Kurt

    March 22, 2012 at 10:56 pm #381722
    ktappe
    Participant

    Updating to the latest revision (439) of InstaDMG and using the 10.7.3 reference build instead of patching 10.7.0 did fix the problem; older iMacs boot fine now.

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

Comments are closed

Copyright © 2025 AFP548. All Rights Reserved.