Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all articles
Browse latest Browse all 11297

FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and /or Drive - Surface Pro 3 UEFI/GPT Win81 MDT 2013

$
0
0

We're trying to get our Windows 8.1 MDT 2013 image to work on Surface 3 Pro, but encountering this error in the process:

FAILURE ( 5456 ):  Unable to determine Destination Disk, Partition, and /or Drive 

This is our first Native UEFI device where we're forced to use UEFI and GPT disk format, and like anything new, it's not working.
I'm currently booting it to a USB drive (formatted correctly with two partitions, a FAT32 boot partition, and the rest of the drive for the Deploy folder).

It runs through the "Format and Partition Disk" task, sits there for a few seconds, looks like it's processing everything up until right before the Install phase, then errors out.

With MDT 2013, my Format and Partition Disk task is set to use MBR 100% of the drive. ZTIDiskpark knows and is correctly detecting the IsUEFI = True and creating the 4 partitions.

  Console > DISKPART> 
  Console >   Partition ###  Type              Size     Offset
  Console >   -------------  ----------------  -------  -------
  Console >   Partition 1    Recovery           300 MB  1024 KB
  Console >   Partition 2    System             499 MB   301 MB
  Console >   Partition 3    Reserved           128 MB   800 MB
  Console > * Partition 4    Primary            118 GB   928 MB

However, for some reason, in ZTIDiskPart.log, it indicates that "DestinationDisk and Partition did not yield a target Partition". After reviewing the ZTIDiskPart.log, it looks like it's only checking the first two partitions then giving up.

Log Files here on OneDrive: 
http://1drv.ms/1s5qvmp
1. BDD.log
2. LiteTough.log
3. ZTIDiskpart.log
If any other log files are needed, let me know!

Again, this is only happening on our first UEFI device (Surface 3 Pro), New computer scenario with Windows 8.1 in MDT 2013. The task sequence works great on all our BIOS/MBR devices. Any idea on why we're getting this error and how we can go about diagnosing it would be incredibly helpful! Thanks!


Viewing all articles
Browse latest Browse all 11297

Trending Articles