Symantec GHOST IMAGING FOUNDATION 7.1 - V1.0 Manual page 174

174 Troubleshooting
Ghost.exe problems
Errors when using Ghost with NTFS files (continued)
Table E-2
Error message
Error 25058 - "Unable to
locate enough contiguous
free space to load run.
Increase the destination
partition size or run Ghost
with -NTC- switch."
Error 24010 - "Encountered
BAD used MFT Record - run
CHKDSK"
Error 25030 -
"NTFSGetClusterCount
failed"
Description
This error occurs when Ghost cannot find a large enough
free space to store a section of an NTFS file. There may be
enough total free space in smaller allocations scattered
about the volume to store the contents of the file, but due
to the fact that Ghost does not attempt to break up
contiguous sections of files as they are cloned, it produces
this error. When cloning volumes with minimal free space
and containing large files comprised of a small number of
contiguous sections, the operation will be particularly
vulnerable to this error.
Possible workarounds include the following:
Defragmenting the source drive before cloning or
creating an image.
Using the -ntc- switch, which lets Ghost attempt to
allocate disk clusters at or near their original location
on the source volume. This minimizes the amount of
disruption to the cluster mappings and the subsequent
space required to store the mappings.
This error can occur when cloning or creating an image
from a source NTFS volume. It may be caused by either
corruption or by a bad sector on the drive.
Possible workarounds include the following:
If the file system is corrupted, running CHKDSK /F on
the NTFS volume before attempting to clone it again will
pick this up.
If the problem is due to a bad sector, run Ghost with the
-fro switch to force Ghost to read sectors one-by-one if
it detects a bad sector during a read of a range of bad
sectors.
This error can occur when Ghost is cloning or creating an
image of an NTFS volume. It is most likely to have been
caused by file system corruption.
A possible workaround is to do the following:
If this is a file system corruption, run CHKDSK /F on the
volume.