PHASE:Running package scripts

[sidmacs]

I have Deploystudio set up on a 10.11.5 machine. I get my computers to netboot to it no problem.
Created with createOSXinstallPkg
Deploystudio used to copy this in under 4 minutes and then the machine would reboot and start installing OS X 10.11.5. Now, it seems to be stuck and the log on the machine says something like
"2016-06-17 10:37:44.425 DeployStudio Runtime.bin[293:17608] installer:PHASE:Running package scripts"
But it never finishes. Does the same thing with a 10.10.5 package I used months ago successfully.
Any ideas why this isn't working?

[gregneagle]

Yes -- three letters: SIP.

[sidmacs]

Thanks Greg is there a work around to get this working?

[gregneagle]

Boot from a volume with SIP disabled. Apple's NetInstall and NetRestore environments are like this, as is an Imagr NetBoot environment built with AutoNBI. I don't know how to build a DeployStudio NetBoot environment with SIP disabled.

[sidmacs]

Thank you I will work it out... I appreciate your help all the way from South Africa

[hildahlp]

I'm also having this issue with DeployStudio 10.11.5 netboot sets. I posted in the DeployStudio forums about this http://www.deploystudio.com/Forums/viewtopic.php?id=7693 and the Administrator replied "DeployStudio netbook sets are customized recovery systems, so SIP should not apply."

[fuzzylogiq]

A new version of DeployStudio was released a couple of days ago. Amongst the bug fixes is "blocking bless calls" - I'd give it a try. http://www.deploystudio.com/downloads/deploystudio-server-1-7-4-3

[hildahlp]

@fuzzylogiq thanks for the info. I am on the 1.7.4.3 version. I had hoped that the bless bug fix would clear this up, but it hasn't. As a data point, I used createOSXinstallPkg to make an install package without any additional custom packages to see if it was one of my custom packages causing the grief. The "plain" installer errors the same way when installed from the 10.11.5 DS nbi. It works as expected when installed from a 10.10.5 DS nbi.

[hildahlp]

I can confirm the error behavior continues with DeployStudio 1.7.4.3, a fresh DeployStudio 10.11.6.nbi and a freshly rolled InstallOSX_10.11.6_15G31_custom.pkg.

[dhandy0]

With SIP disabled (confirmed with csrutil status) something is stopping hdiutil from mounting InstallESD.dmg and BaseSystem.dmg in Greg's postflight script running under a DS nbi. I also tried DS 1.7.4.3, with a 10.11.6.nbi, and a new installer package. I tested hdiutil in Terminal while netbooted and could mount InstallESD.dmg, but not BaseSystem.dmg. hdiuti just never returns. Under a 10.10.5.nbi with the same installer, it all works fine. hdiutil -debug shows a handoff to diskimages-helper, but nothing more. For now, I'll stick with a 10.10.6 nbi to run DS Runtime.

[gregneagle]

FWIW, I just successfully kicked off a 10.11.6 install while NetBooted from an autonbi-built 10.11.4 NBI set. (https://bitbucket.org/bruienne/autonbi) The target volume had 10.9.x installed.

Specifically, this was an NBI containing Imagr (https://github.com/grahamgilbert/imagr)

I don't have (and have no immediate plans to make) a 10.11.x DeployStudio NBI as I am moving away from DeployStudio.

I know this is dramatically different than the environment you are having issues with, but it implies to me the issue might be with DeployStudio or the NBI the DeployStudio tools build, since this worked in the past with DeployStudio and continues to work in the present with Imagr+AutoNBI.

[gregneagle]

And now, FWIW, I built a 10.11.6 NBI using the make nbi Makefile that is part of Imagr (https://github.com/grahamgilbert/imagr). I was able to install 10.11.6 using a createOSXinstallPkg while booted from the NBI.

[gregneagle]

Try the current code; specifically with these changes: a3236fa

[hildahlp]

Sorry to be so slow with a response, but the changes made no effect with DeployStudio 1.7.4.3, DeployStudio 10.11.6.nbi, and a new InstallOSX_10.11.6_15G31_custom.pkg made with the code changes.

[gregneagle]

We've moved to Imagr, and it works there. I'll leave it to others to figure out if it's possible to modify the DeployStudio NBI to get around the SIP issues -- it's not high on my list since we don't need the functionality.

Expect over time for SIP to make this stuff even harder.