none
MDT fails to make a blank disk bootable

    Question

  • When using MDT to deploy an OS to a completely empty disk (zero partitions) - MDT will fail to make the disk bootable, it would seem:

    SMSTS.log

    User did not specify local data drive    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Volume A:\ is not a fixed hard drive    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Volume D:\ is not a fixed hard drive    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Volume W:\ has 30643773440 bytes of free space    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Volume W:\ is not bootable    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Volume X:\ is not a fixed hard drive    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Volume Z:\ is not a fixed hard drive    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    TSM root drive =     TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    We do not find an available volume to store the local data path    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Set a global environment variable _SMSTSNextInstructionPointer=47    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=47    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Set a global environment variable _SMSTSInstructionStackString=41    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Set a TS execution environment variable _SMSTSInstructionStackString=41    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Save the current environment block    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    pszPath[0] != L'\0', HRESULT=80070057 (c:\qfe\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,58)    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,639)    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Failed to save environment to  (80070057)    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842)    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420)    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Failed to persist execution state. Error 0x(80070057)    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)
    Failed to save execution state and environment to local hard disk    TSManager    6/4/2013 10:44:19 PM    2144 (0x0860)

    -----

    However, it's showing that it is successfully making it bootable:

    LTIApply.log

    Event 5625 sent: The image \\SERVER\AdminDeployment$\Operating Systems\win2008r2\win2008r2.wim was applied successfully.    LTIApply    6/4/2013 10:43:33 PM    0 (0x0000)
    About to run command: "\\SERVER\AdminDeployment$\Tools\X64\bootsect.exe"  /nt60 W:    LTIApply    6/4/2013 10:43:33 PM    0 (0x0000)
    Command has been started (process ID 1880)    LTIApply    6/4/2013 10:43:33 PM    0 (0x0000)
      Console > Target volumes will be updated with BOOTMGR compatible bootcode.    LTIApply    6/4/2013 10:43:33 PM    0 (0x0000)
      Console > W: (\\?\Volume{c3ed9a1f-cda5-19e2-b519-00155d546500})    LTIApply    6/4/2013 10:43:33 PM    0 (0x0000)
      Console >     Successfully updated NTFS filesystem bootcode.    LTIApply    6/4/2013 10:43:41 PM    0 (0x0000)
      Console > Bootcode was successfully updated on all targeted volumes.    LTIApply    6/4/2013 10:43:41 PM    0 (0x0000)
    Return code from command = 0    LTIApply    6/4/2013 10:43:41 PM    0 (0x0000)
    Find the boot drive (if any) [True] [6.1.7601.18015] [False]    LTIApply    6/4/2013 10:43:41 PM    0 (0x0000)
    New ZTIDiskPartition : \\MININT-QSI0A4R\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-QSI0A4R\root\cimv2:Win32_LogicalDisk.DeviceID="W:"    LTIApply    6/4/2013 10:43:42 PM    0 (0x0000)

    -----

    If I reboot and try again (now that the system has a formatted disk) - it always works.  This happens 100% of the time under the following condition - If there is more than one physical disk.  I can't purposely recreate this on a single disk.  I'm not even touching that second disk during build, so I don't know why it would affect it.  I've tried both booting from media as well as PXE - same thing each time.

    Oddly, when the disk is clean to begin with, MDT chooses W: for OSDisk.  When it has to clean the disk, it chooses V:.

    Anyone have any ideas?


    • Edited by agressiv Wednesday, June 05, 2013 5:10 AM
    Wednesday, June 05, 2013 5:08 AM

All replies

  • FYI, if anyone stumbles upon this thread:

    This is a bug that Microsoft has confirmed with MDT 2012 Update 1 and the current ADK.  We're exploring workarounds and determining if its a bug in MDT 2012 Update 1 itself or the ADK.

    • Proposed as answer by Brian Gonzalez Monday, October 07, 2013 6:52 PM
    Friday, June 07, 2013 6:45 PM
  • Hi

    I've the same trouble

    Have you find solution ?

    Maybe one idea for modify script (ZTIPDiskpart or another) ?

    Please help me.

    Scorpio92

    Friday, October 04, 2013 2:44 PM
  • This is not a scripting bug in MDT, it's an issue with the stand alone sequencer in MDT (a component from SCCM).

    I have not been able to reproduce this issue in the lab. It's possible that it's an interaction issue with uEFI machines *and* the WAIK.

    Check to see if you have the WAIK installed, or if you have installed the ADK. If you installed the ADK, is this a clean install, or did you upgrade from the WAIK?

    Please let me know either way.


    Keith Garner - keithga.wordpress.com


    Monday, October 07, 2013 4:32 PM