Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

DeployAnywhere fails with Tecra R850 / Intel(R) 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller

Updated: 26 May 2011 | 20 comments
logik's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi all,

As title suggests, i am unable to 'deployanywhere' to this machine. The stumbling point is where WinPE attempts to locate the following driver:

Missing drivers detected:

Device type  : Storage Device
PCI ID       : PCI\VEN_8086&DEV_1C03&SUBSYS_00011179&REV_04
Description : Device Description Unavailable

However:

a) VEN_8086&DEV_1C03 is listed in my Chipset Folder (Intel 9.2.0.1015), under cougahci.inf (%PCI\VEN_8086&DEV_1C03.DeviceDesc%=intelahci,PCI\VEN_8086&DEV_1C03). I have tried adding (%PCI\VEN_8086&DEV_1C03.DeviceDesc%=intelahci,PCI\VEN_8086&DEV_1C03&SUBSYS_00011179 and %PCI\VEN_8086&DEV_1C03.DeviceDesc%=intelahci,PCI\VEN_8086&DEV_1C03&SUBSYS_00011179&REV_04) with no success.

b) I've listed

 ( {0x8086 = { 0x1C03 = () } } ) in skip.pci.manifest.txt, same error.

 ( {0x8086 = { 0x1C03 = (0x11179) } } ) in skip.pci.manifest.txt, same error.

After each image refresh, i have checked pci.manifest.txt and the line had been added correctly.

c) After each modification, I have removed/readded the chipset folder again (recompile image), and then created a new PXE image for network boot.

d) In drivers.manifest.txt, the driver is setup for both XP and VISTA:

            path = "CHIPSET9.2.0.1015\\cougahci.inf",
            os = ("XP" "VISTA")

e) The error I receive on the client (while in WinPE) is:

Installing device:

PCI\VEN_8086&DEV_1C03&SUBSYS_00011179&REV_04

with

matching on

A cancel has been requested.

 

I literally do not know what else to try. I am running GSS 2.5.1 (2266), i've had these problems with other devices before - but never this difficult.

james

 

NOTE: Host OS is Windows XP, WinPE is standard Vista PE

Discussion Filed Under:

Comments

Nitin's picture
24
May
2011
0 Votes 0
Login to vote

Hi, Every thing seems to be

Hi,

Every thing seems to be ok in your case. Though just guess work and may not be applicable in your case !! Have you selected the driver folder from storage tab after added drivers into Winpe? When you add the drivers, the folder is unselected by default. You need to explicitely select the folder and rebuild the winpe.

Can you please specify the model of the machine/laptop?

Regards,
Nitin

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

logik's picture
24
May
2011
0 Votes 0
Login to vote

>When you add the drivers,

>When you add the drivers, the folder is unselected by default. You need to explicitely select the folder and rebuild the winpe.

Yep, made sure of this.

 

Machine is Toshiba Tecra R850 (PTS525A-003019).

Nitin's picture
24
May
2011
0 Votes 0
Login to vote

Can you please send inf file

Can you please send inf file contents to investigate further?

Regards,
Nitin

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

logik's picture
24
May
2011
0 Votes 0
Login to vote

Pulled *.inf from

Pulled *.inf from C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\windrivers\CHIPSET9.2.0.1015

 

AttachmentSize
CHIPSET9.2.0.1015.zip 99.3 KB
Nitin's picture
25
May
2011
0 Votes 0
Login to vote

Hi, Here is the catch.....

Hi,

Here is the catch..... and this was defect in GSS and it is fixed in build 2605...

Background : The reported driver inf file contains Include and Need section. These two section is used to refer install section from other system supplied driver(http://msdn.microsoft.com/en-us/library/ff552302.aspx). However when DA runs, os\windows\inf(system supplied inf folder) is not available. So DA fails in parsing the inf file. To solve this issue, DA will not parse the Need and Include section from inf file for /eval switch. Currently DA fails the operation for such type for drivers. Now DA will not fail operation if it can not find included files in Inf file.

Please get this patch from support team, the instructions to get the patch is mentioned in the sticky note on the top of this forum.

Please let me know whether this patch resolve your problem.

Regards,
Nitin

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

logik's picture
25
May
2011
0 Votes 0
Login to vote

Nope, still doesnt work;

Nope, still doesnt work; still receive the same error message:

A cancel has been requested.
Missing drivers detected:
Device type  : Storage Device
PCI ID       : PCI\VEN_8086&DEV_1C03&SUBSYS_00011179&REV_04
Description : Device Description Unavailable

WinPE image was updated with 2605 (double checked under 'Client' tab on console, reports 11.5.1.2605)

What next?

Nitin's picture
25
May
2011
0 Votes 0
Login to vote

Just to confirm... Have you

Just to confirm... Have you re-build the Winpe after applying the patch? This is necessary to update the boot package with the new binaries. Please go thorugh the readme.txt which contains the procedure to apply the patch.

I am also looking for the hardware to check this issue... So far no luck ...

Regards,
Nitin

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

logik's picture
25
May
2011
0 Votes 0
Login to vote

>WinPE image was updated with

>WinPE image was updated with 2605

Yes, this has been done every time as previously stated.

Nitin's picture
25
May
2011
0 Votes 0
Login to vote

Hmm... I have no clue on why

Hmm... I have no clue on why this isn't work until I execute it on the hardware....let me find the hardware here to check the issue...

Regards,
Nitin

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

Nitin's picture
25
May
2011
0 Votes 0
Login to vote

Can you please confirm the

Can you please confirm the results if you execute ghDplyAw32.exe in isolation on Toshiba laptop? Please attach the results (output file) to this thread.

Regards,
Nitin

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

logik's picture
25
May
2011
0 Votes 0
Login to vote

X:\GHOST>ghdplyaw32.exe

X:\GHOST>ghdplyaw32.exe /target=c:\windows /ddb=c:\ddb
Installing device :
        HID\VID_045E&PID_00CB
with
        C:\WINDOWS\inf\msmouse.inf
matching on
        HID_DEVICE_SYSTEM_MOUSE

Installing device :
        IDE\DiskHitachi_HTS543232A7A384_________________ES2OA70B
with
        C:\WINDOWS\inf\disk.inf
matching on
        GenDisk

Installing device :
        PCI\VEN_8086&DEV_0091&SUBSYS_52018086&REV_34
with
        C:\ddb\PROWireless14.0.2.2-XP\.\NETwNx32.INF
matching on
        PCI\VEN_8086&DEV_0091&SUBSYS_52018086

Installing device :
        PCI\VEN_8086&DEV_1502&SUBSYS_00011179&REV_04
with
        C:\ddb\1000-PROSET16.2-XP\.\e1c5132.inf
matching on
        PCI\VEN_8086&DEV_1502&SUBSYS_00011179

Installing device :
        PCI\VEN_8086&DEV_1C03&SUBSYS_00011179&REV_04
with

matching on

A cancel has been requested.

Missing drivers detected:

Device type  : Storage Device
PCI ID       : PCI\VEN_8086&DEV_1C03&SUBSYS_00011179&REV_04
Description : Device Description Unavailable

Error

X:\GHOST>

logik's picture
25
May
2011
0 Votes 0
Login to vote

Whats even more interesting,

Whats even more interesting, if i look at C:\ddb\CHIPSET9.2.0.1015\cougahci.inf - i can see VEN_8086&DEV_1C03 listed there in plain sight!

Nitin's picture
26
May
2011
0 Votes 0
Login to vote

Can you please zip it

Can you please zip it "CHIPSET9.2.0.1015" folder and attach to this thread? This is going to be very interesting for us. Thanks for your patience.

Regards,
Nitin

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

logik's picture
26
May
2011
0 Votes 0
Login to vote

Taken directly

Taken directly from:

C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\windrivers

AttachmentSize
CHIPSET9.2.0.1015.zip 449.56 KB
EdT's picture
26
May
2011
0 Votes 0
Login to vote

Include and Need sections

cougahci.inf has both an Include and a Need statement in it, and there are no specific drivers referenced in this INF, so it appears to be entirely reliant on the other referenced INF files to handle the necessary driver loading.

Although I see that Ghosti has talked about the Include and Need sections earlier in this thread, I would assume that they do need to be present and available to complete the driver loading.

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

Nitin's picture
26
May
2011
0 Votes 0
Login to vote

We need the source driver

We need the source driver folder and not from the windrivers folder. There are chances of missing some files which are required when added via GBW. 

Regards,
Nitin

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

logik's picture
26
May
2011
0 Votes 0
Login to vote

Intel Chipset 9.2.0.1015

Hello EdT and ghosti,

I used the chipset driver available for this model from Toshiba's website.

http://www.mytoshiba.com.au/file/download/resource...

(Its equivalent to Intel's direct release of 9.2.0.1015, except with a Toshiba stub to facilitate installation)

james

Nitin's picture
26
May
2011
0 Votes 0
Login to vote

James, Please find attached

James,

Please find attached the zip file which contains Intel storage drivers. Please extract and add the drivers from Ghost Boot Wizard and try it. Please update the result. If it does not work then run msinfo32.exe and  send us the output.

AttachmentSize
Drivers.zip 459.98 KB

Regards,
Nitin

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

logik's picture
26
May
2011
0 Votes 0
Login to vote

Morning, I rolled back my

Morning,

I rolled back my Ghost installation to 2269 (after 2605 introduced communication issues), removed the CHIPSET9.2.0.1015 folder, added the contents of 'Drivers.zip' into the image, refreshed and built new PXE image.

Working perfectly; the machine now installs the SATA driver without a problem.

Thanks to ghosti, EdT and Manojkumar for your quick assistance.

james

Nitin's picture
26
May
2011
0 Votes 0
Login to vote

Nice to hear that new drivers

Nice to hear that new drivers actually solved your problem.... I believe there should not be communication issue with 2605 as well. You need to refresh inventory and configuration.

Regards,
Nitin

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