locked
MDT fails to deploy to an MBR disk larger than 2TB RRS feed

  • Question

  • Hello,

     

    Problem:

    MDT 2012 Update Rollup 8 (6.3.8330) failed to deploy using the default server task sequence (server.xml) to a computer using a BIOS (MBR disk) if the disk is greater than 2TB in size.  The deployment will fail during the "Installing Operating System" phase.  When, after the failure, I looked in the DISM.LOG file (Press F8 at the error window to launch a CMD prompt, view / copy C:\Windows\Logs\DISM\dism.log) I saw errors including the following:

     

    2016-01-21 13:58:27, Error                 DISM   DISM WIM Provider: PID=1200 [CreateDestinationFileEx:(3324) -> SetFileSize failed] C:\Windows\assembly\NativeImages_v4.0.30319_32\System.ServiceModel\673e962beaf835de9a3660ea255d2a5e\System.ServiceModel.ni.dll (HRESULT=0x80070070) - CWimManager::WimProviderMsgLogCallback

    [1200] [0x80070070] RestoreFileNodeList:(2122): There is not enough space on the disk.

    [1200] [0xc144012e]

    2016-01-21 13:58:27, Error                 DISM   DISM WIM Provider: PID=1200 C:\Windows\assembly\NativeImages_v4.0.30319_32\System.ServiceModel\673e962beaf835de9a3660ea255d2a5e\System.ServiceModel.ni.dll (HRESULT=0x80070070) - CWimManager::WimProviderMsgLogCallback

    [1200] [0x80070070] RestoreFilesCallback:(3638): There is not enough space on the disk.

    [1200] [0x80070070] EnumImageDataEntries:(1047): There is not enough space on the disk.

    [1200] [0x80070070] GetImageErrorCode:(2833): There is not enough space on the disk.

    [1200] [0x80070070] GetImageErrorCode:(2833): There is not enough space on the disk.

    [1200] [0x80070070] ImageWorkerThread:(187): There is not enough space on the disk.

    [1200] [0x80070070] ImageWorkerThread:(187): There is not enough space on the disk.

    [1200] [0x80070070] RestoreAllData:(985): There is not enough space on the disk.

    [1200] [0x80070070] WIMApplyImageInternal:(704): There is not enough space on the disk.

     

    When in the CMD prompt I ran DISKPART, and:

    LIST DISK

    SELECT DISK 0

    LIST PARTITION

    LIST VOLUME

     

    I saw there were only two partitions.  The C: drive was only 500MB, followed by the Recovery partition which was about 2TB.  This was although according to the default server task sequence the System Reserved partition should be 500MB, followed by the Windows partition C: which should be 99% of the remaining available space, followed by the Recovery partition.

     

    Cause:

    As far as I can tell, Windows only supports addressing MBR disks up to 2TB in size.  The MDT scripts do not take this limitation into account, and using the defaults in the server.xml task sequence will try and create a partition larger than 2TB, which fails.

     

    Solution:

    In the following script:

    \\wds\DeploymentShare$\Scripts\ZTIDiskpart.wsf

    On line 408 I replaced the following:

            '//----------------------------------------------------------------------------
    
            '//  Create Partitions from Table
    
            '//----------------------------------------------------------------------------
    
     
    
            iRemainingSize = oDisk.oWMI.Size / 1024 /1024
    
            iExtendedRemainingSize = 0
    
     
    
            '
    
            ' Enumerate through all partition entries
    
            '


    with:

            '//----------------------------------------------------------------------------
    
            '//  Create Partitions from Table
    
            '//----------------------------------------------------------------------------
    
     
    
            iRemainingSize = oDisk.oWMI.Size / 1024 /1024
    
            If not isUEFI and iRemainingSize > 2 * 1024 * 1024 then
    
                ' The maximum addressable size of an MBR disk is 2TB
    
                iRemainingSize = 2 * 1024 * 1024
    
            End if
    
            iExtendedRemainingSize = 0
    
     
    
            '
    
            ' Enumerate through all partition entries
    
            '


     

    to cap the size that MDT attempts to partition in an MBR disk to 2TB.

     

    I would appreciate guidance, or if appropriate this fix being included in a future version of MDT.

     

    Thank you,

    Matt


    Friday, January 22, 2016 11:19 PM

All replies

  • If you don't file this as a bug on connect this won't likely be in a future version of MDT.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Saturday, January 23, 2016 12:47 AM
  • Thank you, I have filed this here:

    https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/2273147

    Matt

    Saturday, January 23, 2016 2:18 AM