drewster
New Member
- Reaction score
- 0
- Location
- Washington State
We recently ran across an unusual problem that I wonder if anyone else has seen. Also, would love to hear some suggestions if someone has an idea for a more elegant solutions.
Specifications of PC.
Core i5 1155 CPU
2x1TB Seagate SATA Hard Drives (RAID1 Mirror using integrated Intel RAID controller)
Windows Server 2008 Standard
One of the RAID drives failed. Went ahead and installed a brand new 1TB Seagate drive in its place. Windows booted fine and was able to start the rebuild in windows. All looked pretty straightforward up until this point.
A few days go by and the server reboots after a scheduled Windows Update and the system will no longer boot into normal mode, and just gets a quick BSOD and restarts.
The BSOD is:
STOP: c00002e2 Directory Services could not start
Similar to this: http://martijnwestera.blogspot.com/2013/01/stop-c00002e2-directory-services-could.html
Because this server was critical to doing business, the only quick working solution that we found was to set the disks to non-raid, and just let it boot up temporarily on the original 1TB drive standalone, and things were fine.
During the weekend we had more time to try a few other things. Went ahead and cloned the working image into a brand new 2x1TB array with two completely new and different drives, but had the same blue screen.
Finally found this article that described the situation almost perfectly. It was an issue with going from 512 byte sectors to 4KB.
http://support.microsoft.com/kb/2470478/en-us
This made sense, since the original drives were 512 byte, and the new drives were 4KB.
However, even after applying the patch the Blue Screen remained.
We eventually used two 500GB 512 byte disks to replace the 1TB drives and that worked like a charm.
The plan will be to add two new larger drives to the server for a separate mirror where we can start storing data as the 500GB useable space isn't going to work in the long term.
Specifications of PC.
Core i5 1155 CPU
2x1TB Seagate SATA Hard Drives (RAID1 Mirror using integrated Intel RAID controller)
Windows Server 2008 Standard
One of the RAID drives failed. Went ahead and installed a brand new 1TB Seagate drive in its place. Windows booted fine and was able to start the rebuild in windows. All looked pretty straightforward up until this point.
A few days go by and the server reboots after a scheduled Windows Update and the system will no longer boot into normal mode, and just gets a quick BSOD and restarts.
The BSOD is:
STOP: c00002e2 Directory Services could not start
Similar to this: http://martijnwestera.blogspot.com/2013/01/stop-c00002e2-directory-services-could.html
Because this server was critical to doing business, the only quick working solution that we found was to set the disks to non-raid, and just let it boot up temporarily on the original 1TB drive standalone, and things were fine.
During the weekend we had more time to try a few other things. Went ahead and cloned the working image into a brand new 2x1TB array with two completely new and different drives, but had the same blue screen.
Finally found this article that described the situation almost perfectly. It was an issue with going from 512 byte sectors to 4KB.
http://support.microsoft.com/kb/2470478/en-us
This made sense, since the original drives were 512 byte, and the new drives were 4KB.
However, even after applying the patch the Blue Screen remained.
We eventually used two 500GB 512 byte disks to replace the 1TB drives and that worked like a charm.
The plan will be to add two new larger drives to the server for a separate mirror where we can start storing data as the 500GB useable space isn't going to work in the long term.
