Posted on 03-31-2014 08:57 AM
Im currently trying to run Casper Imaging from a net boot image but when I choose a configuration and click install, it mounts the CasperShare says preparing for block copy then apparently says cleaning up after block copy after only like 3 seconds (10GB image file) and an error message appears. “An exception of class IOSException was not handled. The application must shut down. Exception Error Number: 103”
Any assistance with this would be appreciated.
Posted on 03-31-2014 09:10 AM
@FDA double check your Casper Imaging is matching up to what you are running on your JSS or copy over a fresh version of the application to the NBI.
Posted on 03-31-2014 09:15 AM
Thanks for the response, both the JSS and Casper Imaging versions are 9.3
Posted on 03-31-2014 10:02 AM
I've seen similar behavior when diskless NetBoot wasn't working correctly. Not sure about exact error code.
Posted on 03-31-2014 10:28 AM
To echo CGundersen, this seems to be related to the diskless NetBoot service. The handful of times I've ever seen this error I've toggled the NetBoot service in the Server app, and then things are fine afterwards. I unfortunately don't know the exact cause, but bouncing the service helps.
Posted on 04-01-2014 05:12 AM
Since 9.3 I have also seen this, in our enterprise Netboot is not supported so we use USB boot drives, I get the failure when CI is trying to configure the items set to install on reboot. If I remove these actions CI does not crash. I do need to get this figured as there are thing we need to do that need to install or configure on reboot.
Posted on 04-01-2014 07:54 AM
Modifying rc.netboot fixed the issue
Posted on 04-01-2014 12:18 PM
FWIW, I'm not seeing this.. Nor have I modified the rc.netboot.. Just used the 32MB kernel cache script.
Posted on 04-01-2014 01:27 PM
give this a try
http://www.macos.utah.edu/documentation/administration/setup_netboot_service_on_mac_os_x_10.6.x_client.x_client/setup_netboot_service_on_mac_os_x_10.6.x_client-diskless_netboot.html
Posted on 10-22-2015 09:30 AM
I do not know if this is what did it, but I am no longer receiving this error message after upgrading to 9.81
Posted on 10-26-2015 07:15 AM
@carmand did you update Casper Imaging to 9.81 too?