[Dreident]

Oh man I cant believe I missed that. Thats what was missing. Ive been using instadmg so long and didnt even think to check my copypasta command. Feel like a complete idiot. Thanks Yoshi.

[Dreident]

Thanks but I tried setting the clock back pre feb 2012 but that didnt do the trick.

[Dreident]

Im running into the same issue. I think the combo update that gets downloaded and cheksummed from apple servers has changed or the catalog 10.7vanilla hasnt been updated properly. I just changed the checksum to b8322dbd1f7b55bf35aac4122ad2204c51307793 like it expects.

[Dreident]

I see. Ill give deploystudio another shot. Ive been using instadmg to package, SIU to create a netrestore image then netboot with OSX SL Svr’s netboot.

[Dreident]

Im not experiencing that issue mentioned in the link unfortunately. Any idea on how to adjust the shadow file space? Its got be something to do with that. On one 6,2 mbp ive tried the lion image – no luck…then swapped immediately on my svr to the SL image and it works no problem.

[Dreident]

Im serving my images from a Snow Leopard Server (10.6.8). Thanks Ill check out the link.

[Dreident]

Heres a link to a pic of my verbose netboot [url]http://imgur.com/ZSK97[/url]. Also to clarify im just trying a straight vanilla install from 11A511 media. No other packages.

[Dreident]

Hi Trisatan. What exactly happens? I had a co-worker (at another office) try to boot an 8,1 with my instadmg/netrestore image and it stopped at the boot screen. Im getting my hands on some 8,1 mbps (thunderbolt?) soon so i can look at the verbose logs since ive been mainly working on deploying 6,2 mbps. I told him to do the manual method for now – copy .dmg to a usb drive and restore it from disk utility.

[Dreident]

Nevermind. Reading is fundamental and it was simpler than I thought :D. No need to bake into train if you already have a .nbi ready to go.

[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.

[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]

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]

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.

[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.

[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.

[Author]

Posts