Windows Server 2008 R2 Standard - Stop C00002e2 error after Acronis Backup 11.5 restore

As much relevant info as I can think of:

Major recovery problems on Windows Server 2008 R2 Standard - this particular server is a new environment to me. This guy had the server custom built bought from a client who works in IT. RAID 1 array has C: drive for OS and a P: drive for storing data, but both C and P are on the same RAID 1 array.

After an unexpected system power down, we arrive to find the client had broken the power button so we swapped the reset and power buttons, then on boot we were seeing an temp error on CPU, but no matter if you JUST booted or ran for a few hours, it's always 84deg (F) so I think it's misreporting - we told the BIOS to ignore CPU temp for now.

Meanwhile, RAID 1 array fell apart, system stopped booting, constant reboots. One of our techs ran a CHKDSK /F on the array and it found/fixed several errors, BUT we ended up with no P: drive able to be found anymore. Just "Unallocated Space" where the P: drive used to be.  Probably thanks to the CHKDSK?

Anyway, with these developments, I decided to remove the RAID array and replace with two new hard drives and NOT do RAID - I just was going to restore C: to one drive and P: to another using Acronis Backup and Recovery 11.5. I feel like this is where it got hairy. When restoring the data that was previously 2 partitions on one drive, there is an MBR for both C: and P: so I check the box for MBR 1 and 2 to restore and for Disk 1 and 2 to restore and assign them all to the appropriate disks. (after you see the error I get, maybe I should've only restored the MBR for C: drive and restored P: drive data to second drive? i don't know......)

Upon reboot, you load up, see a black screen and the cursor arrow in the middle of the screen for a few minutes, and then blue screen. After disabling auto restart, I see it says "STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. Error Status: 0xc0000001. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information."

So I boot into DSRM and followed instructions found here to check the disks and make sure they are assigned correct drive letters. They are both C: and P: in DSRM just as they should be....

My next best guess is maybe the Intel Rapid Storage Software that runs when you boot into windows that tells you the status of your RAID array and if it's degraded, it attempts to rebuild and report the status to you. I mean, I'm not even getting to CTRL + ALT + DEL screen in normal mode so I can't really tell...

Where should I look in DSRM mode to get more info and fix this? Event viewer? Device Manager? This is a real puzzle to us. Thanks for your insight, guys
Who is Participating?
noxchoConnect With a Mentor Global Support CoordinatorCommented:
There are many guides on treating this problem. I was asking for system state backup because it is required when you restore the domain backup to the same machine again. I am familiar with Acronis and other backup software but still they are not Microsoft built backup tools and sometimes additional system state backup & recovery is required.
Check these links:
S00007359Cloud Engineering OfficerCommented:
when u did the restore, did u use the option to perform a restore using the Universal recovery mode.

also, when u have restored, have u changed the partition labels or drives names to how it actually was.

did u also has a recovery partition on the raid?
S00007359Cloud Engineering OfficerCommented:
is this case, it appears that the disk are not initialised, or brough tonline.

when u get into DSRM mode , get into Device Manager, Disk Management and check if the disk are online, or initialised!, then reboot it.
fecklessnessAuthor Commented:
thanks for replying. no i did not do universal restore mode. i did not change partition labels or drive letters compared to how it was.

how would i check that they are "initialized" as you put it? according to these instructions that makes no sense for me, because i went in to DSRM, Server Manager> Storage> Disk Management> and saw they had drive letters assigned same as they were before (C: and P:), were allocated correct space, it said "active, primary partition" and some other things - what more should i be looking for? i'm at home now, not at the office so i can't dig into this immediately, just thought i would reply while someone was looking at this. thanks
S00007359Cloud Engineering OfficerCommented:
okay, so i see, on aanother server, u will see that there is a system partition, called system reserve! this partition needs to be restored first!

1.In general, System Reserved partition should be selected when restoring system disk

The basic process is:
 1. Restore the System Reserved partition to the disk first,
2. Restore the boot partition (with Windows install)
3. Restore any other data volumes.

see here:
noxchoGlobal Support CoordinatorCommented:
Indeed, you drives are initialized. As you pointed it already they are formatted and having drive letters assigned. IMHO the problem is caused by Active Directory. It detected that hardware has been changed and thus refuses to run from this new configuration. Have you taken system state backup as well?
Since you have an Acronis backup all you need to follow the steps below. With my all respect to others.
1- I assume you finished RAID config and have run the consistency check patiently.
2- Put the Acronis cd and boot with it.
3- Go to Navigation menu and delete all partition and commit the task. This wil remove all partitions from your RAID volume and you will have unallocated drive. Attach your backup source (usb external or where ever your .tib file is)
4- On the destination section select your RAID volume and add all partitions from your backup one by one.
Note: If you are restoring the backup to the same machine please Go to step 6
5- If you are restoring to a different hardware choose Universal Restore option from drop down menu. (If you did not purchase this module separately, it will not be visible anywhere on the screen)
6- Hit the restore button and allow it to  automatically generate a new unique NT signature.
After recover and reboot, your machine will;
a)show you Ctrl+Alt+Screen, if its the same hardware
b)ask you drivers for the new hardware
fecklessnessAuthor Commented:
S00007359 - you are off base with the "System Reserve Drive" and same for noxcho - I do not need an additional system state backup with Acronis. It's a full image of each disk, with all partitions, MBR, etc. If you are familiar with Acronis, you know what I'm talking about.

teomcam - The server was using RAID0. I am using the same hardware so Universal Restore is not required. Also AD should not be thrown off because it's the same exact configuration, just new hard drives. Since RAID0 was not working, we have now tried changing to IDE turning off RAID, using single drives to restore C: and P: to, it stripped all drivers using Acronis Universal Restore and STILL gave the same reaction of a black screen with arrow cursor, then C00002e2 error.

So it's definitely something with AD, but what could it be? Like I said, same hardware setup! I'm baffled! Would something being wrong with the motherboard cause an issue like this.
fecklessnessAuthor Commented:
I noticed the IT guy who sold this to him did setup a Windows System Backup to go to a separate partition, it's in VHD format. Maybe this has system state backed up in it, how would I go about checking?

I will complete current restore I am working on and login to DSRM and report what error messages it gives on booting into normal mode from the Event Log. I'll try to see if anything is relevant from either of the two links you posted, noxcho. Thanks for the input so far.
fecklessnessAuthor Commented:
noxcho - - that article makes no sense because no admin attempted to remove the DirectoryServices-DomainController role so that can't add to this dialogue as I see it. going to follow through on the other article now.
fecklessnessAuthor Commented:

That article solved it. The results didn't exactly mirror the guide, seems like the NTDS.DIT needed repair. That did it! THANKS!!!!
noxchoGlobal Support CoordinatorCommented:
Glad to hear it helped.
Take care
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.