Forgive me if this is posted in the wrong location, this is my first post. I rarely have to turn to others to find a solution to a problem but this is something I have not been able to solve.
I have an HP Proliant 160 (G2) that had 4 aging 1tb drives in raid 1+0 (2tb) I decided to upgrade them to 4x 4TB drives to increase storage space and access speed. I usedWindows Server backup, backed up to an external USB 2tb drive using the bare metal backup option, booted to the Windows 2008 R2 setup disk, and ran the "repair your computer" and was able to finally successfully restore the backup to the new drives. I had issues with the restore process, sadly our drive was setup as a basic disk and it could not be converted to dynamic since it was a boot volume. But at this point I just need the server back online. The restore process finished (took 12 hours) and it restarted itself. All appeared to be restored perfectly but now no one can login to the server and I have not the faintest as to why. The server was offline for maybe 24 hours in total.
The typical error message shown to desktops who were connected to our child domain is "There are currently no logon servers available to service the logon request". We can ping the domain xxxx.xxxx.net and get responses.
When I attempt to join the domain from a computer that is not currently attached I am getting the below error output. I'm considering putting in the old drives but in order to do that, I will need to reconfigure the HP 212 raid controller to see those drives, and I am afraid that if I remake the configuration in the raid array that it will simply blank the drives and wipe the old data right off there when the raid configuration is saved. Just hooking them back up results in a failure to boot, the server is configured for the new drives now.
"Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "xxxx.xxxx.net":
The query was for the SRV record for _ldap._tcp.dc._msdcs.xxxx.xxxx.netThe following domain controllers were identified by the query:
xxxx-2011.xxxx.xxxx.net
xxxx-xxxxxx.xxxx.xxxx.net
However no domain controllers could be contacted.
Common causes of this error include:
- Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or are not running."
