Skip to content
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.

OS installation does not kick off after reboot - macOS Sierra #19

Open
kkulal opened this issue Sep 26, 2016 · 7 comments
Open

OS installation does not kick off after reboot - macOS Sierra #19

kkulal opened this issue Sep 26, 2016 · 7 comments

Comments

@kkulal
Copy link

kkulal commented Sep 26, 2016

Hi,

I am trying to create Sierra OSXinstallPKG and so far I am not successful.

Package install successfully and asks for a restart, after the restart OS installation does not kick off automatically... instead it stays on the manual installation process asking to accept license and to select the volume to continue the installation.

I am using the latest createOSXinstallPKG script "Modified Aug 2016 for installs under SIP"

Please suggest if I am using the correct script for building the package ? or can I modify the script to automate the OS installation ?

Thanks,
Kumaresh

@arubdesu
Copy link

The process configured by the package install DOES automate the install (minus one detail1) so what you're experiencing is not expected. It is just a script, so you can always download the repo and use the file in the master branch. Myself and others are using that exact version you describe without seeing instances of an un-automated install, so either someone ALSO ran the manual installer application on that computer, or something else is going on. The install log may have more information.

1 Filevaulted volumes require unlock after the reboot, before the automated install process runs.

@gregneagle
Copy link
Contributor

Additionally -- if you wait too long after the pkg is installed to reboot, you may see the behavior you describe. This is controlled by Apple code, and "too long" is defined by their code.

@kirkmshaffer
Copy link

We're seeing a situation where we run the installer pkg successfully, then authrestart pretty much immediately, and the macOS installer doesn't kick-off. Machine goes straight to normal (non-FV) loginwindow. If the user runs the whole process again, it works just fine. I don't see much in the install.log of the failures, and the successes are fresh new files starting with the upgrade process.

@gregneagle
Copy link
Contributor

I have never tested with an authrestart.

Since the boot environment is configured in a very specific way to boot into the OS X install environment, anything that alters the boot configuration is likely to break the OS install. Do you see this issue when not using authrestart?

@kirkmshaffer
Copy link

So we saw successes with the authrestart, but were seeing failures as well. Our testing without the authrestart (though limited) was all successes. We also tested startosinstall processes and autherestart saw similar failures as well. Authrestart is apparently a nice little monkey wrench to our plans. Thanks!

@gregneagle
Copy link
Contributor

Of note, Apple's startosinstall tool does (or at least attempts to do) the authrestart for you if possible. It's poorly documented and full of pitfalls, however.

@kkulal
Copy link
Author

kkulal commented Sep 27, 2016

With further testing I am seeing success.... OS installation kicks off automatically after reboot.

I was earlier testing on 10.11.4 VM which was having some issue... when I tried installing the package after an reboot it worked fine, also tested on 10.11.6 and 10.10.5. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants