Ghost Solution Suite

Dear all,

I have some strange problems when i try to push an image to a client with Ghost Solution Suite 2.5.x (latest version / client is a Lenovo T410S BIOS uptodate, compatibility mode on).

I receive the following random errors:

Message: Image file contains corrupt data run

Message: Decompression error

I add some extra info about the progress....

Step 0 - Install + Update Windows XP

Step 1 - I created an image of the WIndows XP installation. Succesfull all the time.

Step 2 - After the image was created i pushed the image back and i updated the installation. (version 1) Succesfull all the time. 

Step 3 - I create again an image, Succesfull all the time. 

Step 4 - When i now push the image back again, i receive the random erros mentioned above. The errors are even random during the push back process.

Summary: Every time I'm doing the 2e push, it fails. I've repeated Step 0 a lot of times. Even deleted and re-created the partitions. Windows detects 0 erros on the partition, and the laptop disk is also OK.

Anyone got any suggestions what i can try or how to fix this?

Some info of the logfile:

*********************************
Date   : Thu Dec  2 09:12:35 2010
Error Number: (27100)
Message: Image file contains corrupt data run
Version: 11.5.1.2266 (Dec 24 2009, Build=2266)
OS Version: DOS v7.10
Command line arguments: -ntc- -clone,dst=1,mode=restore,src=@MCFHSSRV0001push976 -batch -sgb -jaddr=137.120.13.173 -sgt
Active Switches :
       AutoName
PathName            : 552 driver.cab
DumpFile            : @MCFHSSRV0001PUSH976
DumpPos             : 104161836
FlagImplode         : 0
FlagExplode         : 2

CloneSrc            : @MCFHSSRV0001PUSH976
BatchPartSrc        : 0
BatchPartMSrc       :

CloneDst            : 1
BatchPartDst        : 0

Operation Details :
  Total size.........6133
  MB copied..........173
  MB remaining.......5960
  Percent complete...2%
  Speed..............1038 MB/min
  Time elapsed.......0:10  
  Time remaining.....5:44  

Program Call Stack
AbortLog
Generic_Abort
loadAttributes
loadMFTRec
loadMFT
loadVol
LoadNTFSPartition
ProcessNTFSPartition
CopyPartition
ProcessAllPartitions
CopyAllPartitions
CopyFileToDisk
CopyMainline
AttemptOperation
sub_main
main

Call Stack
  0x0051099a
  0x000f001f
  0x000ef6bc
  0x000eea86
  0x000f0ad0
  0x00081a6d
  0x00081935
  0x0007ebff
  0x0007c9e2
  0x0007b53d
  0x0002db0e
  0x00030ad0
  0x0012a197
  0x0012922d
  0x0012900c
  0x001277b8
  0x00002884
  0x00002b21
  0x00006b85
  0x0000549c
  0x0052e578
End Call Stack

Start heap available: 2132377600
Cur   heap available: 2062909440
Total Memory:         2146336768

Allocated
   1024 DpmiDjgpp.cpp:56
  33504 ghost.cpp:1511
    528 IdeDmaServerPci.cpp:144
    528 IdeDmaServerPci.cpp:144
    528 IdeDmaServerPci.cpp:144
    528 IdeDmaServerPci.cpp:144
     64 DiskDriveAccessExInt13.cpp:156
Free
     16 MsdosFile.cpp:182
     80 DiskDriveAccessExInt13.cpp:119
    512 DiskDriveAccessInt13.cpp:190

Fat details:

NTFS details:
----------------

NTFS Global Flags:
----------------
  contiguousWrite=0 forceDiskClusterMapping=0
  inhibitCHKDSK=1 ignoreBadLog=0 ignoreCHKDSKBit=0
  enable_cache=0 xfrbuflen=32768
  last_attr_type = 0
  loadExact = 0
  sameSize = 0
----------------
 =======================================================
 NTFS volume 0:
 ----------------
 initialised..............1
 read cached..............N
 Selective caching........N
 flags....................Volume OK
 drive....................0x00
 part order...............1
 version..................0x0400
 volsize..................487967759
 blocksize................512
 clusterfactor............8
 clustersize..............4096
 mftrecordsize............1024
 indexrecordsize..........4096
 indexclustperrecord......1
 bootSectorCopyOffset.....487967759
 pagefileSys..............-1
 bootIni..................3508
 volumeLabel..............[]
 sectorsInUse.............16811552
 totalNonCopiedBytes......0
 bytesToCopy..............0
 bitmapClusters...........1862
 bitmapUsedBytes..........7624504
 estimatedClusters........1862
 estimatedUsedBytes.......7624504
 clustersizeShift.........12
 blocksizeShift...........9
 mftrecordsizeShift.......10
 indexrecordsizeShift.....12
 totalRootMftRecs.........31147
 clustermap failover......N
 Boot sector details
  name....................[NTFS    ]
  blocksize...............512
  clusterfactor...........8
  reservedSectorsUnused...0
  mediaType...............0xf8
  secPerTrack.............63
  numHeads................240
  hiddenSectors...........423360
  volsize.................487967759
  mftcluster..............786432
  mftmirrorcluster........30497984
  clustersPerMFTRecord....246
  clustersPerIndexBuffer..1

Thanks

Can I suggest that you FDISK the target machine hard disk and start with a fully cleaned disk.

Also, as you are using PCDOS, is your image a single file, or multiple files each no more than 2Gb in size?  PCDOS cannot handle files greater than 2Gb.

Since you have GSS 2.5.x, can we verify that your build version is 2266 or 2269. If not, try updating to the latest.

I would also recommend moving from PCDOS to WinPE, as the latter is much more compatible with current hardware and bios releases, and also handles different NIC chipsets better.

While creating image,use -ib switch and use -fdsp while restoring.

Okay, the version is good; I see you are using 11.5.1.2266. I recommend using Windows PE boot media. With that error, you may need to recreate the image, since it is referring to a corrupt data run in the image itself. Since it is a Lenovo machine, definitely create the image using the -IB switch, as mentioned by the previous poster. The proprietary boot track structure of IBM/Lenovo machines means that we need to capture that info in the image.

Thank you,

Randall Newnham