none
SOLVED - MDT 2012 & Win 7 OSD failure <off a MULTIBOOT USB>

    Question

  • I've also been getting the infamous OSD failure  "Litetouch deployment failed, Return Code = -2147467259 0x80004005" and have read several forums to no avail such as this one, (Link)

    The error occurs as soon as Win7 starts to install with the error "Unable to create a new system partition"

    Here is what I've done:

    Used USB 2.0 port
    Made internal HD 1st in priority
    Modified the TS to create the System reserved partition, make it bootable, and 1st partition
    Verified my MDK was working by deploying XP on the same laptop and had no failures
    Downloaded another copy of Win7 and used a fresh TS (No modifications)
    I am able to see the network & my deployment server "\\karl-med\deploymentshare1"
    I am able to see the hard drive via F8 as I can pull the logs off the C:.  The logs are pretty much the same as what others have posted (i.e. LTIApply.log)

    CustomSettings.ini

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=Y
    SkipAppsOnUpgrade=YES
    SkipCapture=YES
    SkipAdminPassword=YES
    SkipProductKey=YES
    DeploymentType=NEWCOMPUTER
    DoNotCreateExtraPartition = YES

    I am running my MDT 2012 on a XP PC.  The lapop in question is a HP 8470 laptop with a solid state drive.  I haven't seen anything specific for SSD drives and as I said before, I am seeing the drive via F8.

    I am at a loss as to why this still fails.  Any other ideas?
    Thanks!


    • Edited by lrak35 Saturday, December 29, 2012 8:17 AM
    Sunday, December 23, 2012 2:02 PM

Answers

  • Um...  Ok...  There is a solution to this madness after all.  I was chasing the wrong side of the stick.  I am using a USB multiboot app which allows me to load any ISO and launch it.  Seems that after I dug around for awhile on the internet, I stumbled across some threads and came across the solution by accident.

    The emulator was the problem and after reading the tutorial, I am HAPPY to say, Windows 7 IS INSTALLING from my MDT 2012 server off a USB drive :)



    The solution is <DRUM ROLL PLEASE> ..........  < WAIT FOR IT > ....................




    Boot any windows ISO from USB

    http://www.rmprepusb.com/tutorials/firawiniso



    • Marked as answer by lrak35 Saturday, December 29, 2012 8:17 AM
    • Edited by lrak35 Saturday, December 29, 2012 8:18 AM
    Saturday, December 29, 2012 8:17 AM

All replies

  • If you boot the HP 8470 from WinPE and run diskpart cmd "list disk", do you see the SSD and is it Disk 0?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Sunday, December 23, 2012 5:14 PM
  • Yes.   It is Disk 0 in Diskpart.  I can create / delete the partitions normally. 

    Sunday, December 23, 2012 11:24 PM
  • I even tried a custom DISKPART script (Link) and changed the BIOS setting from AHCI to IDA.  Still no change.

    Is there a setting in the Win7 unattend.xml that can resolve this as the error seems to be in the setup program?

    Friday, December 28, 2012 6:36 AM
  • From where do you start the deployment (PXE boot with F12, USB, CD or UNC from Windows)?

    You dont need to set DeploymentType in customsettings. Please remove this or explain why you need it in customsettings.ini.

    Before you start deployment. Check with diskpart your availible paritions with 'list disk' and 'list vol'. Then on error do that again.

    Do you have any other storage inserted like, second disk, USB or media card? If yes, please remove this.

    If all fails please upload bdd.log and setupact.log to an internet disk and post link here. Thanks.

    Friday, December 28, 2012 8:32 AM
  • The error is in the Win 7 setup.  Even though Win7 setup fails, I am able to see the hard drive partitions as I have defined in the unattend.xml file.

    Still trying to determine the cause as there seems to be no post anywhere with a solid resolution.

    Friday, December 28, 2012 1:51 PM
  • The error is in the Win 7 setup.  Even though Win7 setup fails, I am able to see the hard drive partitions as I have defined in the unattend.xml file.

    Still trying to determine the cause as there seems to be no post anywhere with a solid resolution.

    Yes, That is why we would like to see setupact.log or setuperr.log. You will find the files where the Windows folder is. I think it's on the V: when in WinPE. You can search for it by using the dir setupact.log /s

    If you find the setuperr.log you will often see a hex error code. Translate this to deciamal and then run net helpmsg <errcode_in_decimal>

    For example, a few hours ago I got an error message from Windows setup that it could not copy the wim file. I looked in the setuperr.log and found hex code 0x70. This translates to 112 in decimal. I then ran net helpmsg 112 and got explaining "There is not enough space on the disk." I renamed the $oem$ folder in my tsguid folder and problem solved.

    Friday, December 28, 2012 2:07 PM
  • Thank you for the advise.  Makes me wonder what the Panther folder is used for.

    Logs:  https://sites.google.com/site/dinodod/win7

    The error is:

    GetMachineInfo:Couldn't find boot disk on this BIOS-based computer

    Hex 0x00000057 translates to Dec 87

    C:\>net helpmsg 87

    The parameter is incorrect.

    I've also included my Unattend.xml file as well

    Here is what I do: 

    1) Plug in my thumbdrive into a USB 2.0 port

    2) Boot off the thumbdrive

    3) Once MDT welcome screen opens, I unplug my thumbdrive

    4) I now select my Win7 install and off it goes until Win7 Setup, where it fails

    I'm looking for more information on why this is failing.  I've seen several users give up and use a CD which is not an option as I do not need to be wasting any more CDs.  

    ==============

    Looking at the SetupAct.log,  The HD is being seen just fine and is supported

    [0x0606cc] IBS    GetSystemDiskNTPath: Found system disk at [\Device\Harddisk1\Partition0].
    2012-12-28 19:56:41, Info                  IBS    IsDiskSupported:Checking if disk [0] has the necessary driver support.
    2012-12-28 19:56:41, Info                  IBS    IsDeviceSupported:Device description is [INTEL SSDSC2BW180A3H]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [IDE\DiskINTEL_SSDSC2BW180A3H__________________LCSi____]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [IDE\INTEL_SSDSC2BW180A3H__________________LCSi____]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [IDE\DiskINTEL_SSDSC2BW180A3H__________________]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [INTEL_SSDSC2BW180A3H__________________LCSi____]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [GenDisk]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [GenDisk]
    2012-12-28 19:56:41, Info                  IBS    IsDeviceIDPresent:Found device ID [GenDisk] in hwcompat list
    2012-12-28 19:56:41, Info                  IBS    IsDeviceSupported:Device [INTEL SSDSC2BW180A3H] is supported
    2012-12-28 19:56:41, Info                  IBS    IsDeviceSupported:Device description is [Serial ATA Controller]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [PCI\VEN_8086&DEV_1E03&SUBSYS_179B103C&REV_04]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [PCI\VEN_8086&DEV_1E03&SUBSYS_179B103C]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [PCI\VEN_8086&DEV_1E03&CC_010601]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [PCI\VEN_8086&DEV_1E03&CC_0106]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [PCI\VEN_8086&DEV_1E03&REV_04]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [PCI\VEN_8086&DEV_1E03]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [PCI\VEN_8086&CC_010601]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [PCI\VEN_8086&CC_0106]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [PCI\VEN_8086]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [PCI\CC_010601]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [PCI\CC_0106]
    2012-12-28 19:56:41, Info                  IBS    IsDeviceIDPresent:Found device ID [PCI\CC_010601] in hwcompat list
    2012-12-28 19:56:41, Info                  IBS    IsDeviceSupported:Device [Serial ATA Controller] is supported
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [ACPI\PNP0A08]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [*PNP0A08]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [*PNP0A03]
    2012-12-28 19:56:41, Info                  IBS    IsDeviceIDPresent:Found device ID [*PNP0A03] in hwcompat list
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [ACPI_HAL\PNP0C08]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [*PNP0C08]
    2012-12-28 19:56:41, Info                  IBS    IsDeviceIDPresent:Found device ID [*PNP0C08] in hwcompat list
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      H/w    ID [acpiapic]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [DETECTEDInternal\ACPI_HAL]
    2012-12-28 19:56:41, Info                  IBS    DumpDeviceIDs:      Compat ID [DETECTED\ACPI_HAL]
    2012-12-28 19:56:41, Info                  IBS    IsDeviceIDPresent:Found device ID [acpiapic] in hwcompat list
    2012-12-28 19:56:41, Info                  IBS    DetermineDeviceSupport:Disk 0 has the necessary driver support

    • Edited by lrak35 Saturday, December 29, 2012 7:15 AM
    Saturday, December 29, 2012 7:07 AM
  • Um...  Ok...  There is a solution to this madness after all.  I was chasing the wrong side of the stick.  I am using a USB multiboot app which allows me to load any ISO and launch it.  Seems that after I dug around for awhile on the internet, I stumbled across some threads and came across the solution by accident.

    The emulator was the problem and after reading the tutorial, I am HAPPY to say, Windows 7 IS INSTALLING from my MDT 2012 server off a USB drive :)



    The solution is <DRUM ROLL PLEASE> ..........  < WAIT FOR IT > ....................




    Boot any windows ISO from USB

    http://www.rmprepusb.com/tutorials/firawiniso



    • Marked as answer by lrak35 Saturday, December 29, 2012 8:17 AM
    • Edited by lrak35 Saturday, December 29, 2012 8:18 AM
    Saturday, December 29, 2012 8:17 AM
  • Great you found a solution. What USB multiboot app was causing this error?
    Wednesday, January 02, 2013 7:42 AM
  • XBOOT:  
    http://www.pendrivelinux.com/xboot-multiboot-iso-usb-creator/

    I think it has something to do with how either Grub4DOS or Syslinux is setup.

    With the solution, I made my flash drive also emulate a HDD which may have contributed to the solution.  I've never learned anything on Linux so I just used the tutorial.

    Thursday, January 03, 2013 9:29 AM