Ghost Solution Suite

 View Only
  • 1.  Ghost image file corruption

    Posted Jan 01, 2012 04:10 PM

    Hello,

     

    I made an image using Ghost 11.5 before rebuilding the OS for a customer. Now that the computer is rebuilt I'm trying to use Ghost Explorer (also 11.5) to extract just the portions of data that need to be brought back over. I have done this many times before but this time I'm getting an error.

     

    When I open the .GHO file stored on my USB External Drive it's asking me to select the last file in the image span. The image is not spanned, it's all 1 file. Origionally the pop-up wanted a .GHS or a .0 file. I've run the GhostFix.exe program and since that it now wants another .GHO file. If I select the origional image than the pop-up will happen again. If I choose cancel than it tells me that the image file may be corrupted.

     

    I've also tried launching Ghost explorer with the -CRCIGNORE and -IGNOREINDEX options to no avail. I even ran chkdsk on my external drive to see if perhaps the backup drive had become corrupted but no issues were found.

     

    Other Information:

    -Backed up partition is NTFS

    -Was backed up using the Ghost boot CD

    -No errors were given during the backup process

     

    I'm hoping there is a way to tell Ghost Explorer not to ask for any other files and just open it. Otherwise I may be in some hot water :-O

     

    Thanks in advance!



  • 2.  RE: Ghost image file corruption

    Posted Jan 02, 2012 09:52 AM

    Update:

     

    I also want to mention that the format of my external USB drive is NTFS in case that matters

     

    On the advice in another thread I tried opening the image with the trialware version of GSS2.5 and got the same error... I guess I don't know it by that name but I think that might even be the same version I actually have heh

     

    I've also tried restoring the disk from the image that I created. It accepts the image and starts the restore but at 17% it throws the following error even with the CRC ignore flag on:

     

    Abort 27076, Corrupt Packet Length in compressed image file

     

    It asks me to save the error message file but I can find any where that it will allow me to save the file. The PC doesn't have a floppy disk drive and it doesn't appear to have assigned letters to the other drives. It also asks me to run an integrity check on the image which I did. That also makes it to 17% and throws 2 error messages

     

    General Protection Fault at eip=51d65f; flags=3012

    eax=0112e8a4...

    ... error=0000

    Memory allocation error

    Can not load COMMAND, system haulted

    and

    Page Fault at cr2=10000020 in RMCB at eip=bb211; flags=3002

    ...

    ... error=0004

    Memory allocation error

    Can not load COMMAND, system haulted

     

    I can post the full error if anyone thinks that would be helpful but it's just a bunch of hex values that I think are related to the exact position in the image where the problem is. I forgot to mention in my other post that the image was created using 'fast' compression. I'm thinking this new information might mean I'm boned but please let me know if there's anything else I can try.



  • 3.  RE: Ghost image file corruption

    Posted Jan 03, 2012 03:55 AM

    Can you access the files in the GHO image using Ghost Explorer?  That may allow you to recover data in the likely event that your image is hosed.

    You did not mention which make of USB drive you used for the imaging process. It is a fact that many users have had similar problems with "cheap" usb drives so if you are using one of those, this could be the cause.

    My experience of using higher quality USB drives such as WD has been very positive.

    Incidentally, you could also try copying your GHO file to another hard disk, whether local or external USB and see if that makes any difference to the recovery process. If the copy operation fails, then at least you will know that there is a hard error in the file. At this point, if you have tried using Ghost Explorer to see if any data can be recovered, you can then try CHKDSK /F to determine whether any sector errors can be fixed.