Ghost Solution Suite

     I recently imaged a PC and the ghosting goes ok until it finishes and tries to restart.  It then comes up into the Vista Repair screen and is unable to repair.  I have ghosted to the smae machine before with no issues.  It is a new image from a PC with the exact same hardware.  Here are some of the details of the system:
Dell Dimesion 9200
2.4 Duo
2 Gig Ram
250 Gig Hard drive
Vista business Operating System
Sata Drive

Image is of the same system.  Has about 215 GB of info on it.
I have set all the switches to handle the SATA drive, i.e. -noide, etc.
I tried to run the same task that I used in the past and received an error that said it required the -ntexact switch.  I re-ran it with that in place and got this result.  The log file states that the cloning was successful, but that on reboot the client timed out.  I just re-formated the hard drive and reinstalled Vista and then tried to Ghost.  Same result. 

If you need more info or have any info that could help please post.  I am ready to pull my hair out.  We have 10 systems that are the same and this is the only 1 I have had a problem Ghosting to.  All the Hardware diagnostics show no hardware malfunctions.

Rich Gain

I noticed in some other posts that the error message might help.  This is the error message that I received the first time I tried and failed to Ghost.  The recent attempts timed out and gave no error message.

*********************************
Date   : Wed May 30 19:10:22 2007
Error Number: (25058)
Message: Unable to locate enough contiguous free space to load run.
Increase the destination partition size or
run Ghost with -NTEXACT switch.

Version: 11.0.1.1533 (Apr 19 2007, Build=1533)
OS Version: DOS v7.10
Command line arguments: -fni -ffx -noide -nousb -clone,dst=1,mode=restore,src=@MCJESTERMAIN2push38 -batch -sgb -jm=U -sgt
Active Switches :
      AutoName
PathName            : 9453 Unnamed MFT Table entryOOBEDONE.FLG
DumpFile            : @MCJESTERMAIN2PUSH38
DumpPos             : 349319423
FlagImplode         : 0
FlagExplode         : 2

CloneSrc            : @MCJESTERMAIN2PUSH38
BatchPartSrc        : 0
BatchPartMSrc       :

CloneDst            : 1
BatchPartDst        : 0

Operation Details :
 Total size.........195357
 MB copied..........627
 MB remaining.......194730
 Percent complete...0%
 Speed..............1254 MB/min
 Time elapsed.......0:30  
 Time remaining.....2:35:04

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

Call Stack
 0x00397a4c
 0x0009cd91
 0x0009c5cc
 0x0009bca7
 0x0009d872
 0x0004853c
 0x0005236f
 0x000517d0
 0x0004fc67
 0x0004e64a
 0x0004d81d
 0x000173e9
 0x000197d5
 0x000c9984
 0x000c92db
 0x000c9171
 0x000c722c
 0x0000220f
 0x00002374
 0x00005057
 0x00003f2f
 0x003a0c78
End Call Stack


Start heap available: 2135293952
Cur   heap available: 2065891328
Total Memory:         2144665600

Allocated
  1024 DpmiDjgpp.cpp:56
 33504 ghost.cpp:1396
    48 DiskDriveAccessExInt13.cpp:139
Free
    64 GetDriveType.cpp:111
    80 DiskDriveAccessExInt13.cpp:102
   512 DiskDriveAccessExInt13.cpp:223
 32768 MsdosFile.cpp:368

Fat details:
 SRC:
 FatType..........16
 firstSector.......63
 ClusterSize......2048
 clusters.........24026
 root_next_avail..0
 data_next_avail..0
 dir_sector.......0
 root_sector......189
 data_sector......221
 FAT_sector.......0
 DST:
 FatType..........16
 firstSector.......63
 ClusterSize......2048
 clusters.........24026
 root_next_avail..2
 data_next_avail..3520
 dir_sector.......196
 root_sector......189
 data_sector......221
 FAT_sector.......14

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

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

      ---------------------------------------------------
      Cluster Allocation Map
      ---------------------------------------------------
      Start: 0 Length: 259819 Next: 259819
                     Gap: 2325
      Start: 262144 Length: 2368 Next: 264512
                     Gap: 99908
      Start: 364420 Length: 528594 Next: 893014
                     Gap: 102776
      Start: 995790 Length: 4017 Next: 999807
                     Gap: 128
      Start: 999935 Length: 0 Next: 999935


   =======================================================
   =======================================================
   NTFS volume 1:
   ----------------
   initialised..............1
   read cached..............N
   Selective caching........N
   flags....................Volume OK
   drive....................0x00
   part order...............1
   version..................0x0400
   volsize..................488179711
   blocksize................512
   clusterfactor............8
   clustersize..............4096
   mftrecordsize............1024
   indexrecordsize..........4096
   indexclustperrecord......1
   bootSectorCopyOffset.....488179711
   pagefileSys..............-1
   bootIni..................-1
   volumeLabel..............[]
   sectorsInUse.............26403720
   totalNonCopiedBytes......0
   bytesToCopy..............0
   bitmapClusters...........1863
   bitmapUsedBytes..........7627808
   estimatedClusters........1863
   estimatedUsedBytes.......7627808
   clustersizeShift.........12
   blocksizeShift...........9
   mftrecordsizeShift.......10
   indexrecordsizeShift.....12
   totalRootMftRecs.........0
   clustermap failover......N
   Boot sector details
      name....................[NTFS    ]
      blocksize...............512
      clusterfactor...........8
      reservedSectorsUnused...0
      mediaType...............0xf8
      secPerTrack.............63
      numHeads................255
      hiddenSectors...........98304
      volsize.................488179711
      mftcluster..............786432
      mftmirrorcluster........30511231
      clustersPerMFTRecord....246
      clustersPerIndexBuffer..1

      ---------------------------------------------------
      Cluster Allocation Map
      ---------------------------------------------------
      Start: 61022463 Length: 0 Next: 61022463


   =======================================================

Disk Info :
 remote.............0
 drive..............0
 sectorsUsedCount.......488276039
 estimatedUsedCount.....400092006
 numPartitions..............3
 Version............1101

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    0  de No         63      96327      96390      14261 No
 1  1    0   7 No      98304   21106688   21204992    7200096 Yes
 2  2    1   7 No   21204992  467073024  488278016  441060672 Yes

Disk Info :
 remote.............0
 drive..............0
 sectorsUsedCount.......488278016
 estimatedUsedCount.....0
 numPartitions..............3
 Version............0

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    0  de No         63      96327      96390      14261 No
 1  1    0   7 No      98304    7999488    8097792    7200096 Yes
 2  2    1   7 No    8097792  480180224  488278016  441060672 Yes

Fixed Drives

Drive 128
Int 13h
Total Sectors            16434495
Bytes per Sector         512
MB                       8024
Cylinders                1023
Heads                    255
Sectors per Track        63
Successful IO Count      0

Extended Int 13h (Active)
Total Sectors            488281250
Bytes per Sector         512
MB                       238418
Successful IO Count      25928

Floppy Drives

Drive 0
Int 13h (Active)
Total Sectors            2880
Bytes per Sector         512
MB                       1
Cylinders                80
Heads                    2
Sectors per Track        18
Successful IO Count      1

Could I get some help with this?  I have had no reply in a week.  I have spent about 30 hours trying to resolve this.  I want to make sure this is not a Ghost issue so I can contact Dell.

Rich Gain
Jester's Playhouse

Sorry, I have overlooked that too :-)

I got a little confused with the process now, if I understand this correctly, if you clone without -ntexact switch it comes up with the error, but if you use -ntexact, cloning completes successfully but machine does not boot to Vista and you cannot repair that either. Is that correct?


At which step does client fail, after cloning you may do SID changes or conifig changes. Does any of them work successfully? It will be very helpful to see the task scenario (just right-click on the task and select task scenario).

If your task does not have any of them (in case if this is a syspreped image) only other thing I can think of is updating disk signatures after clonning. If so, could you try -fdsp switch with Ghost? This will force not to change the disk signatures.

Krish

Hi,

Thanks for the info, this certainly helps.

Looks like this is a straight cloning (no SID change, no Configuration).

In the first post you mentioned that you have other machines that works. Do they use the same image?

If not the same image, do they have the same structure (Diagnostic partition and two NTFS partitions)? I am trying to see if there is any confusion with the diagnostic partition.

Could you try the restore with -fdsp switch? Vista is sensitive to the disk signatures and Ghost update them after cloning. Just to make sure if there is no issue there.

Krish

Krish,
Tried it witht the new switch.  Same result.  I want to reinterate that I ghosted fine until the updates were posted and think maybe this has to do with changes in the updates.  I am making a new image and will try again, but I think this might have something to do with the updates.

Rich Gain

Hi Rich,

Please let us know what happens with the new image, in the mean time I will see if I can re-produce the issue here.

Krish

Ghosted with new image.  Removed -ntexact tag and -fdsp tag and it ghosted fine until it restarted.  It looks like all the info is there but windows cannot find its operating system.  I saw a previous post where the pointers where not starting the machine to the right partition.  Could this be the issue?  I unistalled Ghost SS 2.0.1 and reinstalled 2.0 and still had the same issue.  I am completely frustrated and would really like to find out what the issue is.  Is is a hardware problem, a software problem or a Vista problem?  Please give me some advice.  All hardware diagnostics that I have run have concluded that there is no problems with the hardware.

I looked at the repair log from windows and it says that a patch is preventing the system from starting.  The last test performed by vista was a registry hives test which it never finished.  I do not know if this helps in any way.

I did a little more digging.  Windows can attempt to start with Safe Mode, but gets hung up on crcdisk.sys and restarts.  I tried multiple safe mode restarts and it always gets hung up at this driver.

Hi Rich,

Since you can start to boot from hard disk, the partition should be active. I don't think that's the problem.

When I did a search on crcdisk.sys in the web, there were many hits from the users who faced the same issue after installing Vista.

There were multiple reasons, but most common looks like old drivers. Vista is trying to install an older driver in case if you had a previous installation. Some others had found it to be a faulty device. There were others who simply added another device after install before first boot.

Do you restore this image to the same machine? If not, if it is the same model? If it is the same model, could you see the BIOS settings for SATA drive is same in both systems?

You have three partitions, I presume vista is installed in partition 2, and 3 is a data partition. Do you have multiple OSs in these partitions?

Krish

Problem solved.  Thanks for all the help Krish.  Early on in the problem, a Dell Support rep told me to change the RAID settings in the Bios.  I changed it back and had no problems.  I think that there is still a problem with the 2.0.1 update because that is what started the whole incident that caused me to change the Bios in the first place.  I am going to stick to 2.0 for now.

Hi,

Good to hear it :-)

However, still I am not sure if the problem was related to 2.01, since the first issue you got suggesting to use -ntexact switch could happen when you clone a relatively full partition. By any chance did you change the BIOS settings before you try with -ntexact?

There are bug fixes in 2.01, so it is a good idea to try it if possible. I know that you have to get on with your work rather than trying these things out though :-)

Krish

The -ntexact switch was used before the change to the Bios.  After the -ntexact ghosting, I could not restart the computer.  I wish I would of thought to look at safe mode back then.  Again, thanks for the help and I will wait until the next update to give it a try.

Richard Gain
Jester's Playhouse