In this scenario physical server also having PDC emulator role as role was not transfer due to hardware crash. How to tackle such scenario and plan the risk mitigation?
May depend on the extent of the repairs that were done. If the operating system was reinstalled, then cleanup will need to be done before server name can be reused.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564.
I'd use dcdiag / repadmin tools to verify health correcting all errors found
before starting any
operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--