Symantec Ghost Solutions job fails due to driver in preOS

Personally I would switch to the DOS Boot Disk, and not bother with WinPE.

I'll just re-interate, we've had many problems deploging Ghost Enterprise Suite 2.0 using the Windows PE based boot disks, with getting various drivers to work correctly, that in the end we abandonded the WinPE versions in favour of the older DOS boot function, which works perfectly.

I just went to the client properties and changed the Virtual partition PreOS to PCDOS. Now the task fails with the message below.

Thanks for the help

I just tried this what they did here:  http://www.symantec.com/connect/forums/driver-issue

lets see if this works.

I also moved it back to WinPE.

so far it looks like i am stuck on this. It hasn't moved for about 10 minutes after adding the driver to WinPE. it looks like the same outcome as when I modified the pci.manifest.txt files.

Please help soonest.


 

The task just failed with the same "failed to reboot client to recovery partition error"

I would not bother with WInPE.

Check the PC, you are trying to Ghost, is the disk defragmented, does it had enough free disk space.

Also use the virtual dos partition.

is PCDOS the virtual partition you are talking about? It's the one I selected. You can see in the image I uploaded.

Yes, check the disk of the client you are trying to Ghost.

the disk did not looked deframentated. I tried with the pcdos and it failed with the same message..like i posted earlier.

Defragment the disk.
Remove files from the root partition.
Free-up space.

I performed a disk defragmentation and cleaned up a few things...but it shows that there is ample space on the drive.. I have the same issue when trying to create an image.

What else should i do?

please bare in mind that I am trying to do this on a remote site with only one person to assist.

thanks again.

Try another PC, as a sanity check.

I don't have another to try on.

The problem you have with missing/Wrong drivers in WinPE is common to systems using SATA controllers and disks.
The easiest way would be to configure the HDD controller to be IDE compatible (this is usually a BIOS setting). I assume that you do not care about the data on the disks and that you want to re-image it completely. BTW, using IDE/ATA mode for the HDD controller might also solve your "DOS" configuration issues.

The harder (but cleaner) way is to inject the correct SATA drivers into the PE image prior to boot it.
Check this link:
http://www.symantec.com/business/support/index?page=content&id=TECH110136&locale=en_US

Well i tried to inject the correct driver into the winpe image. I the message relating to the drivers does not appear after I injected the sata controller drivers. however, I do receive the"failed to reboot client to recovery partition error" message.

i recall having a similar issue when i changed the sata operation settings in the bios to autodetec /ahci.

do you think changing the bios setting from ahci to legacy or ide will fix this?

Correction, the optional settings on bios are:

Ata
Legacy

It's is currently on ahci

Is ATA/Legacy a single option?

If not, I'd try ATA first and then Legacy.

Also, I am not familiar with ghost operations taht require to reboot to "recovery partition". What I suspect is that there is no recovery partition...
Usually, I use ghost to reimage completely a disk or one or several partitions. This usually does not involve any recovery partition. AFAICT, recovery partitions are common with OEM installs, and they can embed a ghost image which is the equivalent of the factory installed image.
I rarely use that. OTOH, I usually re-image from a .gho file that I created first.
Is it what you are trying to do?

Yes I am using a gho file to push the image to the client. I then tried to pull the image after the push failed and ended with the same results

Normally, ghost can work from the WinPE environment without needing any recovery partition or without needing to reboot.
Can you open a console (cmd.exe) while under WinPE and:
- connect to the share that hosts your .gho file (net use g: \\<Server>\<share> /user:<User> )
- launch ghost32
- select the appropriate options to re-image the local HDD from the ghost file

?

Also you did not answer the question regarding the HDD controller options...

Ok thanks for the info. I have not received confirmation that the sata operation setting in bios was changed from ahci to ata.

I am waiting on personell to make this change.

One more thing to add to this puzzle is that I was told that the current image on the workstation came from a dell optiplex 780. The workstation we are trying to re-image is actually a opti 760.

Do you think this can be causing chaos?

thanks again

You've not written the image yet have you? At present, you are trying to boot the workstation to accept the image?

If you do not have a like for like image, e.g. an image for the same hardware, you could experience issues when the PC starts with that image.

The personell that installed the image on the 760 did not use pxe or the ghost console. He installed it off a usb drive.

I am trying to create(pull) an image to the server so that I can have a base image to deploy to future clients.

Howerver, I wonder if this problem is occuring because of the incorrect image that was initially installed or because of an actual issue with ghost.

The only issue I experienced is the fact that I get prompt for a High Def audio driver when I log on. But I would think this wouldn't be the issue. This is the only workstation of it's kind in the lan. the others workstations are legacy opti 260's

Personally, I would ensure, I had a working correct image on the machine I was taking the image from, rather than a "hacked image and install", to base my Baseline Golden Master Image on.

The image that was used on this particular test machine was used on the rest of Dell Optiplex 760's on a remote site. You can say that we are using Baseline Golden Master Image on this machine. We only have one image that we have used for other deployments.

I switched the bios from ahci to ata and did not do much. I need to try legacy mode now. I hope this does the trick.

thanks for your input.

the personell has not made the bios changed to 'legacy' but I have a feeling that will not do much.

According to Symantec KB's, my issue relates to an incorrect NIC. I have an Intel 82567LM-3 Gigabit Network Card. Hence, I have the pro1000 nic drivers into the Universal Packet Driver template.

Although I just removed them from the WinPE boot image, I had the SATA controller and Intel nic drivers injected prior to having the correct image installed on the workstation.

Please help soonest. Thank you.

I've requested that this question be closed as follows:

Accepted answer: 0 points for tobe1424's comment http:/Q_27347064.html#36989389

for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Is there a way i can accept my own solution which is in the last post? I had forgotten to accept my own solutions, even though I don't received any points, I figure it might serve others well

Thx