Recovery image

So following this up...

I put down just the recovery image and it worked.

So from there I changed the recovery config to partition (as well as the
os config) the drive the same way the OS package is set to. Still
didn't work when I imaged. It seems to by-pass the partitioning
function completely.

I then went and tried a Target Boot mode (instead of the Lion 10.7.2 NBI
that we would use in production), and I could see it step through the
partitioning phases on the work flow, but still didn't partition the
drive after the image(s) were put down.

John Wojda

Lead System Engineer, DEI & Mobility

3333 Beverly Rd. B2-338B

Hoffman Estates, IL 60179

Phone: (847)286-7855

Page: (224)532.3447

Team Lead DEI: Matt Beiriger
<mailto:mbeirig at searshc.com;jwojda at searshc.com?subject=John%20Wojda%20Fe
edback&body=I%20am%20contacting%20you%20regarding%20John%20Wojda.>

Team Lead Mobility: Chris
<mailto:cstaana at searshc.com;jwojda at searshc.com?subject=John%20Wojda%20Fe
edback&body=I%20am%20contacting%20you%20regarding%20John%20Wojda.> Sta
Ana

Mac Tip/Tricks/Self Service & Support
<http://bit.ly/gMa7TB>

"Any time you choose to be inflexible in your approach to an
unpredictable project you are already building failure into your plan"

Has anyone found a resolution to this issue?

I opened a ticket with JAMF but unfortunately was out sick for 4 weeks and haven't followed up.

I suspect it has something to do with the partition type being apple_boot that messes all this up. I assume you're trying to reimage a system that has an existing Recovery HD, with a configuration that has the two partitions?

My guess is before you can actually do anything you have to convert back the apple_boot to apple_hfs before diskutil is allowed to touch it, like you convert from apple_hfs to apple_boot to make it hidden. That was my guess, ran out of time before turkey to test that theory.

However, the current Casper Imaging doesn't deal with that so it'd have to be something you do manually prior. Feature request would be appropriate if this is the case.

Just a theory…

This is a fresh install without a previous Restore Partition.

I think this is fixed in Casper 8.4 (was a bug in 8.31). I had the same issue where it would blow past the partitioning setup in the Configuration settings, but worked if applied individually.