So we have been using Clonedeploy (Crucible) for a while now and always has worked flawlessly with Yosemite images. We have a script we wrote that once we image we log in with a basic account on the machine and launch the script it resizes the drive. This has worked 100% in Yosemite. Well this summer we are imaging all our 2010 White Macbooks with El Captian but we are seeing some odd behavior of some imaged machines. It seems like maybe every 15 or 20 Macbook's we image the script fails when resizing the drive and end gives a file system consistency error. When we try to boot into single user mode on those clients ad run an fsck_hfs on the drive we get invalid b-tree node size (3 0) errors and Disk Utility also fails when trying to repair the volume. Once a client has this issue it almost seems impossible to re-image the same machine without getting the same result and error message. Like i said earlier, none of our Yosemite images have this issue. No matter how many new El Capitan images we recreate from scratch we run into this same odd imaging issue. Is there something about El Capitan and the way clonedeploy deploys the image to the drive that is making these clients get these invalid b-tree node size (3 0) errors? Any help would be great as we are at a point where we are putting aside almost every 15th macbook as it will not image. One more note: If we image the machine that has this issue with Yosemite, it is fine and no filesystem errors. But if we try imaging it again with El Capitan after we just imaged it with the Yosemite image, that SAME computer still gives the same "invalid b-tree node size (3 0)".