On behalf of Dreident

[Allister Banks]

Hey guys. Ive come across an issue. I get kernel panics on my 3,1 macbook pros after booting from the network. This happens between the globe icon and the imaging screen. I’m using Leopard 10.6.5 build 10H574. Screen shot: [url]http://i56.tinypic.com/jux26s.jpg[/url]

Now I dont get this issue if I boot from one of my earlier test images with a 3,1 mbp (10A432) or if I boot from a 4,1 mbp with my most recent image (10H574). I also copying the most recent image (10H574) from a usb drive to the 3,1 with disk utility and it worked.

My Image lab hardware:

a few 3,1 mbps and a 4,1 mbp

Instadmg settings:

svn version 410
vanilla 10.6 catalog + 1 custom catalog that calls vanilla 10.6 that contains: clearReg and createUser
I had other packages but disabled them for troubleshooting
import created dmg to SIU netrestore

The error looks like an ethernet driver having an issue starting.

[Dreident]

Thanks Allister. I just tried a vanilla 10.6.5 image without any extra packages and Ive got the same issue. 3,1 mbps kernel panic and the 4,1 mbp boot fine. Maybe one of the apple updates in vanilla 10.6.5?

[Allister Banks]

Checksumming should reduce the variables, you should be getting the pkgs “as advertised” = not corrupted
It’s the same BaseOS disc, too? BTW, is it 10.6.0 or 10.6.3?

Does “copying image from usb drive” mean you restored it to the disc and it booted fine?

Allister

[Dreident]

All the checksums passed on the vanilla 10.6.5 updates. Ive deleted all of them though and re downloading as I type. Installing from usb drive means booting to an osx disk, starting disk utility then applying the instadmg image driectly to the 3,1 mbp hard drive. It works if I do it that way.

[Dreident]

I completely removed all of the cached files and recreated/redownloaded them (image, all apple updates). Im still getting the same problem. Ive tested a 6,2 and a 4,1 mbp with no issues. The 3,1s that I have all fail with that kernel panic which im guessing is a nic driver issue.

Anyone have the same problem? My next step is to comment out the combo update from the vanilla catalog.

[Allister Banks]

It can’t be the image, it’s got to be how its being offered up to netboot clients. Please suck in the first createUser/clearReg “usb drive restored” image(or even quicker, just mount the instadmg image), preferably before booting it, with SIU’s ‘create network disk image’. Or tell me why you don’t think that would work, things are a little too vague for me still so I could be wrong. I think it’s that you’re not letting SIU import a format its expecting.

Allister

[Dreident]

Well all things point to the image. I have two test servers, 1 vm and 1 running on a 3,1 mbp. Tried creating the netrestore from both and same problem. Ill try the image I created tonight without the combo update tomorrow.

Ill try that deploy to 3,1 then capture it again but im not sure how that will affect the 4,1 or 6,2 deployments. Im trying to be as universal as possible. Thanks for the feedback.

[Allister Banks]

Sorry, just to clarify one point: are you using SIU’s ‘create network disk image’ from either the ‘usb drive and installer media restored’ image or the instadmg-created dmg when it’s mounted?

Allister

[Dreident]

To clarify im using instadmg to create the dmg images. in this case im using only the vanilla catalog. I then create a netboot image by starting SIU, I select “Net Restore Image” and then create the netboot without any customizations. I select the new image in server admin and then test with a network boot.

Ive confirmed in my lab that something is up with the 10.6.5 combo update regarding 3,1 macbook pros. I created a new netboot image without it but with all the other standard updates as of Nov 2 and it work with all of my macs (3,1/4,1/6,2 mbp). I also have a new pic that has more 3,1 10.6.5 update kernel panic details below

[Dreident]

stupid spam blocker. pic is hosted at i51[b]dot[/b] tinypic [b]dot[/b] com [b]slash[/b] 9gx7p0 [b]dot[/b] jpg

[Dreident]

Ok looks like I got an acceptable solution. I took the i386 folder (/library/netboot/netbootsp0/mynetrestore.nbi/i386) from a 10.6.5 less image which contains the boot files and slapped it on my latest custom image with 10.6.5. It works for my 3,1s and my 4,1 but not the 6,2.

I get around this by having two identical image folders with different i386 boot files and then filter by model. Do this by going to server admin -> netboot -> settings -> images -> click on bottom left pencil icon. Thanks for the help.

[Allister Banks]

Great work! Sorry I couldn’t have been of more help. This is a good one to offer up to the great google in the sky as well, it possibly has something to do with the EFI changes that broke whole disk encryption along with 10.6.5.
And yes, spam blocker is annoying the everliving heck out of me too.

Allister

[Author]

Posts