Ghost Solution Suite

Hi There,

I am trying to clone a PC using WinPE. It boots fine into it and starts going though its process, however it stops at the following:

x:\GHOST>ghost32 /setosdrives /blind 1>>x:\ghost\startlog.txt

It just stays like that and does not continue. I am unable to type any commands or stop it.

After 20mins or so, the Ghost Console states that the task has failed and says that the client has timed out.

I have Windows 7 installed on the PC and am running the latest version of Ghost 2.5.1

Hope you can help.

Thanks,

Terry

Are you booting WinPE via PXE or from a CD/DVD or a USB device?

I am running it as an image task from the Ghost Console

I had this exact issue, and it was solved by putting a CD in the drive.  One of the Symantec reps on the site told me about it, saying it was an issue.  It didnt even need to be a particular CD, it was just querying for something to be in the drive.  When I did that, it started right up.  If that is the issue, Symantec has a patch

Hello,

Based on where it is failing, the issue may be with a storage driver. It is just after that point Ghost32 should be loading, and the first thing Ghost does is establish a connection with the storage controller. You will likely need to add the Windows Vista 32bit driver for the SATA controller (as required by WIndows PE 2.0, which is what Ghost uses). 

Thank you,

Randy

Hi

If this is a console task, you can check the exact cause for this issue as follows:

As soon as the clone task fails in your console, the executed task on the bottom of console window will get a red "x" mark on it. Right click the same and click on Event Log ....Now, it will pull up a new window in which you can see the internal steps performed during the execution of the task.  If I am right, You will see " To Virtual Partition Failed " .  Right click the same and select  Event Details. This will show you the cause for the failure of the task. Check the same and update it here..Will help you ....


Dilip

Hi There,

Thanks for the reponses.

Terry - I shall give that a go and see what happens.

Randy - I believe that i am using a Windows 7 32bit driver rather than a Vista driver, so i will change that to Vista and let you know the outcome.

Dilip - When i go into the event log it just says "Client Timed out"

Many Thanks,

Terry

Hi

It is must that you must add the vista(32) version of drivers for your WinPE. Please remove the previous template and add the vista version of network driver. It will work.  For details regarding the same , go to event log in your task ..Right click "Client Time Out" and select  Event Details. This will show you the cause for the failure of the task. Check the same and update it here..Will help you ....

Dilip

Hey Terry,

Please find the links below that would detail us on the usage of VISTA Driver for WinPE and also the methodology we need to employ while adding the VISTA drivers to the WinPE boot package.

Why does Symantec Ghost need drivers for Windows Vista when imaging some other operating system?
http://service1.symantec.com/support/on-technology.nsf/854fa02b4f5013678825731a007d06af/5e6480394b1bcf05882575d3007ec9aa?OpenDocument

How to add drivers to DeployAnywhere or WinPE
http://service1.symantec.com/support/on-technology.nsf/854fa02b4f5013678825731a007d06af/e4c1aea6046866e288257444007f9333?OpenDocument

Hope this helps.

Terry,

That solved it for me too, thanks heaps for the post... This particular laptop is just giving me grief. First I had a different issue, then this one. It's a  Dell Latitude E6400.

I was able to isolate which point of the boot process it was getting stuck at by playing with the batch files. Spefically modifying it to boot straight to a command prompt without running anything. Then I just ran each of the ghost commands in sequence to work out where it got stuck.

It seems that the command 'ghost32 /setosdrives' cause it to lock up (which is how I found this thread) - which I was able to work around with the CD trick.

What a weird one...

Do you have anymore information on this patch?

no problem.  I had such a time with this problem, I wanted other people to know about it and have them be able to work around it, and then get the fix since they than know what they need.  I think you still have to request 2269 from the admins, not just live update to it