Ghost Solution Suite

 View Only
  • 1.  GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 28, 2010 01:24 PM
    We have several laptops with bad spots on the disk.
    if we do a ghost image without -fro, we get a fatal error at about 45% complete. the error is as follows:

    *********************************
    Date   : Wed Jul 07 18:44:32 2010
    Error Number: (29003)
    Message: Bad block(s) encountered on read: Win32 error: (0x0000045d)
    The request could not be performed because of an I/O device error.
    , device:F:\, 8 sectors starting from absolute sector 36326656
    Version: 11.5.0.2113 (Apr 22 2008, Build=2113)
    OS Version: Microsoft Windows XP Professional  (Build 2600)
    Command line arguments: -span -auto -cns
    Active Switches :
           AutoName
    PathName            : 17 Unnamed MFT Table entry
    DumpFile            : Y:\marijana\201007_f.006
    DumpPos             : 15011688121
    Last LFO Buffersize : 65536
    Last LFO Path       :
      Full Path         : Y:\marijana\201007_f.006
      Drive Letter      : Y:\
    Last LFO Filesystem : Native
    Last LFO Error      : Win32 error: (0x00000002)
    The system cannot find the file specified.

    ------------------------------------------------------
    if we run with the -fro switch, the  image completes, we can open it and extract individual files from the image, but if we try to restore the image to a new disk it returns almost immediately with "Corrupt ID header encountered" as follows"

    *********************************
    Date   : Thu Jul 08 17:04:42 2010
    Error Number: (27074)
    Message: Corrupt ID header encountered
    Version: 11.5.0.2113 (Apr 22 2008, Build=2113)
    OS Version: Microsoft Windows XP Professional  (Build 2600)
    Command line arguments: -span -auto -cns -bfc -fro
    Active Switches :
           AutoName
    PathName            : 5 .
    DumpFile            : Y:\old disk\20100707_f.GHO
    DumpPos             : 38835815
    Last LFO Buffersize : 65536
    Last LFO Path       :
      Full Path         : Y:\old disk\20100707_f.GHO
      Drive Letter      : Y:\
    Last LFO Filesystem : Native
    FlagImplode         : 0
    FlagExplode         : 2
    Operation Details :
      Total size.........39627
      MB copied..........148
      MB remaining.......39479
      Percent complete...0%
      Speed..............986 MB/min
      Time elapsed.......0:09  
      Time remaining.....40:02  


    ------------------------------------------------------------------
    The question is:
    if the image completes and we can read it with ghostexplorer, why can't we restore the image to a new disk?

    thanks,
    Ole Jensen.


  • 2.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 28, 2010 01:43 PM
    Hi,

    If the image file is present in the Ghost server try the following,

    To run the integrity check from Windows

    1. Run Ghost32.exe. By default this is located at :

      C:\Program Files\Symantec\Ghost\Ghost32.exe.

    2. Choose Local > Check > Image File.
    3. Browse to the image file and click Open.
    4. Choose Yes to proceed with the integrity check.

    Eventhough the image completes and you can read it with ghostexplorer we need to make sure whether the image file is good. If the image fails the integrity check you need to create a new image.

    Regards,

    Prasanna Rajagopalan



  • 3.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 28, 2010 01:52 PM
    Additionally, attempt to open it in the Ghost Explorer and extract a file. The integrity check and this are the best tests for viability of an image. And please note the -FRO switch is telling Ghost to ignore bad sectors. You may want to run disk diagnostics on the source disk, like CHKDSK.


    Thank you,

    Randy


  • 4.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 28, 2010 03:49 PM
    Prasanna,
    the integrity check says the image is bad.
    " Ghost has detected corruption in the image file. "
    however, Ghost explorer opens, reads, extracts files.

    If you create an image using -fro and it does not report a problem, then the image should be good.
    it should "Force Ghost to continue even if bad blocks exist in the source".
    it should simply ignore what it can't read and produce a valid image of what is left.
    if the bad part is in a file, then the file may be truncated.
    if the bad part is a folder structure then the folder and all affected files may be truncated.
    in any case, it should continue and produce an image that is readable.
    since the errors occur at the 45% (of 60GB) there should be some useable data in the image.
    the restore reports a total failure in less than 10 seconds.

    redoing the image backup produces the same result.

    running chkdsk exhaustively ( -f -r) reports that there are bad sectors on the disk, but that the structure is intact. chkdsk terminates without errors.

    thanks for your assistance,
    Ole Jensen.


  • 5.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 28, 2010 04:02 PM
    Randy,
    thanks for your response.
    I think I covered most of your response in my reply to Prasanna. to save bandwidth, I won't copy that info into this message.

    -fro actually says to continue even if errors exist in the source, it doesn't specifically say ignore errors.
    ignoring errors could lead to an unstable structure in the image, but continuing should truncate the file or the folder and "continue".

    chkdsk was run prior to the image backup.
    it indicates that it found errors, but corrected them and completed successfully.
    Chkdsk results for the disk follow:

    X:\BIN>chkdsk f: /f /r
    The type of the file system is NTFS.
    Volume label is DataPart_D.

    CHKDSK is verifying files (stage 1 of 5)...
    File verification completed.
    CHKDSK is verifying indexes (stage 2 of 5)...
    Index verification completed.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
    Security descriptor verification completed.
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    Windows replaced bad clusters in file 19777
    of name \data\OLDDDR~1\maja\BOOKSP~1\DEITEL~1.RAR.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    Free space verification is complete.
    Adding 1 bad clusters to the Bad Clusters File.
    Correcting errors in the Volume Bitmap.
    Windows has made corrections to the file system.
      47423879 KB total disk space.
      37240812 KB in 49441 files.
         19224 KB in 10550 indexes.
          2628 KB in bad sectors.
        196803 KB in use by the system.
         65536 KB occupied by the log file.
       9964412 KB available on disk.
          4096 bytes in each allocation unit.
      11855969 total allocation units on disk.
       2491103 allocation units available on disk.



    thanks,
    Ole Jensen.


  • 6.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 29, 2010 08:45 AM
    Please go through this forum thread and check if your issue can be resolved.

    https://www-secure.symantec.com/connect/forums/cant-reimage-or-extract-files-ghost-image-help


  • 7.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 29, 2010 09:25 AM
    One thing that can help is to run a boot time defragmentation on the drive with a utility that can do this, such as Diskeeper or PageDefrag. At least one of those will have an evaluation copy that is free to use. I find that it is usually necessary to run this 2-3 times. Please note that the Windows Defragmentation Utility will not do what we need; this will defragment the Master File Table (MFT). MFT fragmentation can prevent us from getting a viable image.

    Thank you,

    Randy


  • 8.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 29, 2010 03:05 PM
    Gkg - it took about 4 hours to compile a new file. it reported no problems, but the resulting single span file (72GB) has the same problem as the original 35 span file (2GB each).
    there was some other interesting information in the thread, but it didn't resolve the problem.

    any other thoughts?

    thanks,
    Ole Jensen


  • 9.  RE: GSS2.5.1 - ghost32 with -fro (on disk with errors) creates unrestorable image

    Posted Jul 29, 2010 03:08 PM
    Randy,
    I checked the fragmentation and there were only 2 fragments in the mft (46% used).
    I don't think that is the answer.

    Any other thoughts?

    thanks,
    Ole Jensen.