Stop c00002e2 after DCPromo in VM with Server 2008 R2 RTM
- I have installed Server 2008 R2 RTM in a virtual machine, running in an installation of Server 2008 R2 RC with Hyper-V.
It seems to run without problems, using two virtual CPU's and two GB of memory. In fact, this server has the smallest number of events shown in Administrative Events of any of my machines.
I can join the domain and I can install roles such as DNS or File Services without problems. I can also add the role of Active Directory Domain Services without error. When I run dcpromo, either command line or from the MMC console, it also seems to complete without error. But after the obligatory reboot, I am faced with the listed BSOD in the VM Connect window. The complete error message is as follows:
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.
There are no events after "The Event log service was stopped", until the boot to DS restore mode.
I can run dcpromo /ForceRemoval with no problems and the VM will boot and run normally afterwards.
The VHDs are on a BIOS supported RAID 1 mirror on an AMD AHCI Compatible RAID Controller. The VHD for the server is 60GB, fixed size. I also have two other VMs, running Windows 7 (RC & RTM), which seem to run very well.
I also have file shares on the host on this mirror which seem to be fine.
Could this possibly be due to a driver problem on the Hyper-V server, even though the VHD shows up as a "Virtual HD ATA Device"?
Answers
- The problem does seem to be the SATA driver.
I "updated" the driver to an older version. In the SATA BIOS setup, I deleted the array and redefined it.
After Windows loaded, I partitioned and formatted the new drive. I used a slow format to thoroughly exercise the array. It took over 24 hours.
After that, I created a new VHD and VM and installed Server 2008 R2 RC this time. I have enabled the ADDS and File Services roles. Dcpromo completed without error.
It seems to be a success. I have seen no ESENT errors or warnings, or any other indications of problems with this array.- Marked As Answer byVincent HuMSFT, ModeratorMonday, November 02, 2009 6:32 AM
All Replies
- I think I'll try it again and see if I can delay the reboot. I better check my metadata first.
Hi Brian,
I recommend that you update the Hyper-V host machine to the RTM version of Windows Server 2008 R2.
By the way, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Hope the issue will be resolved soon.
Vincent Hu
- Marked As Answer byVincent HuMSFT, ModeratorFriday, October 23, 2009 7:14 AM
- Unmarked As Answer byBrian Borg Friday, October 23, 2009 11:24 PM
- I think my install ISO might be corrupt.
Now my other 08R2 RTM virtual machine is acting up.
I hesitate to upgrade my servers with Hyper-V to the RTM. They are working reasonably well. - No, the ISO is ok. I downloaded the DVD again, this time with the DL Manager.
Fc /b shows there is no difference with the one I downloaded in August.
I also downloaded the Evaluation VHD image. Maybe I'll have better luck with that.
It boots with no problems. I enabled the ADDS role, and am currently trying dcpromo (again).
My first two attempts failed. Hi,
What did you mean by “My first two attempts failed”? Have you succeed to finish the dcpromo in new downloaded VHD image?
Vincent Hu
Vincent, thanks for your reply.
I tried various options in the dcpromo wizare, by using the back button.
My first two were "let the wizard chose a replication partner" and specifying a partner.
On the third attempt, I tried Install From Media, even though the IFM export was two days old. The wizard took it and I let it chose the replication partner it still needs.
This time, it completed. Not only that, but it survived the first reboot. I checked the logs, and the mmc AD console and it seemed to be working. But Windows Update now had problems. It refused to open, displaying an error.
I thought a reboot might solve the problem, but unfortunately it would not boot except in DS restore mode. The EDB.log for ntds.dit was now corrupt. I played with trying to fix it to no avail.
I think the problem might be the SATA RAID mirror, as supported by the BIOS and the AMD RAID driver. Now that I know what to look for, I see significant messages in the event log on the host server, such as ESENT events 454, 465, and 472, in the DFSR databases. If ESENT has problems keeping it's log files on this array on the host, it is not surprising that it has the same problem in clients using VHD's on the array.Hi,
You may try to store the VMs on a single disk to test whether it works.
By the way, for the DCpromo issue, I recommend that you initial a post in Directory Service related forum so that you can get the most qualified pool of respondents. Thanks for your understanding.
Vincent Hu
- The problem does seem to be the SATA driver.
I "updated" the driver to an older version. In the SATA BIOS setup, I deleted the array and redefined it.
After Windows loaded, I partitioned and formatted the new drive. I used a slow format to thoroughly exercise the array. It took over 24 hours.
After that, I created a new VHD and VM and installed Server 2008 R2 RC this time. I have enabled the ADDS and File Services roles. Dcpromo completed without error.
It seems to be a success. I have seen no ESENT errors or warnings, or any other indications of problems with this array.- Marked As Answer byVincent HuMSFT, ModeratorMonday, November 02, 2009 6:32 AM
