Novell is now a part of Micro Focus

The Mystery of the Internal Segmentation Fault

Novell Cool Solutions: Trench
By Scott Campbell

Digg This - Slashdot This

Posted: 11 Sep 2003

I just went through the process of getting ZEN to image some Evo D530 SFF machines with XPP installed and thought that some might benefit from my experience.

When attempting to image these machines I was getting a "Internal Segmentation Fault" which appears to be fairly notorious with ZEN Imaging. I battled with Windows to delete the last file ZEN displayed but sadly ZEN would still produce the error on another file. I tried ZEN3.2, 3.2sp2, 4.0, 4.0sp1, 4.01 all with the same results.

It turns out that HP's images include a file in the windows\system32\drivers directory that has a very long filename (>200 characters) with some dubious characters in it (namely '(' ')' ), the file is hidden and was about 2KB, once I deleted this file I was able to happily take an image of the machine. ZEN was showing the file prior to reading this hidden file as it was obviously dying when attempting to read the filename.

The filename is different for each model and possibly machine but starts with HP and has an extension of .mrk

I guess the moral of the story is, when you get the Internal Segmentation Fault, look for a file in that directory with potentially invalid characters or an exceptionally long filename.

Additional Suggestions

CJ Goggin

If you're running Windows XP, right clicking on My Computer, and turning off system restore (apply, ok) and repeating to turn system restore back on PRIOR to saving the image to the server seems to help eliminate this error when restoring the image to a machine.

Also, I've seen it crop up on a single machine in a room that had already been multicast with the same image earlier. Turned out that the second RAM module had a flaw. Removing the affected module allowed the machine to take the image.

Haakon Trodal

I did have the same error message, but there was a different solution for me. Using ZEN4 and W2K, the problem turned out to be the cluster size of the partition. Since we converted the system partition from FAT32 to NTFS, the default cluster size will be 512. That means you will have to create the partition with the following command: "img pc1 NTFS C1"

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates