Ghost Solution Suite

 View Only
  • 1.  Decpmpression error

    Posted Sep 21, 2010 11:45 AM

    Hello,

    We’ve been using Ghost 11.5 to backup and restore installations in our College for a few years and we rarely had any decompression errors while restoring.

    Usually running windows scandisk and defrag would find the culprit and solve the issue.

    But now, we are currently confronted with an increasing amount of corrupted images to the point where we are doing an integrity check as soon as the imaging task is complete. And most of the time, we get decompression errors (19225).

    We ran different types of disk, memory, motherboard verification software on the model computers and no errors were detected.

    As far as I know, switches and routers are working properly.

    The model workstations are currently running WinXP Pro and don’t have a 3Com NIC.

    Also tried using a lower level of compression with no luck.

    We have corrupted files using either WinPE or PC-DOS.

    All files are stored on a SAN.

    Current version of the Ghost console: 11.5.0.2113

    Any idea on what can cause this problem to occur?

    Thanks



  • 2.  RE: Decpmpression error

    Posted Sep 21, 2010 01:35 PM

    Hello,

    I would advise running the updates, which will take you to version 11.5.1.2266. The base build had quite a few defects that were resolved in the updates. Either run LiveUpdates, or apply via the download. I have sent a PM with download info. Try creating the corrupted images again.

     

    Thank you,

    Randy



  • 3.  RE: Decpmpression error

    Posted Sep 21, 2010 04:29 PM

    Thanks for the quick reply Randy!

    I’ll forward the information to the tech responsible for the servers and hope he can update asap.

    I guess we’ll have to update our Ghost CD's to take into account the new versions of the Ghost client.

    I’ll keep this thread updated.

    Thanks again.



  • 4.  RE: Decpmpression error

    Posted Oct 01, 2010 05:20 PM

    Hello Randy,

    I have good news and bad news.

    The good news is that our console is updated to 11.5.1.2266.

    The bad news is during the Live Update process, something went wrong and the update failed leaving us with a less than functional Ghost Console.

    We had to download and install the updated version using the download info you sent me.

    Unfortunately, we lost all of our configuration files, tasks and computer groups.

    Unless there’s an easy way to restore/recover what has been lost, I won’t be able to test anything for a while.

    Edit : We’ve restored the backup Ghost Database following the steps mentioned in your post of January 25th (https://www-secure.symantec.com/connect/fr/articles/after-updating-ghost-version-11512266-your-ghost-console-no-longer-has-any-clients-or-machi) .

    Eerything is back.

    Edit 2 : Well, now the Default folder is getting flooded with dozen of duplicates of existing computers until the console is out of licenses.

    Even if I delete all of them, they simply reappear a few seconds later even after rebooter the server.

    Any idea of what might be causing this?

    Thanks

    Edit 3 : I just found this in the forums.

    https://www-secure.symantec.com/connect/fr/forums/after-applying-ghost-solution-suite-25-live-update-5-build-2266-clients-begin-duplicate-thems

    Would it be possible to have access to this fix please.



  • 5.  RE: Decpmpression error

    Posted Nov 10, 2010 10:55 AM

    Hello Randy,

    We’ve contacted technical support regarding the duplicate client issue and applied the fix yesterday.

    Since then, 4 images were created and 3 of them are corrupted (decompression error).

    It seems updating to the latest build 2266 with the duplicate client fix does not solve our problem.

    I found many posts on the forums regarding this problem and no apparent solution have been provided besides using fast compression.

    Currently, we are far from being at optimal efficiency when we need to pull 3 to 7 times data from a model computer before having an uncorrupted image. 

    Is there anything else we can try?