It seems that I have run into this error again. We are testing our DR restore capabilities. Restored one of our DCs, fired it up, it boots, gets to the login screen, sits there for maybe 2-3 minutes, reboots itself, starts up again ... then hits:
STOP: c00002e2 Directory services could not start.
A device attached to the system is not functioning.
Error Status: 0x0000001
Please shutdown this system and reboot into Directory Services Restore Mode
Now we've fiddled around with the VM, rebooting it a few times, managed to get into DSRM okay, but can't get past the error. The DC VMs in question are checked monthly via a SureBackup job and its been working fine for the past 3 months.
I should also mention that the environment we are restoring in has zero functioning DCs; we're testing what happens in the event of complete systems loss.
I somehow don't think that DSRM is actually really the issue. The message "device attached to the system is not functioning" sounds like a virtual hardware issue. Anyway, when I did get the VM booted up into DSRM mode and logged in, I checked in msconfig to see if anything looked wrong. The "safe boot" option was already unchecked, so Veeam had already done its work there (?).
The backups I am restoring are about 4 months old. We've had some VMware host patches applied since then. I updated my DR servers to be running the latest ESXi v5.1 Update 3, same as my Production servers now, but I suspect that the backups were taken when we were running on an earlier version of ESXi.
Could that stop the restore process(es) working properly? (it would trouble me greatly if that were true!)
I'm going to try restoring some more recent backups now, just to see whether last nights backups give me a different result. I expect they will restore fine. Anyway, I will report back once I have more data.
I haven't logged a support ticket yet; thought I would get some informal feedback first, but will open a ticket if that's the best way to find out what's happening.