Video Screencast Help

Ghost32 Hangs on startup

Created: 11 May 2011 • Updated: 12 May 2011 | 11 comments
This issue has been solved. See solution.

I am using Ghost Suite 11.5.1.2266.  Normally i haven't had any problems but on one computer i am not able to get Ghost32 to run from a CD or USB boot device.  I am attempting to image the one drive to an image file stored on a separate drive attached to the computer.  I have tried disabling all the NICs and Storage drivers except for the always include ones and the NIC for this computer and storage drivers.  I don't believe it is the storage device drivers since I can access the drives from the command line before ghost32 boots from the WinPE environment.  I have a ASUS Rampage III, with the internal Intel 82567v-2 Gigabit controller, Intel ICH10R Raid controller, and the Marvel 91xx SATA 6G storage device controllers.  There are no drives on the Marvel controller.  I have tried starting Ghost32 using the -nousb and it still hangs.  The Ghost32 window comes up, but no other information inside the window and the window is frozen.  I can't close it, i can only reboot at this point.  There are no error messages.  Is there a error file that might indicate what is causing this?  Any ideas from anyone?

Comments 11 CommentsJump to latest comment

EdT's picture

So you can boot WinPE to a command prompt from a USB or CD device and view the contents of your hard disk, and presumably view the connected USB device also.

What I am wondering is whether the Ghost program is somehow detecting the Marvell chipset and trying to mount is, perhaps incorrectly, causing the program to hang, I presume you have waited a few minutes to see if the hang times out ?  Try adding the Marvell drivers and see how you get on.

By the way, if you are starting your USB device from a USB-3 port, make sure you have the USB-3 drivers included in your WinPE boot disk, Also, if the CD (I assume its a DVD these days) is connected to a SATA port, maybe you also need to make sure its a port for which drivers have been supplied.  Also , if you happen to be using a USB-3 drive for storage, you may need to load the drivers that came with the USB-3 drive as well.

WinPE V2 has the ability to load drivers dynamically - if you type DRVLOAD <path to INF file> and the INF file has a SYS and CAT file in the same folder, then WinPE should be able to load the driver from a USB stick or other convenient storage device. This can avoid the necessity of generating new WinPE media while finding out which drivers work.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Stillwater_Brian's picture

Thanks for the reply.  I tried loading the USB3 drivers dynamically, it said it loaded sucessfully, but ghost32 still hangs after the ghost32 screen is displayed.  Sometimes the background is displayed inside of the frame of the ghost32 window.  I disabled the USB3 controller, NIC, SATA6 controller, onboard audio, onboard Firewire, and none of this seemed to fix the problem, the program still freezes at the ghost32 window.  Any other ideas?

EdT's picture

Just a thought - did you use the WinPE or the WinPE (512) option?  You need the 512 option in order to be sure to have enough space to load drivers. If this is not the issue, then check if your ASUS mobo has the latest bios, and if you are overclocking the board, please try setting the board back to non-overclock settings in case there are any marginal speed issues with the memory.

If none of these points help, check out this article: Adventures with WinPE Symantec Connect

This will give you a path to generate an independent WinPE boot system with which you can try booting your system. You can copy Ghost32.exe over and try from there.  However, this is a last resort move, as you have stated that it is only one machine that is not working as expected.  One more thought that occurred to me just now, is that if this machine is what I might describe as a hot gaming platform with a monster video card, you may need to load some video drivers as well. For the purposes of testing quickly however, if you have an old, lower performance, PCI-E graphics card, you could just plug that in in place of whatever you have at the moment and see if it makes a difference.

Having said all that, my monster gaming rig does boot WinPE V2 quite happily although the boot SSD is not visible without the SATA-6 drivers loaded, and the USB-3 ports don't work without the USB-3 driver, etc, etc, but the NVidia 570 card works fine without any drivers.  The motherboard is latest ASUS P6 as well but socket 1155 instead of the 1336 of the Rampage.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Stillwater_Brian's picture

I tried the setting back to normal speed for the clock, that didn't seem to fix anything.  I do indeed use the 512 option. 

My BIOS was dated so i flashed it to the latest.  I ran the WinPE again and it still doesn't work.  Haven't tried the video card yet (i have a nVidia 580) will try that next.  Just confirming it doesn't matter that I'm trying to image a 64bit OS hard drive from the 32 bit WinPE. 

How would you add in the video drivers, same as the USB 3.0 drivers, include them on the disk and then dynamically install them at the dos prompt?

Stillwater_Brian's picture

First I at least found the problem area.  RAID.

Tried an older video card and that did the same thing. 

I then disabled my RAID in the bios.  I have 2 drives mirrored, and another 2 drives on the same controller as non-RAID.  I rebooted and things worked normally.  So the issue it appears to be Ghost and the storage driver handling the RAID set.  I rebooted after it was working and went back into the BIOS to reset the SATA controller to RAID (options are IDE, AHCI, and RAID) but after rebooting, i found my RAID drives no longer in a RAID volume but non-members.  I ended up rebooting to the OS and used the Intel Console to build an array from an existing volume.  It will take some time to rebuild but it looks like i haven't lost any data.  I would like to be able to Ghost my non-RAID OS drives without having to change my BIOS and remove HDs.

I am using the Intel ICH10R SATA drivers v8.9.7.1001 dated in Feb 2010.  The vendor and hardware IDs match the iaStor.inf vs the iaAHCI.inf.

Any idea?

Nitin's picture

Hi,

It is worth to try with build 2269 patch binaries. I suspect this is new Intel AHCI controller driver issue. You can try workaround to put the blank CD in CD/DVD drive and try opening ghost32.exe booted via USB drive ghost boot package. 

Details about how to obtain the patch can be found in the sticky posting at the begining of this forum.

Please also try to search forum on 2269 and view threads which discuss the various issues that these patches address. Alternatively, if you have support agreement with Symantec, you can talk to support member and describe your issues, as they will only release the patches if you have an issue that the patch is designed to address.

Regards,
Nitin

If you feel your issue has been addressed to, please use the "Mark as Solution" link for the relevant thread

SOLUTION
EdT's picture

If you are still stuck after going through the process Ghosti recommends, and you have time to explore a differnet path, check out this article: https://www-secure.symantec.com/connect/articles/readyadventures-winpe

This describes how to build a V2 WinPE boot environment using the Microsoft free WAIK, which also includes their own imaging utility called imagex.exe

You can then try the same drivers as you have already proved with the GSS WinPE build, and check if you can create an image using imagex.  It works in a similar way to Ghost but excludes things like the swap file automatically, so can generate slightly smaller images. It's not as clever as Ghost, so to restore a WIM image, you need to partition and format the disk first (using diskpart) and then write the image, but at least it gives you an alternative path to try which will establish if your driver collection is complete and correct.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Stillwater_Brian's picture

ghosti: Thanks for the tip on the blank DVDs in the drives, that seemed to have resolved the issue.  I was able to boot using the USB drive with 2 blank DVDs in the 2 DVD bays that i have.  I then tried to boot using my normal WinPE Boot CD with a blank DVD drive in the other bay, that also worked.  So the issue seems to be the controller not liking drives that are empty.  I have a feeling that the 2269 patch might work but I don't have a current service agreement and you can't contact Symantec Tech support to get the patch without one.  So the workaround is simply put in a blank DVD during my ghosting operation.

EdT: thanks for your help, your suggestions got me thinking in other areas which eventually led me to the problem area.  I was about to try your WinPEv2 solution but one question, what version of WinPE does GSS 2.5.1 ship with?  Isn't WinPEv2 Vista?  So would I be creating an earlier version of WinPE with v2 or a later version than  ghost boot wizard produces.

Nitin's picture

Good to hear that your issue is resolve with the workaround. You can get rid of the problem once for all by getting the build 2269 patch.

Regards,
Nitin

If you feel your issue has been addressed to, please use the "Mark as Solution" link for the relevant thread

EdT's picture

GSS ships with WinPE V2, and the article uses the latest V2 version available, so I cannot guarantee its exactly the same build release as GSS but in other respects its based on the same Vista kernel and uses the same drivers.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.