Ghost Solution Suite

When using either the Ghost v8.0 console or CLI to create an image, ghost is creating many, many span files. I am trying to pull an (sysprepped) image from a Dell Optiplex 360.  The hard drive (80GB) was formatted into two partitions (C: drive 19.53GB, 5.7GB used, 13.83GB free and a D:drive 60.47GB free). Both partitions are NTFS and were defragmented.  The C: drive was imaged with Windows XP SP2 and basic software (MS Office, WinZip, McAfee). D: drive is bare of any files. In the past when pulling images we get a 2GB gho file and anywhere from one to three ghs files, depending on how full the C: drive is. In this case, I am watching my network drive fill up with many, many span files. At last count I stopped the image process at 17 ghs files.  I suspect the image process would continue until I get 80GB worth of ghs files, almost as if I was pulling a sector-based image.

In the past when this happened we had issues with the NIC and network card settings. Per our network install all NICs and switches are set to 100 Full. In order to image we need to be at 100 auto. If not then this is where we start seeing too many ghs files being created. I have verified my switch and NIC are at 100 Auto.

We have not made any setting changes to Ghost that would create sector-based vs file-based images.  I'm not sure how you would make that change during the Ghost process (if we even could with this version of Ghost). Is there any way using the CLI to ensure I am pulling a file-based image? I created an image of an Optiplex 360 about 4 months ago with a 2GB gho file, two 2GB ghs file and one 420MB ghs file. However, we are not happy with the image and want another image.

Please note that we not using Ghost Solutions Suite. We just attended training and are in the process of purchasing v2.5.

Any thoughts out there?
Thanks,
Ken

Ken,

By default, Ghost will make a file-based image, as opposed to a sector-based one. One thing that could prompt a sector-based image would be if the drive ws encrypted and Ghost did not have proper access to the file system. Is the drive encrypted? Additionally, you can verify whether or not the image is file-based or sector-based by trying to open it with Ghost Explorer (sector-based images are not explorable); be warned, however, that an image so large with take a long time to load and be taxing on the virtual memory.

If you are in the process of purchasing GSS 2.5, that is excellent. Installing this should restore any defaults.

Randall - thank you for responding.

That is what we were during our training class last week. I am not letting the ghost process fininsh (80GB of ghs files will fill my server up pretty quickly), so after killing the ghost session I delete all of the gho/ghs files.  I suspose I could try again and look at the gho file, but I don't have ghost console installed yet.  I do have a licensed copy of GSS v2.0 I am trying to install (don't ask why we haven't used that).  Somehow I really don't think I am getting sector-based images, though.  Like I said, this creating of many ghs files has happened to us in the past, usually correctable by changing network settings.

To answer your one question, no the drive is not encrypted.

The issue may be that Ghost is not able to read the hard drive correctly and is forced to do a sector-by-sector. You could try adding these switches:

-FNI -FFX -NOIDE -NOUSB

These drive geometry switches allow Ghost better access to the drive. Pleas note, however, that the cause of this could be that the version of Ghost you are using doesn't adequately support newer drive technology. Trying with GSS 2 or GSS 2.5 would be ideal.

Thanks Randall.  I will give these switches a try.  I am also trying to get GSS 2 installed in parallel.