I recovered the EFI partition from my non-Hasleo test protection image and, indeed, the DEFAULT BOOT OS directive returned as expected, BUT.
and if it was, since it's not in the image, will be basically unrecoverable. Since both the image & restore only dealt with the OS partition ('C'), the EFI partition, which contains the BCD info for an UEFI System, should not have been touched. This is not good because even if any of Brian's attempts to restore that partition at a different backup chain point, without a BOOTmgr reference to the BOOT partition, the 'maybe' properly restored OS partition would BOOT properly. Sometime during the restoration, prior to the error above, the BCD is modified in some way that makes the DEFAULT OS Partition BOOT entry disappear. I'm really not sure what support can do at this point due to Problem #2 to follow.Ģ. Once the restoration is started, old partitions start to disappear (as expected) in preparation for the partition restoration (in Brian's case) then the broken chain is discovered and you get a DATA error and a request to call SUPPORT at a given number. the application when doing a restore never checks the integrity (is the chain in tact, are the pieces basically error free, etc.) prior to starting the restoration (disk modification), not a good thing. The (2) main problems here using a broken backup chain are, basically.ġ. Click to expand.OK, repeated most of what Brian did with very similar results.
