2022 failover test fails BSOD

Bright_Admin 1 Reputation point
2022-02-09T18:59:23.397+00:00

When running failover testing in Azure Site Recovery the server fails to boot with a request to run the repair. I saw there is a similar issue with 2019 after a Feb update that was supposed to have been fixed in May but wanted to confirm if this was the same thing?

https://splitbrain.com/windows-update-azure-site-recovery/

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
641 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. SadiqhAhmed-MSFT 38,401 Reputation points Microsoft Employee
    2022-05-09T07:58:44.687+00:00

    @Bright_Admin Thank you for your patience!

    "Sharing the solution with broader community"

    The original issue seems to be related with AD

    Active Directory server performing Instant VM job, the Instant VM fail to boot and a blue screen displays with the following message:

    STOP: c00002e2 Directory Services could not start because of the following error: a device attached to the system is not functioning. Error status: 0xc0000001.

    Solution

    To resolve this issue:

    1. Power on the Instant VM.
    2. When the machine is powering on, press F8 before the OS begins to load and choose the Directory Service Restore mode.
    3. Rename all *.log files in the folder, C:\Windows\NTDS. For example, rename the file edb.log to edb.log.old
    4. Run the command:

    esentutl /p "C:\Windows\NTDS\ntds.dit"

    1. Restart the system.

    If the response helped, do "Accept Answer" and up-vote it

    0 comments