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?
@BrightAdmin-6108 Thanks for reporting this. Will check with the concerned team and get back to you soon.
@BrightAdmin-6108 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:
Power on the Instant VM.
When the machine is powering on, press F8 before the OS begins to load and choose the Directory Service Restore mode.
Rename all *.log files in the folder, C:\Windows\NTDS. For example, rename the file edb.log to edb.log.old
Run the command:
esentutl /p "C:\Windows\NTDS\ntds.dit"
Restart the system.
If the response helped, do "Accept Answer" and up-vote it
10 people are following this question.
