Casper Imaging + 10.10.2 = No Block Copy

I think its more devious than just the block copy, i was noticing package failures different ones each install, and without casper when booted to 10.10 and installing, i went to a 10.9.3 image and installed the OS, and packages and it works fine. So, I am not sure we should be blaming JAMF because of problems with 10.10.x

@adamlalicker, there is no need for a 10.10.2 NBI as no hardware will ONLY boot to that version. So reverting to a 10.10.1 NBI should work.

Since Yosemite, a lot of modern hardware ships with the internal storage preconfigured as CoreStorage. Saw a full-up image (booted from Mavericks, but Casper Imaging 9.63) taking forever today and realized it was doing file-by-file copies. Stopped it, ran Disk Utility, saw the machine was CoreStorage (it likely shipped with Yosemite), reverted it to JHFS+, and reformatted the drive, and Casper Imaging 9.63 did a block copy. So who knows if that has anything to do with it...

I've been running into the same errors as everyone else with 10.10.2 as the host machine.

It just does that installing package as opposed to the block copy. I've done everything I can possibly think of and I cannot get this resolved at all.

Just for more background, I use Target Mode imaging.

I've been working with support and my TAM for 3 days now and they think it has something to do with the antivirus. I'm using Sophos and have never had an issue until now, even when we were using Symantec. I highly doubt antivirus could possibly play into this, but maybe someone else out there can confirm this.

I was able to image ok using a boot volume with 10.10.1 and using Casper off of that. So I think I can agree that 10.10.2 is the root cause here.

On that same note, is there any official word on when an update or fix is going to be in place? I can get by for now, but it would be nice to at least have a timeline as to where this sits.

Per my account manager:

There is a defect with a machine running 10.10.2 that it will not block copy - D-008472.

So at the very least keep an eye out for D-008472 in future release notes.

We use a USB boot disk for Casper Imaging… I re-formated it with 10.10.1 and it works fine. Casper Imaging 9.63 just doesn't like 10.10.2 for some reason.

@RHammen, https://macmule.com/2015/01/02/casper-imaging-corestorage-volumes/

Confirmed that 10.10.2 as a boot source is the block copy problem (or one of them).
Went back to 10.9 5 boot source and it was OK.
JSS 9.62.

anyone heard when the fix (9.64) might be coming out?

@CorpTech my account manager stated that it should be a bug fix in the release of 9.64. Just look for D-008472 in future release notes.

I'm guessing, based on previous release history, we'll see an update within weeks, not months. JAMF have been trying to squash bugs in the 9.6.x chain without hopefully introducing too many new ones ;-).

In case anyone missed it, 9.64 is now out:

[D-008472] Fixed an issue that caused an OS X v10.10.2 DMG with a priority of “1” to copy excessively slowly when using Netboot or Target Mode Imaging.

i saw it and now cannot image at all with 9.64. I will try to get back with a resolution, but be careful out there.

Well that's comforting...

I haven't tried imaging yet, but that is not cool at all.

Put Casper imaging 9.64 in our NBI and imaging fine now for me. JSS still running 9.62

I too was having this problem from a boot drive. I tried removing compiled configuration profiles and re replicating my drive amongst many other things. In the end I completely wiped the boot drive, installed 10.10.2 and replicated from scratch. I didn't expect it to make a difference but it is now working for me again.

Is this still an issue on 9.65? Planning our move to 9.65 and we cant be dealing with this.

@dgreening it is fixed, but there are other issues to lookout for.

See this

And this

There are others too. Search for "9.65".
9.65 is not without flaws, but the core storage thing appears fixed.

I think that we are good in terms of those two reported issues. We are all AFP and don't have $ : or / in our AD service account password.

I used Imaging 9.65 with our 9.62 environment and block copy is back!

I have a 9.65 server and 9.65 imaging app, and using target mode imaging, then fill out the hostname click ok and the imaging app freezes, never images the machine, never un-mounts the disk the elapsed time freezes and never moves. Local disk distribution point.
same thing happens on a 10.9.5 10.10.2 machine running imaging.

I'm having issues with 9.65 running on 10.10.2 and Target Mode Imaging - basically that the resultant disk has bad permissions (everything is owned by 99 instead of 0). Fixing disk permissions allows the resultant computer to boot, but no restore partition is created. I'm using an AutoDMG 10.10.2 base.

@dgreening - I see in another post that the "!" character is bad as well. I have that in our accounts and I need to change that. Casper Admin is crashing like crazy when replicating the DP's - so hopefully that helps alleviate that.
Also, if you're using a beta of OS X 10.10.3, Casper Remote 9.65 crashes on launch (confirmed by others) so using 9.62 works.

Casper Imaging 9.65 seems to work ok on 10.10.3.

After limited testing, I'm seeing the problem is back in Casper Imaging 9.7 on a 10.10.3 netboot image. I can confirm that 9.65 still works from the same image.

I can second that with 10.10.3 CasperNBI, 9.72 issue is back.... Having success with 9.63 and 10.10.3 image.... Any word on a fix?