NetInstall set created with SIU using 10.13.1 boots to grey screen/mouse cursor and does not start
| Originator: | neil.martin83 | ||
| Number: | rdar://35384457 | Date Originated: | 7/11/17 |
| Status: | Closed | Resolved: | Partially |
| Product: | macOS + SDK | Product Version: | 10.13.1 |
| Classification: | Bug | Reproducible: | Always |
Summary: Creating a new NetInstall set using the 10.13.1 installer as a source. Clients NetBoot successfully but remain on a screen with a grey gradient background and a mouse cursor. The mouse can move freely and the display will sleep after 10 minutes. There is little/no network activity. The installation does not start and the Mac remains in this state until hard powered-off via the power button. Steps to Reproduce: Create a NetInstall set using the macOS installer as a source, with the following settings: Automation Settings: Automatically install to: Macintosh HD Erase target volume before installing System (Default) Language: English Expected Results: Client should NetBoot successfully and automatically erase the "Macintosh HD" volume and install macOS. A NetInstall set created using a 10.12.6 installer as the source, with the same settings, works as expected. Actual Results: Clients NetBoot successfully but remain on a screen with a grey gradient background and a mouse cursor. The mouse can move freely and the display will sleep after 10 minutes. There is little/no network activity. The installation does not start and the Mac remains in this state until hard powered-off via the power button. I have tried this on 2 iMacs - a 12,1 and 14,1 and can replicate this issue every time. Version/Build: macOS: 10.13.1 17B48 SIU 2: 10.13 (820) macOS installer: 13.1.05 Configuration: All options in SIU are left as default, apart from the Automation Settings which are: Automatically install to: Macintosh HD Erase target volume before installing System (Default) Language: English
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
Dupe of 33920691
Apple Developer Relations
Engineering has determined that your bug report is a duplicate of another issue and will be closed.
The open or closed status of the original report your bug was duplicated to appears in a text box within the bug detail section of the bug reporter user interface. For security and privacy reasons, we don't provide access to the original bug yours was duped to.
If you have any questions or concerns, please update your report directly at this link: https://bugreport.apple.com/.
Neil Martin
Apologies for the delay in replying,
Unfortunately I'm not able to do this as I cannot SSH into a Mac that has booted into a NetInstall environment (at least I don't think I can - please tell me if there is a way). Once it boots, it is sitting at a grey screen and is unresponsive to keyboard input so I'm not able to do anything on the Mac itself. Please tell me if there are any hidden key commands etc I could try there that might bring up something helpful?
As 10.13.2 was released today, I'll try generating a new NetInstall set with it and see how I get on. :-)
As someone who manages Macs for an organisation, I'm an active member of the Mac Admin's community on Slack (there are over 10,000 of us in there!). We even have a #netboot channel. I believe some folks who work at Apple do pop into the Slack - I'm just spreading the word to encourage more of you to do so in the interest of strengthening the relationship between Apple and the systems administrators who manage your devices. :-) It's easy to join in by going to https://macadmins.herokuapp.com/ - many other organisations have senior technical staff actively participating, including Microsoft and Adobe.
Kind regards,
Neil.
Apple Developer Relations
November 15 2017, 9:47 AM Engineering has requested the following information in order to further investigate this issue:
Please generate and attach a sysdiagnose when the issue is occurring. You can ssh in to kick this off, then copy the archive to a USB stick, or via scp over the network.