Recently, I decided to try to use the Linux client for Ghost outside of the provided ThinStation system. Some newer hardware is either not supported at all or not supported well. A Ghost image that, when using a home brewed WinPE 3.0-based CD takes ~10 minutes to pull, took 70+ minutes in ThinStation on one particular piece of hardware (designed in 2005).
At first, I got "Internal Error 8032" "An internal inconsistency has been detected" but also in my attempts got error 36000 once (I only saw it once and didn't record its message). This message is deceptive and frustrating.
Examining all Linux binaries in the ghost.zip, I see they are all UPX-compressed. When I attempt to extract ghost with upx-ucl, I see "CantUnpackException: header corrupted 2". upx-nrv is no better and attempting to list is less informative. The others don't display this behavior. Researching this issue across the web, I find that it's common for malware as an analysis countermeasure.
#8032 appears to actually be a copy protection measure. The Linux distribution in question used a module called ramzswap which allows the kernel to compress some unneeded data in memory as a part of the swap system (uncompressed RAM, ramzswap, normal swap on disk). Disabling the ramzswap module solves this issue. As root, 'swapoff -a' then 'rmmod ramzswap'.
This should not have been "An internal inconsistency has been detected" but rather stating that something about the system was determined to be incompatible, preferably with hints somewhere as to what is incompatible (even if it's buried in documentation/knowledge base that can be searched quickly)
Distribution in question (name/version): Tiny Core Linux 3.6
I'll post back here with the link to the TCL forum post when I finish it. Kudos to filoo95 at http://forum.tinycorelinux.net/index.php?topic=6942.msg40514#msg40514 for stumbling on the solution.