<div>
Sounds like you had a 4-disk configuration. &nbsp;When 2 disks go bad in a 4-disk or 5-disk configuration the result can indeed become unrecoverable. &nbsp;A better choice for business use is RAID 6 which will tolerate two disk failures. &nbsp;RAID 10 would also be a possibility.<br />
<br />
The thing about RAID sets is that they are usually installed with drives all purchased at the same time. &nbsp;When the first drive failure occurs there is often another failure coming along right behind it so it is necessary to deal with RAID failures expeditiously.<br />
<br />
In this situation I would replace the failed drives, relink the RAID set, then restore from the most recent full backup. &nbsp;(Always remember that RAID is not a panacea; there must still be periodic full image backups.) &nbsp;At that point you can decide whether to restore from the system state snapshot.
</div>


<div>
I already replaced the drive that failed. I can get to the OS via recovery DVD but repairing the BCD files fail. I'm stuck on trying to restore via system state. We don't have &nbsp;BMR backup. It is only System State. It won't let me restore via System State because its via the cmd prompt in the recovery DVD which is not allowed apparently.
</div>


<div>
<div class="content wysiwyg-content">
I'm having an issue where we cannot get any repair methods to work at all. We had a RAID 5 failure with Disk 1 failing and Disk 0 forcing itself offline. I forced Disk 0 online and then replaced Disk 1 with a new disk and allowed it to rebuild. However, the OS (Windows Server 2012 R2 Datacenter) became corrupted. Anytime I load the OS, I get a Boot Data Configuration error 0x00000f<br />
<br />
I tried running all sorts of bcdedit and bcdboot style commands to try to fix the boot files. via cmd line with the recovery DVD. Literally, nothing we tried working. It became a frustrating experience.<br />
<br />
We turned to DPM 1801 which has a System State backup. We wanted to restore with that. However the wbadmin start systemstaterecovery didn't work because &quot;its not supported in WinRE environment&quot;. If I try wbadmin start sysrecovery, it tells me it can't find the backup. Do I have to blow up the OS, re-install the OS, and then run the restore? Sounds redundant.
</div>
</div>


I'm having an issue where we cannot get any repair methods to work at all. We had a RAID 5 failure with Disk 1 failing and Disk 0 forcing itself offline. I forced Disk 0 online and then replaced Disk 1 with a new disk and allowed it to rebuild. However, the OS (Windows Server 2012 R2 Datacenter) became corrupted. Anytime I load the OS, I get a Boot Data Configuration error 0x00000f

I tried running all sorts of bcdedit and bcdboot style commands to try to fix the boot files. via cmd line with the recovery DVD. Literally, nothing we tried working. It became a frustrating experience.

We turned to DPM 1801 which has a System State backup. We wanted to restore with that. However the wbadmin start systemstaterecovery didn't work because "its not supported in WinRE environment". If I try wbadmin start sysrecovery, it tells me it can't find the backup. Do I have to blow up the OS, re-install the OS, and then run the restore? Sounds redundant.

Need to either fix broken OS or restore System State from DPM but having issues with both

Data Protection Manager (DPM)

Operating systems perform basic tasks, such as recognizing input from the keyboard, sending output to the display screen, keeping track of files and directories on the disk, and controlling peripheral devices such as disk drives and printers. For large systems, the operating system makes sure that different programs and users running at the same time do not interfere with each other. The operating system is also responsible for security, ensuring that unauthorized users do not access the system. Operating systems provide a software platform on top of which other programs, called application programs, can run.

Operating Systems

restores

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.