none
Strange issue with new model failing to determine destination disk RRS feed

  • Question

  • Deploying images is working for all of our other Dell machines. I've been trying to deploy on a Latitude 3590 and it is not working so I assumed the first problem was missing drivers. I imported drivers, updated deployment share, still wasn't working. The operating system would install and on the reboot, it would try to boot to the NIC again and wouldn't continue deployment. If I manually continued deployment, I received an error FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. I researched that error and made sure that I was setting the OSDisk variable and applying in under operating system.

    I started looking through the logs and found this in the BDD.log after diskpart finishes

    <![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '494586032128' and VolumeName = 'Windows' and VolumeSerialNumber = '4EF5B486']LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Search for Drive: TargetPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '494586032128' and VolumeName = 'Windows' and VolumeSerialNumber = '4EF5B486']LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[DestinationDisk and Partition did not yield a target Partition.]LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Drive not found: ]LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[DestinationDisk: 0]LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Assume this disk is the destination Disk, and verify.]LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '494586032128' and VolumeName = 'Windows' and VolumeSerialNumber = '4EF5B486']LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Search for Drive: TargetPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '494586032128' and VolumeName = 'Windows' and VolumeSerialNumber = '4EF5B486']LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[DestinationDisk and Partition did not yield a target Partition.]LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Assume this disk is not the destination Disk (2).]LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[ZTIDiskpart processing completed successfully.]LOG]!><time="09:09:17.000+000" date="08-29-2018" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">

    and then further down received

    <![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="09:46:04.000+000" date="08-29-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '494586032128' and VolumeName = 'Windows' and VolumeSerialNumber = '4EF5B486']LOG]!><time="09:46:04.000+000" date="08-29-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Search for Drive: TargetPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '494586032128' and VolumeName = 'Windows' and VolumeSerialNumber = '4EF5B486']LOG]!><time="09:46:04.000+000" date="08-29-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[DestinationDisk and Partition did not yield a target Partition.]LOG]!><time="09:46:04.000+000" date="08-29-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.]LOG]!><time="09:46:04.000+000" date="08-29-2018" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Event 41002 sent: FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.]LOG]!><time="09:46:05.000+000" date="08-29-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="09:46:05.000+000" date="08-29-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="09:46:05.000+000" date="08-29-2018" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="09:46:05.000+000" date="08-29-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    I can post then entire log if that is helpful. I'm hoping someone can point me in the right direction

    Wednesday, August 29, 2018 5:05 PM

All replies

  • Are you using Dell CAB files? I have not deployed to a 3590 (but LOTS of other Dells).

    Does this happen on more than one 3590 or only one so far? You may need to clear the disk.
    With the error up, press F8 to get to a DOS prompt. Use:

    diskpart (enter)
    list disk (enter)
    select disk 0 (enter, providing it shows disk 0, the main HDD)
    clean (enter)
    Exit (enter)
    Exit (enter)

    Boot back in and see if it completes.

    Wednesday, August 29, 2018 7:40 PM
  • I've only tested one but I will give another a shot. I have cleared the disk and unfortunately that does not help
    Wednesday, August 29, 2018 8:00 PM
  • Sorry forgot to add that I am using Dell CAB files and I've tried a few different versions to see if that would help. We use all Dell laptops here so I have 3570s and 3580s that work with no problem. It fails on all task sequences, even new ones I just built
    Wednesday, August 29, 2018 8:10 PM
  • So to be clear, the OS will install and on reboot, it starts up trying to PXE again? Just jumping ahead, I did have this issue and for me I fixed the 'boot to NIC loop' problem like this:

    I had to edit my LTIApply.wsf file. I first made a copy of the file, then edited it below. The first section is what it initially is, and the 2nd is what it was changed to. That prevented any of my pc's from booting in a loop to NIC.

    Modify the original file as follows:



    This prevented the boot-looping to NIC for me.
    Wednesday, August 29, 2018 8:21 PM
  • Okay I'm going to give that a shot. I did find another forum that describes exactly what my issue is

    https://serverfault.com/questions/913635/dell-latitude-3490-mdt-results-in-no-boot-device-found

    But I didn't find anything to really try besides setting up UEFI boot. When I boot to NIC I was doing it under the legacy boot so it did apply the non UEFI partitioning. 

    Wednesday, August 29, 2018 8:41 PM
  • I'm not sure about that one. If you set the pc to UEFI, then MDT will create the partition that way...likewise with Legacy. It has logic to format the partition accordingly. But if you want the pc formatted UEFI, then set the BIOS that way before going to PXE.

    For me, I was setting the BIOS to UEFI for my newer Dells and they were booting in a loop to PXE, until I modified the LTIApply file in my Deploy\Scripts folder. Now they don't ever try to boot back in a loop again.

    I hope this helps.

    Wednesday, August 29, 2018 8:48 PM
  • Could you post your BDD.log file on a public hosting site so that I could take a look?

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Monday, September 3, 2018 9:21 AM