locked
MDT 2012 successfully captured xp image but I am not able to deploy them successfully. RRS feed

  • Question

  • I successfully captured xp image using MDT. Created a task sequence and specify the xp.wim file that I captured but no luck on deploying. This is the error I am getting after mdt install the os on a machine. Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware referace manuals for additional information.

    I loaded the xp source cd and created a task sequence for capture and point the TS for the xp source for the OS. Run the LTE script from a reference computer and successufully capture the image.

    I don't know what to do.  Loaded all the drivers that we use for XP machines but I have no luck.

    Any help would be greatly appreciated.


    • Edited by ROBTRIMED Tuesday, October 15, 2013 11:50 PM
    Tuesday, October 15, 2013 11:18 PM

All replies

  • What you are talking about is Bugcheck 0x7b - INACCESSIBLE_BOOT_DEVICE. The bootloader successfully loaded up the OS, however the OS could not find the disk device from where it came from to load up the rest of the OS.

    Essentially this means that you are missing the correct driver for the storage controller. I suspect that you are using the newer Intel ACHI storage controller, which does *not* have an in-box equivalent.

    ZTIDrivers is smart enough to insert any appropriate drivers into the deployment process for the full OS install.

    *however*

    If you have a Windows XP or Windows Server 2003 syspreped image, then it is different matter, MDT does not have a way to *inject* drivers during *deploy* time. Instead you should add the driver to the image itself. MDT has a step to perform that action during sysprep and capture. a) add the Intel Driver to a new driver folder b) add the folder to a new selection profile c) in your Task Sequence --> State Restore --> Imaging --> Sysprep Only --> "Add mass storage drivers to sysprep.inf for XP and 2003" (get the hint :^) add the new selection profile here.

    ( think this is correct, but it's been several years since I've touched ZTIDrivers.wsf ).

    The long term fix is to get off of XP and onto a newer OS :^)


    Keith Garner - keithga.wordpress.com

    • Proposed as answer by Keith GarnerMVP Wednesday, October 16, 2013 1:40 AM
    Wednesday, October 16, 2013 1:40 AM
  • Thanks Keith for the response.

    I created a folder on my MDT\delpoymentshare\out of box drivers and put the mass storage drivers that I downloaded from Intel and Microsoft sites, go to my Task Sequence and did your instructions but no luck.

    I am restarting again from the scratch. I copied all the drivers and put in c:\sysprep\i386\$oem$ hopefully this one will work or if you have a better suggestion that would be great.

    Wednesday, October 16, 2013 5:13 PM
  • I am stil getting the same error "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware referace manuals for additional information."

    What I did something new was load the driver(mass storage driver, etc...) in the selection profile for Optiplexe 210L, edit the sysprep and put this drivers on my sysprep but still no luck. What did I missed?

    Please help...

    [Sysprep]
    ;   BuildMassStorageSection = Yes


    [SysprepMassStorage]
    ;
    ; Added for Intel SATA Controller Support
    ;
    PCI\VEN_8086&DEV_2681&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_27C1&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_27C5&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_2821&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_2829&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_2922&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_2929&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_3A02&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_3A22&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_3B29&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_3B2F&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_3B22&CC_0106=C:\Drivers\Ref_IntelSATA\iaAHCI.inf
    PCI\VEN_8086&DEV_2682&CC_0104=C:\Drivers\Ref_IntelSATA\iaStor.inf
    PCI\VEN_8086&DEV_27C3&CC_0104=C:\Drivers\Ref_IntelSATA\iaStor.inf
    PCI\VEN_8086&DEV_27C6&CC_0104=C:\Drivers\Ref_IntelSATA\iaStor.inf
    PCI\VEN_8086&DEV_2822&CC_0104=C:\Drivers\Ref_IntelSATA\iaStor.inf
    PCI\VEN_8086&DEV_282A&CC_0104=C:\Drivers\Ref_IntelSATA\iaStor.inf
    ;
    ; Added for VMware VMSCSI Support
    ;
    PCI\VEN_104B&DEV_1040=C:\Drivers\Ref_VMSCSI\vmscsi.inf
    ;
    ; Added for VMware LSILogic SCSI Support
    ;
    PCI\VEN_1000&DEV_0621=C:\Drivers\Ref_lsilogic\symmpi.inf
    PCI\VEN_1000&DEV_0622=C:\Drivers\Ref_lsilogic\symmpi.inf
    PCI\VEN_1000&DEV_0624=C:\Drivers\Ref_lsilogic\symmpi.inf
    PCI\VEN_1000&DEV_0626=C:\Drivers\Ref_lsilogic\symmpi.inf
    PCI\VEN_1000&DEV_0628=C:\Drivers\Ref_lsilogic\symmpi.inf
    PCI\VEN_1000&DEV_0030=C:\Drivers\Ref_lsilogic\symmpi.inf
    PCI\VEN_1000&DEV_0032=C:\Drivers\Ref_lsilogic\symmpi.inf
    ;
    ; Added for ich4ide Controller Support
    ;
    PCI\VEN_8086&DEV_24CB=C:\Drivers\Ref_IntelInf\ich4ide.inf
    PCI\VEN_8086&DEV_24CA=C:\Drivers\Ref_IntelInf\ich4ide.inf
    ;
    ; Added for ich5ide Controller Support
    ;
    PCI\VEN_8086&DEV_24D1=C:\Drivers\Ref_IntelInf\ich5ide.inf
    PCI\VEN_8086&DEV_24DB=C:\Drivers\Ref_IntelInf\ich5ide.inf
    PCI\VEN_8086&DEV_25A2=C:\Drivers\Ref_IntelInf\ich5ide.inf
    PCI\VEN_8086&DEV_25A3=C:\Drivers\Ref_IntelInf\ich5ide.inf
    ;
    ; Added for ich6ide Controller Support
    ;
    PCI\VEN_8086&DEV_2651=C:\Drivers\Ref_IntelInf\ich6ide.inf
    PCI\VEN_8086&DEV_2652=C:\Drivers\Ref_IntelInf\ich6ide.inf
    PCI\VEN_8086&DEV_2653=C:\Drivers\Ref_IntelInf\ich6ide.inf
    PCI\VEN_8086&DEV_266F=C:\Drivers\Ref_IntelInf\ich6ide.inf
    ;
    ; Added for ich7ide and ich8ide (ich78ide.inf) Controller Support
    ;
    PCI\VEN_8086&DEV_27C0=C:\Drivers\Ref_IntelInf\ich78ide.inf
    PCI\VEN_8086&DEV_27C4=C:\Drivers\Ref_IntelInf\ich78ide.inf
    PCI\VEN_8086&DEV_27DF=C:\Drivers\Ref_IntelInf\ich78ide.inf
    PCI\VEN_8086&DEV_2820=C:\Drivers\Ref_IntelInf\ich78ide.inf
    PCI\VEN_8086&DEV_2825=C:\Drivers\Ref_IntelInf\ich78ide.inf
    PCI\VEN_8086&DEV_2828=C:\Drivers\Ref_IntelInf\ich78ide.inf
    PCI\VEN_8086&DEV_2850=C:\Drivers\Ref_IntelInf\ich78ide.inf
    ;
    ; Added for ICH9IDE, ICHAIDE and IBEXIDE (ibexide.inf) Controller Support
    ;
    PCI\VEN_8086&DEV_2920=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_2921=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_2926=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_2928=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_292D=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3A00=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3A06=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3A20=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3A26=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3B20=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3B21=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3B2D=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3B2E=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3B26=C:\Drivers\Ref_IntelInf\ibexide.inf
    PCI\VEN_8086&DEV_3B28=C:\Drivers\Ref_IntelInf\ibexide.inf
    ;
    ; Added for Intel 631xESB/6321ESB/3100 Serial ATA Controller Support
    ;
    PCI\VEN_8086&DEV_2680=C:\Drivers\Ref_IntelInf\ESB2ide.inf
    PCI\VEN_8086&DEV_269E=C:\Drivers\Ref_IntelInf\ESB2ide.inf
    ;
    ; Below driverlist is Common XP builtin drivers
    ;
    Primary_IDE_Channel=%systemroot%\inf\mshdc.inf
    Secondary_IDE_Channel=%systemroot%\inf\mshdc.inf
    PCMCIA\*PNP0600=%systemroot%\inf\mshdc.inf
    *PNP0600=%systemroot%\inf\mshdc.inf
    PCMCIA\KME-KXLC005-A99E=%systemroot%\inf\mshdc.inf
    PCMCIA\_-NinjaATA--3768=%systemroot%\inf\mshdc.inf
    PCMCIA\FUJITSU-IDE-PC_CARD-DDF2=%systemroot%\inf\mshdc.inf
    *AZT0502=%systemroot%\inf\mshdc.inf
    PCI\CC_0101=%systemroot%\inf\mshdc.inf
    PCI\VEN_10B9&DEV_5215=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_2441=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_244A=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_244B=%systemroot%\inf\mshdc.inf
    PCI\VEN_10B9&DEV_5219=%systemroot%\inf\mshdc.inf
    PCI\VEN_10B9&DEV_5229=%systemroot%\inf\mshdc.inf
    PCI\VEN_1097&DEV_0038=%systemroot%\inf\mshdc.inf
    PCI\VEN_1095&DEV_0640=%systemroot%\inf\mshdc.inf
    PCI\VEN_1095&DEV_0646=%systemroot%\inf\mshdc.inf
    PCI\VEN_0E11&DEV_AE33=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_1222=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_1230=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_7010=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_7111=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_2421=%systemroot%\inf\mshdc.inf
    PCI\VEN_8086&DEV_7199=%systemroot%\inf\mshdc.inf
    PCI\VEN_1042&DEV_1000=%systemroot%\inf\mshdc.inf
    PCI\VEN_1039&DEV_0601=%systemroot%\inf\mshdc.inf
    PCI\VEN_1039&DEV_5513=%systemroot%\inf\mshdc.inf
    PCI\VEN_10AD&DEV_0001=%systemroot%\inf\mshdc.inf
    PCI\VEN_10AD&DEV_0150=%systemroot%\inf\mshdc.inf

    Thursday, November 7, 2013 4:06 PM
  • Is the OemPnPDriversPath under Unattended pointing to the correct location? Looks like it would be Drivers\Ref_IntelSATA, Drivers\Ref_VMSCSI, Drivers\Ref_lsilogic, and so on.

    -Nick O.

    Thursday, November 7, 2013 10:34 PM
  • Nick, thank you for quick response but can you please explain it to me what you mean by Is the OemPnPDriversPath under Unattended pointing to the correct location? Do you mean point my driver selection profile to my sysprep?

    On my TS/Preinstall/Inject Drivers/ I specify the model of xp driver that I need (Optiplex 210L) and disable the add mass storage in Imaging/Sysprep/ but doesn't work.

    I even try this but nothing work for me.

    Location: BlogsJohan
    Arwidmark
       
    Posted
    by:
    johan
    4/23/2010

    Ever struggled with a 0x0000007B BSOD when deploying a Windows XP SP3
    image?

    Struggle no more, here is a working driver set and sysprep mass storage
    section for most current hardware models...

    Instructions for adding the sample files to MDT 2010 Lite
    Touch

    In these steps I assume you have a deployment share in the D:\MDTProduction
    folder, Windows XP Pro SP3 (full source) imported to the
    D:\MDTProduction\Operating Systems\Windows XP Pro SP3 Eng x86 Unattend folder,
    and that you created a Task Sequence named Windows XP Pro SP3 Eng x86 Unattend
    Task Sequence.

    Step 1 - Download sample files


    1. Download and extract the sample files to D:\Setup\Sample
      Files
      (http://www.deployvista.com/Repository/tabid/71/EntryId/62/DMXModule/396/Download/attachment/language/en-US/Default.aspx)

    Step 2 - Disable the builtin add mass storage action


    1. Right-click the Windows XP Pro SP3 Eng x86 Unattend Task Sequence
      and select Properties.
    2. In the Task Sequence tab, configure the Windows XP
      Pro SP3 Eng x86 Unattend Task Sequence
      with the following
      setting,
    3. Disable the Capture Image -> Add mass storage drivers to
      sysprep.inf for XP and 2003 action
      .
    4. Click OK.

    Step 3 - Configure sysprep.inf


    1. Right-click the Windows XP Pro SP3 Eng x86 Unattend Task Sequence
      and select Properties.
      .
    2. In the OS Info tab, click Edit
      sysprep.inf
      .
    3. Edit the mass storage section using the
      D:\Setup\Samples Files\Sysprep\storage.txt sample

    Step 4 - Add the drivers


    1. Using Explorer, copy the D:\Setup\Sample
      Files\$OEM$
      folder to the D:\MDTProduction\Operating
      Systems\Windows XP Pro SP3 Eng x86 Unattend
      folder

    Step 5 - Build and Capture


    1. Run the Windows XP Pro SP3 Eng x86 Unattend Task Sequence
      on a virtual machine.

    Thursday, November 7, 2013 11:29 PM
  • Try looking at http://support.microsoft.com/kb/314479, specifically the Sysprep Setup section. It's been about two years since I had to create a XP image but I remember things working once I specifically noted where the drivers were going to be located, i.e. the drivers path property in Sysprep.inf needs to be set for the actual path of the storage drivers on the image.

    Keep in mind XP cannot have drivers injected like Vista and newer, so the drivers must already exist on the image before sysprep. I've seen MDT's processes not work before in terms of building the mass storage section, which is why Johan recommends disabling that step.


    -Nick O.

    Friday, November 8, 2013 4:08 PM