Jump to content


  • 0
Zero

Querky AHCI issue

Asked by Zero

Question

Zero Newbie

Zero

Posted
Posted

Hi All,

 

Quick one for you all.

 

I am currently deploying XP via SCCM OSD, and i have created a slipstream version of XP using Nlite. i have injected all the drivers for all of our lenovo fleet, and the media itself works a treat. then it gets tricky. we have around 6-7 lenovo models of drivers this cd is built for. i installed xp using this slipstream media, and then used the SCCM capture cd to capture a wim. funnily enough, the image is around 500mb, where the slipstream media is about 1gb.

 

that rang warning bells. so i tried that newly captured image on the same model, and it works. trying it on another model, and it installs the OS, but apon reboot to install the SCCM client, xp bluescreens with 000007b error, which implies my AHCI driver for that model is no longer on the image (where on the slipstream media, it works regardless because the driver has been injected)

 

so my question is as follows

 

1) during my initial installation of windows xp, obviously the driver needed was there. does XP drop/not carrying across un-needed drivers that are on the CD, for a cleaner install?

2) if the above answer is yes, what do i need to do to get those drivers either embedded onto the image, or installed?

 

edit: just wanted to say that i dont get the blue screen until AFTER its applied the xp.wim. this implies that the WinPE from sccm sp2 has the driver able to write to the disk, but the actual OS that is installed doesnt....

Share this post

Link to post
Share on other sites

11 answers to this question

Recommended Posts

  • 0
Zero Newbie

Zero

Posted
Posted

Ok so i've gone one step further and created WMI filters in my task sequence that relate to a driver to be installed.

 

So far, it picks up the driver and says "preparing to install". on reboot, i still get a blue screen with a 7b stop error.

 

 

what am i doing wrong?

Share this post

Link to post
Share on other sites
  • 0
Zero Newbie

Zero

Posted
Posted

Ok i've hit brick wall.

 

with my stand-alone media, it does the following

  • formats the hdd
  • applies the windows xp wim
  • matches the vendor ID to a driver (Description: Apply Intel® ICH8R/DH/DO SATA AHCI Controller TSManager 12/08/2010 5:28:21 PM 1192 (0x04A8))
  • crashes with error 80004005 while installing the device drivers

 

here is my attached smsts.log file from the install. can someone please go through it with me and see if they notice anything weird? i really cant see anything atm!

smsts.log

  • Like 1

Share this post

Link to post
Share on other sites
  • 0
Zero Newbie

Zero

Posted
Posted

Bump.. i really need help with this.

 

i've tried an alternative today. i created a custom sysprep.inf file and popped it into the c:\sysprep directory.

 

Created in the entry a BuildmassstorageSection=No

 

and then manually added my drivers.

 

Created an automated build and capture disk, captured that version of my OS

Created a Task sequence with the .wim, burnt THAT to dvd

moved to another model. doesnt work. still gettingthe 7b error.

 

edit: i pretty much followed this guide.

http://kongkuba1.spaces.live.com/blog/cns!EEFF1607E296E5AB!146.entry

 

edit: originally i followed this guide for sccm driver injection, but i was just getting error 80004005 with it

http://myitforum.com/cs2/blogs/rzander/archive/2009/08/07/apply-xp-massstorage-drivers-from-sccm-osd-task-sequence.aspx

Share this post

Link to post
Share on other sites
  • 0
anyweb Proficient

anyweb

Posted
Posted

first of all I wouldn't use an nlite version of XP in configmgr, i would add all drivers via the apply drivers package steps and wmi queries,

to create the master WIM image (with no drivers in it) i'd build and capture that image on a virtual platform such as vmware or hyperv, that way you are far less likely to see any bsod's when applying it to new models,

 

i'll take a look at your logs and come back soon

Share this post

Link to post
Share on other sites
  • 0
Zero Newbie

Zero

Posted
Posted

the log you posted looks ok, can you post one with the 80004005 error (driver injection access denied) pls

 

 

Hey,

 

Thanks for the prompt reply!

 

the 80004005 error is found in the smsts.log

"0, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\encryptablevolume.cpp,368) OSDDiskPart 12/08/2010 5:28:22 PM 1336 (0x0538)"

Volume 'C:' is not an encryptable volume OSDDiskPart 12/08/2010 5:28:22 PM 1336 (0x0538)

 

 

i havent got bitlocker set anywhere... and its windows xp.

 

in the meantime, im going to rebuild the base image in vmware, and see how i go..

Share this post

Link to post
Share on other sites
  • 0
Zero Newbie

Zero

Posted
Posted

Ok i rebuilt my image in vmware, and i got a bit more of a useful log with the error.

 

it is statign in smsts.log

"Loading offline registry hive "C:\WINDOWS\system32\config\software" into HKLM\OfflineRegistry1	OSDDriverClient	16/08/2010 2:44:27 PM	1436 (0x059C)
Loading offline registry hive "C:\WINDOWS\system32\config\system" into HKLM\OfflineRegistry2	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
CurrentControlSet is mapped to ControlSet001	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Driver Cache Index = C:\WINDOWS\inf\drvindex.inf	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Driver Cache = C:\WINDOWS\Driver Cache\i386	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Device Search Path = C:\WINDOWS\NLDRV\290;C:\WINDOWS\NLDRV\289;C:\WINDOWS\NLDRV\288;C:\WINDOWS\NLDRV\287;C:\WINDOWS\NLDRV\286;C:\WINDOWS\NLDRV\285;C:\WINDOWS\NLDRV\284;C:\WINDOWS\NLDRV\283;C:\WINDOWS\NLDRV\282;C:\WINDOWS\NLDRV\281;C:\WINDOWS\NLDRV\280;C:\WINDOWS\NLDRV\279;C:\WINDOWS\NLDRV\278;C:\WINDOWS\NLDRV\277;C:\WINDOWS\NLDRV\276;C:\WINDOWS\NLDRV\275;C:\WINDOWS\NLDRV\274;C:\WINDOWS\NLDRV\273;C:\WINDOWS\NLDRV\272;C:\WINDOWS\NLDRV\271;C:\WINDOWS\NLDRV\270;C:\WINDOWS\NLDRV\269;C:\WINDOWS\NLDRV\268;C:\WINDOWS\NLDRV\267;C:\WINDOWS\NLDRV\266;C:\WINDOWS\NLDRV\265;C:\WINDOWS\NLDRV\264;C:\WINDOWS\NLDRV\263;C:\WINDOWS\NLDRV\262;C:\WINDOWS\NLDRV\261;C:\WINDOWS\NLDRV\260;C:\WINDOWS\NLDRV\259;C:\WINDOWS\NLDRV\258;C:\WINDOWS\NLDRV\257;C:\WINDOWS\NLDRV\256;C:\WINDOWS\NLDRV\255;C:\WINDOWS\NLDRV\254;C:\WINDOWS\NLDRV\253;C:\WINDOWS\NLDRV\252;C:\WINDOWS\NLDRV\251;C:\WINDOWS\NLDRV\250;C:\WINDOWS\NLDRV\249;C:\WINDOWS\NLDRV\248;C:\WINDOWS\NLDRV\247;C:\WINDOWS\NLDRV\246;C:\WINDOWS\NLDRV\245;C:\WINDOWS\NLDRV\244;C:\WINDOWS\NLDRV\243;C:\WINDOWS\NLDRV\242;C:\WINDOWS\NLDRV\241;C:\WINDOWS\NLDRV\240;C:\WINDOWS\NLDRV\239;C:\WINDOWS\NLDRV\238;C:\WINDOWS\NLDRV\237;C:\WINDOWS\NLDRV\236;C:\WINDOWS\NLDRV\235;C:\WINDOWS\NLDRV\234;C:\WINDOWS\NLDRV\233;C:\WINDOWS\NLDRV\232;C:\WINDOWS\NLDRV\231;C:\WINDOWS\NLDRV\230;C:\WINDOWS\NLDRV\229;C:\WINDOWS\NLDRV\228;C:\WINDOWS\NLDRV\227;C:\WINDOWS\NLDRV\226;C:\WINDOWS\NLDRV\225;C:\WINDOWS\NLDRV\224;C:\WINDOWS\NLDRV\223;C:\WINDOWS\NLDRV\222;C:\WINDOWS\NLDRV\221;C:\WINDOWS\NLDRV\220;C:\WINDOWS\NLDRV\219;C:\WINDOWS\NLDRV\218;C:\WINDOWS\NLDRV\217;C:\WINDOWS\NLDRV\216;C:\WINDOWS\NLDRV\215;C:\WINDOWS\NLDRV\214;C:\WINDOWS\NLDRV\213;C:\WINDOWS\NLDRV\212;C:\WINDOWS\NLDRV\211;C:\WINDOWS\NLDRV\210;C:\WINDOWS\NLDRV\209;C:\WINDOWS\NLDRV\208;C:\WINDOWS\NLDRV\207;C:\WINDOWS\NLDRV\206;C:\WINDOWS\NLDRV\205;C:\WINDOWS\NLDRV\204;C:\WINDOWS\NLDRV\203;C:\WINDOWS\NLDRV\202;C:\WINDOWS\NLDRV\201;C:\WINDOWS\NLDRV\200;C:\WINDOWS\NLDRV\199;C:\WINDOWS\NLDRV\198;C:\WINDOWS\NLDRV\197;C:\WINDOWS\NLDRV\196;C:\WINDOWS\NLDRV\195;C:\WINDOWS\NLDRV\194;C:\WINDOWS\NLDRV\193;C:\WINDOWS\NLDRV\192;C:\WINDOWS\NLDRV\191;C:\WINDOWS\NLDRV\190;C:\WINDOWS\NLDRV\189;C:\WINDOWS\NLDRV\188;C:\WINDOWS\NLDRV\187;C:\WINDOWS\NLDRV\186;C:\WINDOWS\NLDRV\185;C:\WINDOWS\NLDRV\184;C:\WINDOWS\NLDRV\183;C:\WINDOWS\NLDRV\182;C:\WINDOWS\NLDRV\181;C:\WINDOWS\NLDRV\180;C:\WINDOWS\NLDRV\179;C:\WINDOWS\NLDRV\178;C:\WINDOWS\NLDRV\177;C:\WINDOWS\NLDRV\176;C:\WINDOWS\NLDRV\175;C:\WINDOWS\NLDRV\174;C:\WINDOWS\NLDRV\173;C:\WINDOWS\NLDRV\172;C:\WINDOWS\NLDRV\171;C:\WINDOWS\NLDRV\170;C:\WINDOWS\NLDRV\169;C:\WINDOWS\NLDRV\168;C:\WINDOWS\NLDRV\167;C:\WINDOWS\NLDRV\166;C:\WINDOWS\NLDRV\165;C:\WINDOWS\NLDRV\164;C:\WINDOWS\NLDRV\163;C:\WINDOWS\NLDRV\162;C:\WINDOWS\NLDRV\161;C:\WINDOWS\NLDRV\160;C:\WINDOWS\NLDRV\159;C:\WINDOWS\NLDRV\158;C:\WINDOWS\NLDRV\157;C:\WINDOWS\NLDRV\156;C:\WINDOWS\NLDRV\155;C:\WINDOWS\NLDRV\154;C:\WINDOWS\NLDRV\153;C:\WINDOWS\NLDRV\152;C:\WINDOWS\NLDRV\151;C:\WINDOWS\NLDRV\150;C:\WINDOWS\NLDRV\149;C:\WINDOWS\NLDRV\148;C:\WINDOWS\NLDRV\147;C:\WINDOWS\NLDRV\146;C:\WINDOWS\NLDRV\145;C:\WINDOWS\NLDRV\144;C:\WINDOWS\NLDRV\143;C:\WINDOWS\NLDRV\142;C:\WINDOWS\NLDRV\141;C:\WINDOWS\NLDRV\140;C:\WINDOWS\NLDRV\139;C:\WINDOWS\NLDRV\138;C:\WINDOWS\NLDRV\137;C:\WINDOWS\NLDRV\136;C:\WINDOWS\NLDRV\135;C:\WINDOWS\NLDRV\134;C:\WINDOWS\NLDRV\133;C:\WINDOWS\NLDRV\132;C:\WINDOWS\NLDRV\131;C:\WINDOWS\NLDRV\130;C:\WINDOWS\NLDRV\129;C:\WINDOWS\NLDRV\128;C:\WINDOWS\NLDRV\127;C:\WINDOWS\NLDRV\126;C:\WINDOWS\NLDRV\125;C:\WINDOWS\NLDRV\124;C:\WINDOWS\NLDRV\123;C:\WINDOWS\NLDRV\122;C:\WINDOWS\NLDRV\121;C:\WINDOWS\NLDRV\120;C:\WINDOWS\NLDRV\119;C:\WINDOWS\NLDRV\118;C:\WINDOWS\NLDRV\117;C:\WINDOWS\NLDRV\116;C:\WINDOWS\NLDRV\115;C:\WINDOWS\NLDRV\114;C:\WINDOWS\NLDRV\113;C:\WINDOWS\NLDRV\112;C:\WINDOWS\NLDRV\111;C:\WINDOWS\NLDRV\110;C:\WINDOWS\NLDRV\109;C:\WINDOWS\NLDRV\108;C:\WINDOWS\NLDRV\107;C:\WINDOWS\NLDRV\106;C:\WINDOWS\NLDRV\105;C:\WINDOWS\NLDRV\104;C:\WINDOWS\NLDRV\103;C:\WINDOWS\NLDRV\102;C:\WINDOWS\NLDRV\101;C:\WINDOWS\NLDRV\100;C:\WINDOWS\NLDRV\099;C:\WINDOWS\NLDRV\098;C:\WINDOWS\NLDRV\097;C	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Adding C:\drivers\1 to plug-and-play search path.	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
sDevicePath.length() < XP_MAX_DEVICEPATH, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,246)	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Maximum DevicePath length (4096) exceeded.	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
AddPnPDriverDirsToDevicePath( sTargetPath ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,714)	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Failed to update device path in offline registry. Code 0x80004005	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557)	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Entering ReleaseSource() for D:\SMS\PKG\VI100070	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
The user tries to release a source directory D:\SMS\PKG\VI100070 that is either already released or we have not connected to it	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,409)	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Failed to provision driver. Code 0x80004005	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Unloading offline SOFTWARE registry hive	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Unloading offline SYSTEM registry hive	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Exiting with return code 0x80004005	OSDDriverClient	16/08/2010 2:44:28 PM	1436 (0x059C)
Process completed with exit code 2147500037	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
!--------------------------------------------------------------------------------------------!	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
Failed to run the action: Intel(R) ICH8M-E/M SATA AHCI. 
Unspecified error (Error: 80004005; Source: Windows)	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
Sending status message . . .	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
Do not send status message in full media case	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
Clear local default environment	TSManager	16/08/2010 2:44:28 PM	1208 (0x04B8)
The execution engine ignored the failure of the action (Intel(R) ICH8M-E/M SATA AHCI) and continues execution	TSManager	16/08/2010 2:44:29 PM	1208 (0x04B8)
Sending status message . . .	TSManager	16/08/2010 2:44:29 PM	1208 (0x04B8)
"

 

it seems it is matching a driver and then failing to install it! - any help?

Share this post

Link to post
Share on other sites
  • 0
Zero Newbie

Zero

Posted
Posted

So i've figured it out i think, capturing overnight so i can apply and view my changes but here's an explanation

 

it seems that it grabs a list of drivers from the registry. nlite edits this devicepath registry entry to include and integrate drivers you have slipstreamed into the bootable media. once installed, that directory remains filled out.

 

it can be found under hklm\software\microsoft\windows\devicepath, it populates %systemroot% with a directory called nldrv and populates that subdirectory.

 

i have reset that value to its default %systemroot%\inf and will re-try the TS tomorrow.

 

 

 

UGH!

Share this post

Link to post
Share on other sites
  • 0
Zero Newbie

Zero

Posted
Posted

hey,

 

 

So i recaptured my build and capture without that registry value modified, and now my sccm injection works.

 

So in summary: Dont use Nlite driver injection if you're going to use sccm for deployment that includes some form of driver injection via sccm.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
Go to question listing
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.