Monday, 14 May 2018 20:02

Understanding FAILURE (5615): Boot Drive not Found

Written by
Rate this item
(0 votes)

image

Continuing the theme of focusing on disk-related cases (yesterday I posted an article detailing how to fix the "Verify BCDBootEx" step failing on HP ProDesk 600 MT G3 systems), this post showcases yet another reason why you should stop deploying systems in Legacy mode. It also shows how a little time spent on reviewing log files to get a couple of clues can quickly lead to a solution.

I love the questions people post on the TechNet forums and I try to help them successfully troubleshoot their problems when I have some spare time on my hands. This particular question was submitted back in September 2017 on the MDT forum because an attempt to deploy a Windows Server 2012 R2 image resulted in an error: FAILURE ( 5615 ): False: Boot Drive was not found, required?

I asked the user to upload his BDD.log of a failed OS deployment. After receiving the log a short time later, I opened it and scrolled down to the last error message:

image

It showed that the LTIApply script could not detect any boot drives followed by the generic error message Litetouch deployment failed, Return Code = -2147467259 0x80004005.

This information indicated that while MDT could successfully apply the OS image, an attempt to write BCD entries failed. My assumption, therefore, that the issue was being caused the Format and Partition step. I examined the log to see how diskpart configuration looked like. This is where the log file was essential: it showed that the OS partition size was almost hitting 4 TB.

image

I also saw that the system was configured to use legacy MBR style partitioning as indicated by the value of the IsUEFI property:

 Property IsUEFI is now = False

It’s unfortunately still not widely known that when using MBR style partitioning there is a Windows Storage limit of 2TB. Funny story: I am still seeing customers using legacy BIOS configuration for OS deployment and I wish they would stop rather sooner than later (as a matter of fact, Intel plans to remove legacy support from new client and server platforms by 2020). Like many other technologies designed several decades ago (the first BIOS implementation was invented by Gary Kildall in mid-seventies), it's naivete is staggering when viewed through modern eyes. UEFI offers superior user experience as well as a wide range of security features such as Secure Boot, Signed Capsule and so on. This led me to the recommendation to reconfigure the server in question to use a GPT (Guid Partition Table) configuration (albeit using a smaller partition would have worked in theory). The user verified the suggestion and confirmed that the issue was solved.

Read 6062 times Last modified on Monday, 14 May 2018 20:16
  1. Comments (0)

  2. Add yours
There are no comments posted here yet

Leave your comments

  1. Posting comment as a guest.
0 Characters
Attachments (0 / 3)
Share Your Location

Recent Posts

  • An alternative ESU MAK Activation Solution
    This blog post was shared with me by a colleague of mine, Daniel Dorner, a Microsoft Premier Field Engineer. It’s…
    Written on Wednesday, 04 December 2019 21:04
  • The Case of Missing UE-V Templates
    My customers often deal with unexpected Windows behavior and this case is no different. This particular one is especially interesting…
    Written on Tuesday, 03 September 2019 12:20
  • The Case of Corrupted Store Apps
    A few days ago I began experiencing issues with built-in Windows apps where various apps would flash open and close…
    Written on Wednesday, 14 August 2019 13:36
  • The Case of Changing Default Printer
    While I sometimes long for the day when I no longer have to deal with unexpected Windows 10 behavior, there’s…
    Written on Wednesday, 14 August 2019 20:36
  • Windows 10 1903: Useful Resources for IT Professionals
    Windows 10, version 1903 is now available via Windows Update for Business, Windows Server Update Services (WSUS) and the Volume…
    Written on Friday, 07 June 2019 11:21
  • Windows 10 1903 Built-In Apps: What to Keep
    The development of the Windows 10, version 1903 is finished and the update is now available for download from Visual…
    Written on Monday, 03 June 2019 06:59