• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2133
  • Last Modified:

Symantec Ghost Solutions job fails due to driver in preOS

When I tried to deploy or capture an image, the job fails during the "to virtual partition step" with drivers could not be found in the preos for the following devices: see pics below

I originally had another device listed in there but I used the ghost boot wizard to edit the winpe file and added the intel nic it was asking for. I am wondering what would I have to do to add the device?

I tried modifying the pci.manifest.txt files but the job hangs at what wold be the same preOS step.

Please help soonest and many thanks

 event log event details winpe editor
0
tobe1424
Asked:
tobe1424
  • 19
  • 8
  • 3
  • +1
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Personally I would switch to the DOS Boot Disk, and not bother with WinPE.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
tobe1424Author Commented:
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


event detailpcdos setting
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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

lets see if this works.
0
 
tobe1424Author Commented:
I also moved it back to WinPE.
0
 
tobe1424Author Commented:
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.


 this is where it gets stuck
0
 
tobe1424Author Commented:
The task just failed with the same "failed to reboot client to recovery partition error"
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
tobe1424Author Commented:
is PCDOS the virtual partition you are talking about? It's the one I selected. You can see in the image I uploaded.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, check the disk of the client you are trying to Ghost.
0
 
tobe1424Author Commented:
the disk did not looked deframentated. I tried with the pcdos and it failed with the same message..like i posted earlier.

client hdd
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Defragment the disk.
Remove files from the root partition.
Free-up space.
0
 
tobe1424Author Commented:
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?

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

thanks again.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Try another PC, as a sanity check.
0
 
tobe1424Author Commented:
I don't have another to try on.
0
 
vivigattCommented:
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
0
 
tobe1424Author Commented:
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?

0
 
tobe1424Author Commented:
Correction, the optional settings on bios are:

Ata
Legacy

It's is currently on ahci
0
 
vivigattCommented:
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?
0
 
tobe1424Author Commented:
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
0
 
vivigattCommented:
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...
0
 
tobe1424Author Commented:
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
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
tobe1424Author Commented:
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
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
tobe1424Author Commented:
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.

0
 
tobe1424Author Commented:
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.
0
 
tobe1424Author Commented:
We found that there was a bug with the ghost solutions suite build 2266. We ended up having to purchase a support agreement in order to obtain the patch. Also, in addition to injecting the xp driver into the winpe image, we inserted the intel driver for vista as well -- even though they are xp clients.

We had build 10.5.1.2266 and after installing the patch, the ghost boot wizard was upgraded to 10.5.1.2269. The patch only updates the ghost boot wizard, not the entire console.

Here is brief list of fixes this build takes care of:

Solution

I. Issues Resolved

------------------------------------------------------------------------------

•One-click Virtual partition does not work on the Lenovo M57P / M58P desktop computer
•Adding a Mass Storage driver to WinPE 2.1 causes Ghost to hang in the PreOS
•After installing the GSS2.5, the Ghost console server, Ghost Boot Wizard and Ghost explorer do not launch.
•Using Ghost32.exe for Hot imaging fails to execute on client machine.
•Client replication observed when upgrade from GSS older version to GSS 2.5.1



0
 
LeeTutorretiredCommented:
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.
0
 
LeeTutorretiredCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
 
tobe1424Author Commented:
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
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 19
  • 8
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now