Netboot Upgrade, fails to netboot

ImAMacGuy
Valued Contributor II

Rather than redo the work on the netboot, I figured I would just use the 10.9.1 build that i used to create the NBI, run the combo update, and re-run it through SIU. That completes as expected, however when I try to netboot a machine I just get a Circle with a line through it.

I can reboot off the (now 10.9.2) partition just fine though, so it seems like it's failing due to the SIU.

Any ideas?

157 REPLIES 157

franton
Valued Contributor III

None at the moment. I'm getting the same with a fresh build of the OS.

ImAMacGuy
Valued Contributor II

that's encouraging.

franton
Valued Contributor III

I assumed it was to do with my attempts to modify rc.netboot file. I'm building a totally vanilla one now.

ImAMacGuy
Valued Contributor II

ohh that could be, I was replacing the rc.netboot also..
i do have the unmodified file, I will delete the modified one and restore the original and see if that helps.

I'm also trying a different piece of hardwa... oh it failed too.

ImAMacGuy
Valued Contributor II

original rc.netboot failed too.

franton
Valued Contributor III

Are you HTTP or NFS booting these images?

ImAMacGuy
Valued Contributor II

nfs.

franton
Valued Contributor III

I just tried HTTP. It failed but I wasn't surprised at that because our servers have never liked that setting.

Trying NFS now ...

franton
Valued Contributor III

Nada. I've now ripped an older version of SIU from a 10.9.1 mac and i'm going to try that instead.

ImAMacGuy
Valued Contributor II

hmm found this on the apple kb for 10.9.2

Improves the reliability of diskless NetBoot service in OS X Server

jhalvorson
Valued Contributor

Just a point of reference, as of Feb 26, 2014, the latest versions are:
OS X 10.9.2 (13C64) with Server 3.0.3 (13S3007) and System Image Utility 2 (10.9.2 675)

Do those versions match what your using? SIU 10.9.2 675 and the NetBoot .nbi hosted on a server running Sever 3.0.3?

I recall there has been a pattern that Server updates get released within a few days after a OS X 10.9 update are released. Maybe another update to Server is coming?

ImAMacGuy
Valued Contributor II

<edit> sorry apparently my inner Yoda leaked in to my response... let me rephrase it.

I spent yesterday afternoon and this morning upgrading everything :)

franton
Valued Contributor III

@jhalvorson Yes they match.

franton
Valued Contributor III

I've wasted all day on this. As far as i'm concerned, SIU on 10.9.2 is totally broken.

Lotusshaney
Contributor II

I bet that this is an older mac, say 2011 and that the kernelcache file inside the .nbi/i386/x86_64 folder is larger than 32 MB ???

ImAMacGuy
Valued Contributor II

Franton, did teh 10.9.1 SIU work?

franton
Valued Contributor III

Nope. I'm about to try processing the same captured OS DMG through 10.8.5 SIU instead.

cbrewer
Valued Contributor II

Seeing the same thing this morning. Updated NetBoot image to 10.9.2. After using 10.9.2 SIU and adding it to my NetBoot server, the image is unbootable. I've tried modified and unmodified rc.netboot files. I've also tried diskless and not diskless, http and nfs. My NetBoot servers were running 10.9.1 and the problem remains after upgrading to 10.9.2.

cbrewer
Valued Contributor II

@Lotusshaney is onto something. My kernelcache file is 35.5MB and I was able to boot my 10.9.2 NBI from a 2013 MacBook Pro Retina. However, my 2011 MacBook Pro would not boot it.

Lotusshaney
Contributor II

Here is my blog post

Keep getting no-entry signs booting from a net boot image made on a mac that boots fine from the same image when its on a HDD ? New Macs Netboot fine but old ones don’t ? Check the kernalcache in the .nbi folder.

TFTP original file limits is 32MB. I think new models have removed this limit in there firmware. All my old NB images kernalcache files are under that size.

10.9.x ones are 35MB so won’t TFTP to the older macs. If I remove unused kexts and build the image the kernalcache is under 32MB and EVERYTHING boots !!!!

I think Apple needs to look at system image utility and make it more selective on needed kexts

Lotusshaney
Contributor II

TFTP is used to copy the kernalcache file over to the client regardless of NFS or HTTP. version 1 had a limit of 32MB file transfers. New version of TFTP supports 4GB file transfers so Im guessing apple has update the firmware in some models and not others

ImAMacGuy
Valued Contributor II

i've opened a ticket with apple enterprise support on this.

Thank you for your findings, I will get teh ticket update with the info and report back.

ImAMacGuy
Valued Contributor II

double post

franton
Valued Contributor III

I need to now have words with my bosses over the Xserve replacement order. I've got 1,1 Xserves and I'm betting there's no way to make them work.

franton
Valued Contributor III

@Lotusshaney Which kexts are you removing from your image?

Lotusshaney
Contributor II

I removed the atto raid kexts and the apple 802.11 wifi drivers. I'm net booting via thunderbolt or USB so I don't need wifi.

With these removed I get a kernalcache of 25MB when I build the nbi and everything boots. 2013 MBPr's and pros to 2009 iMacs :)

franton
Valued Contributor III

Thanks for the tip! I'll give that a try tomorrow when i'm back in the office.

franton
Valued Contributor III

Having ... fun ... with this. I'm going to replace the kernel cache file generated by SIU with one generated by the following command: ```
sudo kextcache -prelinked-kernel kernelcache /System/Library/Extensions/ -kernel /mach_kernel -n -a x86_64
```

franton
Valued Contributor III

Forget that. It just boots and then shuts my 2012 iMac down.

franton
Valued Contributor III

Ok Mike Bombich's old guide (copied on AFP548) seems to have a better solution. I'm now trying:

sudo kextcache -a x86_64 -s -l -n -z -m kernelcache /System/Library/Extensions/

franton
Valued Contributor III

Sorry @Lotusshaney ... I just can't replicate what you're doing.

ImAMacGuy
Valued Contributor II

I got a response from Apple Enterprise support.

Thanks for providing additional info. Though your notes about the size of the kext cache are interesting, I suspect the underlying cause is the method used to update to 10.9.2. In versions of Mac OS X prior to Lion, it was recommended that you apply a combo update to create a "universal" boot image. In OS X Lion and later, that methodology has changed somewhat. It's easy to miss, but there is a section in <http://support.apple.com/kb/HT4178> for OS X Lion and later that says: Important: Even if the computer you are imaging has the latest version of OS X installed, you must update it using the latest version of the installer to create an image that supports multiple Macs. You can redownload the installer by pressing and holding the Option key while you click the Purchases tab in the Mac App Store application. You'll need to create your NetBoot image from a source that was updated by installing OS X 10.9.2 using the Install OS X Mavericks.app as described in that paragraph. Based on my own testing, an image created using that method should work as expected with multiple Mac hardware revisions. Please let me know if an image created using that method exhibits issues.

Basically they are saying download a fresh 10.9.2 installer from MAS, adn then recreate the whole netboot. But I suspect that franton has tried that already.

franton
Valued Contributor III

No, but i'm about to now.

nessts
Valued Contributor II

This is what i did prior to shutting down my NB and running SIU, now my older systems NB.
sudo rm /System/Library/Extensions/IO80211Family.kext/
sudo rm /System/Library/Extensions/ATTO*

franton
Valued Contributor III

Going from a fresh install didn't work. The file is still 35.5Mb in size. The net boot.dmg I created earlier came from a fresh install as well. Going to try @nessts tip.

Lotusshaney
Contributor II

@nessts thats exactly what I do, but I boot after the delete

gachowski
Valued Contributor II

I am seeing the same issue, open a tix with Apple Enterprise support.

: )

nessts
Valued Contributor II

Apple Enterprise Support's answer will be buy new hardware it works on the new hardware just fine.

ImAMacGuy
Valued Contributor II

i'm pending their response from my updates to the ticket today.