Posted on 02-20-2015 01:13 PM
[D-008217] Fixed an issue that prevented Casper Imaging from creating multiple partitions when imaging a drive that has core storage enabled.
Solved! Go to Solution.
Posted on 02-28-2015 07:11 AM
Finally tested & noted https://macmule.com/2015/01/02/casper-imaging-corestorage-volumes/
@tkimpton & @donmontalvo, cheers for getting the word out.
Don, you should mark a post as the answer. :)
Posted on 02-20-2015 01:19 PM
Whoops, happens to the best of us I guess!!
Posted on 02-20-2015 02:24 PM
Thank god. I was sick of converting (reverting) CS volumes first. Thanks for pointing it out @donmontalvo.
Posted on 02-21-2015 01:31 AM
Wow that's great :)
Posted on 02-28-2015 07:11 AM
Finally tested & noted https://macmule.com/2015/01/02/casper-imaging-corestorage-volumes/
@tkimpton & @donmontalvo, cheers for getting the word out.
Don, you should mark a post as the answer. :)
Posted on 03-01-2015 02:20 PM
Yay!
Just wish this had of been implemented before we manually reverted 100+ new machines for the start of our new academic year last week!!
Still, thankful for the fix!
Posted on 03-10-2015 11:35 AM
Just curious, is anyone running into issues imaging an encrypted Mac using Casper Imaging 9.65?
Posted on 03-10-2015 10:02 PM
Just a note..
When I initially tested Casper Imaging 9.65 trying to image a volume on which I had re-enabled Core Storage manually (diskutil cs convert disk0s2), but not rebooted after the convert command.. Casper Imaging threw up an error stating it couldn't delete the Core Storage data & halted imaging. (2013 Mac Pro)
But when not messing about trying to recreate problems (or rebooting the Mac after re-enabling CS on a volume), 9.65 seems to be working well, mad props to the JAMF team! :D
Posted on 03-11-2015 02:19 AM
@Adminham Did you have Casper Imaging open when you converted the volume? It seems to cache the mountpoint.. Which will have changed when changing to CoreStorage.
@donmontalvo FV2 is coming, I asked in the other thread, have you tried removing Auto-Run data?
Posted on 03-13-2015 05:15 AM
Updated the JSS to 9.65. Created a new netboot with Casper Imaging 9.65.
I now get the error
Nothing in the log.
Anyone else experiencing this?
Posted on 03-13-2015 06:21 AM
Thanks @bentoms, I was able to get it to work by deleting auto-run/prestage.
But now another issue, actually two issues:
optional image ALT text
optional image ALT text
Its been busy, just getting to circle back around to this.
Don
Posted on 03-13-2015 07:45 AM
@chrisbju & @donmontalvo CS volumes are working fine for me:
@donmontalvo FV2 is "coming" I here.
As for the DP not mounting, see this thread.
Posted on 03-13-2015 08:15 AM
@bentoms wrote:
@chrisbju & @donmontalvo CS volumes are working fine for me:
Here too, unless FV2 is enabled on the target drive.
@donmontalvo FV2 is "coming" I here.
I can bring this up with our rep, is there a thread about support for Casper Imaging and reimaging FV2 enabled drives? That'll be the scenario for us if/when we need to blast a computer, it'll be FV2 enabled.
Posted on 03-13-2015 09:06 AM
Currently (before 9.65) I have a netboot set that runs a script that force unmounts the drive, then creates a new single partition. That has been my way of working around CS enabled drives or FV. After the partition the script then launches Casper Imaging. While you'd want to be careful how you set this up as mine doesn't warn, nor ask, if you want to do this so it's pretty destructive. But in my test environment it works well.
Posted on 03-13-2015 09:50 AM
@Brad_G I did similar, but now imaging does it all for me.
I just tested again & imaged 2 macs that were CS enabled, Imaging reverted & partitioned them fine.
Nice work JAMF!
Posted on 03-13-2015 12:20 PM
@bentoms and I had a Twitter DM to confirm. FV2 != CoreStorage. So yea working fine with CoreStorage enabled drives, unless FV2 is enabled. Then no workie. Hopefully workie soon. Opening ticket with JAMF.
Posted on 03-13-2015 02:50 PM
if its a complete re-image I have my guys open a terminal and do
diskutil cs list
then
diskutil cs delete UUID
and imaging works just fine.
If its encrypted and you just need to add to it and want to keep it encrypted, you can unlock it then it mounts and it should be good to go for imaging as well I think.
Posted on 03-13-2015 02:52 PM
of course i cannot even run 9.65 imaging tool i have to run 9.62 for some reason which means i have to image from 10.9.5 box, I suppose I need to work on that again next week...
Posted on 03-13-2015 03:24 PM
Had to go into Recovery Utility > Disk Utility > Wipe Disk to get that error away.