Ghost Solution Suite

 View Only
Back to discussions
Expand all | Collapse all

odd inconsistant problem after GSS 2.0 upgrade

  • 1.  odd inconsistant problem after GSS 2.0 upgrade

    Posted Jun 05, 2007 10:34 AM
    I work for a computer training school, we have previously used Ghost 8.0 with minimal problems. We just upgraded to Ghost 11.01 due to Vista classes starting and needing Vista compatibility. I have been experience a issue I have never seen in the past. After restoring a classroom several PC's will keep rebooting to the safe mode menu screen, the same type of thing that happens  when you restore an image to a PC with different hardware then the one the image was captured on. Normally I would just re-image the PC and that would take care of the problem, but the same thing happens when I do that.
     
    Now the really odd part. While pushing an image to a room yesterday, only one loaded correctly out of 19. So I thought I would try an run a repair on one of the PC's with an XP disk, well it would boot from the CD but would bluesreen before it gave me the options to install XP, Recovery Console, and Repair. This time it froze on the bluescreen instead of doing the looping reboot to the safe mode option screen. All the PC's in this room have swap drives(only one was locked in at the time) So I locked in the 2nd drive and unlocked the first one, pushed the image out with a server task and they all worked except one. This has happened in every room we have since the upgrade while using both the console and server. I have run out of ideas and would appreciate any help or advice. Thank you.


  • 2.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Jun 05, 2007 07:31 PM
    does all your machine have same hardware?
    It is interesting that even windows XP error out with bluescreen.
    Did you try with sysprep option by any chance?


  • 3.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Jun 05, 2007 08:03 PM
    All computers in the rooms have the same hardware: We have a couple P4 D 3.0 GHz rooms, a few P4 3.0GHz rooms, and a few P4 1.6 rooms. We have never had to run sysprep before when we used Ghost 8.0 and never had any problems. I find it odd it blue screens out before even given the chance to run a repair or install a fresh copy of XP when booted from an XP cd post-drop. I still waiting to hear back from a Symantec tech but I though I would ask here in the mean time.


  • 4.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Jun 06, 2007 05:43 PM
    even though it might not be helpful but I'm bit curious what kind of message your are getting when there is a blue screen of death?
     


  • 5.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Jun 06, 2007 06:48 PM
    Something like 0x000000CA and something else about plug n play. Thats all I can remember off the top of my head. I researched the error earlier and didn't find anything helpful. I was able to kill the drive and redrop it and it worked. We loaded 3 rooms today and didn't have any problems. Maybe it's one of those problems that fix themselves, lol.


  • 6.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Jul 28, 2007 03:09 PM
    Wow, I'm sorry to hear you are having this problem, but I'm glad I'm not the only one.  I'm having the same problem.  I have been beating my head against the wall and wasting my time on this for almost a month!  I am getting the exact same error message.  Even trying to boot from a WinXPsp2 install disk and trying to do a repair gives me the same blue screen you mentioned.
    What the heck is going on here?  How could something this major have been missed before they released it?  It only happens with the latest update of GSS2 that I downloaded.  I have ghostcast server v11.0.1.1533 that seems to have the issue.  Someone in another department is using v11.0.0.1502 without problem.

    I've narrowed it down to images that were created using ghostcast server v11.0.1.1533 and that have had sysprep run on them.  The only thing that I can figure, is that ghost is stripping 1 or more important files that sysprep needs to finish the setup process.
    I hope this gets resolved soon, because I really love the newer version instead of the old 8.2 release.
    I've gotten around this problem by reverting back to GSS1.x that had v8.2 ghostcast.



  • 7.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Aug 30, 2007 03:58 PM
    I ran into this problem too, with GSS 2.0x... The latest build craps out any image I deploy, but build 1502 seems to have been ok. Although, build 1502 craps out any images created with GSS 1.x/Ghost 8.3. Luckily, I still had network  boot disc that was still v8.3 and the 8.3 images weren't crapped on. I might have to revert back to GSS 1.x


  • 8.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Aug 30, 2007 05:00 PM
    Hmmm...  So, we have at least 3 people who have taken the time out of their busy schedule to post on the forum about the latest version of Ghost not working at all.  I'm sure there are more that are experiencing this problem that either haven't bothered to use the forum, or just decided to stick with the older version of ghost.
    This is a MAJOR problem.  Why isn't someone from Symantec responding to this thread?


  • 9.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Sep 11, 2007 11:20 AM
    Yes, I agree for this to be a MAJOR problem. It's a shame no one from Symantec Support has responded to us. Reverting back to GSS v1.x seems to be my only long term fix for now, however, I might have to recreate some images. Anyone from Symantec going to help us out??? :(


  • 10.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Oct 09, 2007 07:12 PM
    I ran into this same problem using Ghostcast server 11.01.1.1533 on a Sony Vaio VGN-S240P that has a recovery partition.
     
    It also gives the error after you exit GHOST "ABORT:15004, Boot Record Expected"
     
    When I created an image that does not have Sony's recover partition, the problem went away, but the problem for me is that I need that partition to be in the image (FYI - it is a WinPE recovery image).
     
    When I spoke with Support, they weren't really helpful and said that I needed to buy a service contract (the rep was in denial that this is a bug) even though we just bought 25 lics.
     
    Anyone out there with a solution?


  • 11.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Oct 11, 2007 11:29 AM
    Update: After some testing I found that user:albertsj1 is right on the money with what he found.
     
    The download that was sent to us by electronic means from Symantec had version 11.01.1.1533 and I had the forementioned problems with it.
     
    With the actual media that arrived with the lics, the version is 11.0.0.1502.
     
    I loaded this version (11.0.0.1502) and had to created a new image using it (the image created  11.01.1.1533 by still gave the same error with 11.0.0.1502).
     
    This solved the problem!
     
    There is without a doubt a bug with the download version 11.01.1.1533 version of Ghost server and it's client that is being distributed.
     
    Thanks again albertsj1 !


    Message Edited by MRAY on 10-11-2007 08:30 AM


  • 12.  RE: odd inconsistant problem after GSS 2.0 upgrade

    Posted Nov 30, 2007 02:42 AM
    wow guys ... i was in a deep dark place when i stumbled onto this thread. words cannot describe the frustration i was feeling running into this bug. one week i was using gss 2.0 to deploy a 150 gig image to 40 machines and everything was running smooth, remember thinking .. 2.0 rox !!! .

    1 week later i was deploying an updated image with some minor fixes and updates to the same machines and BAM!  bsod on 9/10.  with  gss  running  as  smooth as it  did only one week earlyer this was the last place i thought to look. i was convinced that it had to be the updated image that  was conflicting with the fairly new  pci-e  machines. the 0xCA plug and play bsod allso pointed in this direction. after all, any device driver loaded during XP startup could cause this error.

    after 3 days of bughunting the image and trying to redeploy, i finally concluded that ... hmmm ... there was nothing to conclude?. everything was totally random and i the 3 days didnt get me any closer to eliminating possible causes to this. WTF ! . The world had gone mad and a thick cloud had decented on my head after working 20 hours a day trying to fix this problem.

    thank you thank you thank you,  for taking the time to write theese posts. as the last resort i was investigating  all possible pitfalls  when i stumbled onto this thread. reverted back to 8.2 and sun started shining in my part of the world again.

    A bug of this nature is probably one of the worst things to encounter, and i can only hope for other poor users of 2.0 that symantec fixes this issue fast so they dont have to experience the agony that i (and you) went through. I usually never take the time to respond to threads like this, but i allmost felt obligated to go back and share the experience with the next poor fellow who might be reading this.

    nasty bug ....