Failure(5456):unable to determine Destination Disk,Partition,and/or Drive RRS feed

  • Question

  • AD:Win Srv 2012:AD+DHCP+DNS;

    MDTServer:MDT2013 Preview+ADK8.1  

    Deployment Type=Replace

    "Standard Client Replace Task Sequence" error:

    • Edited by 雷龙 Monday, August 5, 2013 2:39 PM
    Monday, August 5, 2013 2:23 PM

All replies

  • Can you post your BDD.log (to SkyDrive or something).  Is it an SSD by any chance?

    David Coulter | | @DCtheGeek

    Tuesday, August 6, 2013 1:34 AM
  • @DCtheGeek

       Thank you for your reply, not an SSD.


    Tuesday, August 6, 2013 11:33 AM
  • Sorry it took so long to get back to you, been a busy day.

    Digging through the log, it looks like ZTIUserState is what's generating the error (the actual code is in ZTIUtility as part of the GetOSTargetDriveLetterEx Function).  I've compared ZTIUserState.wsf and ZTIUtility.wsf between MDT 2012 U1 and MDT 2013 Preview and the scripts are identical (other than the version header), so I don't believe it's a problem specifically with the Preview components.

    These are the actual lines before the error:

    Unable to yield a target Partition (Special Recovery option for Litetouch).
    DestinationDisk and Partition did not yield a target Partition.

    Immediately after that, it does GetAllFixedDrives and finds that D: (Disk #1, Part #0) is the FirstPossibleSystemDrive.  So it sees the disks and partitions (which means it's probably not a HDD driver error).  You can validate this by dropping to debug command prompt while in WinPE and doing diskpart --> list disk and seeing the results.  From your screenshot, it looks like that's a 50 GB partition, but I can't see how much is free.

    I think the problem is some variables aren't set, though, that should have been set automatically when you created the Task Sequence.  If you look in DeployRoot\Control\<TS ID> there is a file for your Task Sequence called ts.xml.  At the top of it should be something like the following:

        <variable name="OSGUID" property="OSGUID">{12345678-1234-1234-1234-0123456789AB}</variable>
        <variable name="DestinationDisk" property="DestinationDisk">0</variable>
        <variable name="DestinationPartition" property="DestinationPartition">1</variable>
        <variable name="DestinationOSVariable" property="DestinationOSVariable">OSDisk</variable>
        <variable name="DestinationOSRefresh" property="DestinationOSRefresh"></variable>
        <variable name="DestinationOSDriveLetter" property="DestinationOSDriveLetter"></variable>
        <variable name="DestinationOSInstallType" property="DestinationOSInstallType">ByVariable</variable>

    Can you validate that segment exists and post what you have?  It will help me walk the GetOSTargetDriveLetterEx function and see where the failure actually is.

    David Coulter | | @DCtheGeek

    Wednesday, August 7, 2013 2:43 AM
  • ts.xml:

    I'm sure "C:"、“D:” and"F:" all have enough free space.

    Wednesday, August 7, 2013 1:37 PM
  • I mistakenly assumed you used a "Standard Client Task Sequence" and see that you used a "Standard Client Replace Task Sequence" (which I've never really tried before (now's a great time!).  This is why you do not have the global variables I was looking for.  I'll have to play with the Replace Task Sequence to understand what it's doing, so hopefully someone with more experience with it can respond to you first. : )

    David Coulter | | @DCtheGeek

    Thursday, August 8, 2013 6:50 PM
  • I feel very strange, when there is more than one hard disk or partition, use hyper-v to test basic OK, but testing will appear frequently with VMware9.0 the question.

    Friday, August 9, 2013 1:58 AM