Can you please download secinspect.exe from Download Sector Inspector (SecInspect.exe) from Official Microsoft Download Center and save it to a temp folder on the C: drive and run the following command:- c:\temp>secinspect.exe > secoutput.txt  And upload the file here? Also let us know the physical disk number. We can check its MBR information from this output.  FYI i have seen issues in the past wherein after a poweroutage on windows server the MBR on some disks is zeroed out. it can be on physical hardware as well as on VMs. It is unrelated to ScaleIO.
Hello, we are evaluating ScaleIO on two different infrastructures: on the former architecture ScaleIO is installed on Windows 2012 R2 and on the latter on Ubuntu 14.04.  What is relevant for this post is the SDS role.  Simulating an unexpected power outage we noticed a major issue on SDS nodes installed on Windows 2012 R2 when power came back.  This is the description of the problem we noticed with SDS on windows 2012 R2.  We have 5 SDS installed on 4 different Windows 2012 R2 servers. We assigned to every SDS a 100 GB disk with GUID partition table, left unformatted with a letter assigned to it.  Here you can see as disk how the disk looks like from the windows disk manager after setup:  [IMAGE]  We simulated a power outage so all nodes lost power simultaneously. When the SDS came back we noticed that only one SDS was working correctly while the other 3 nodes were unavailable because, in particular, ScaleIO couldn't access the disks.  From the windows disk manager we noticed that the disk appears as "not initialized" and immediately a pop-up ask if we want to initialize disk (previously used by SDS). It seems that the partition table has been lost.  Here you can see as disk how the disk looks like from the windows disk manager after power outage:  [IMAGE]  With linux all the test ran smoothly, after power outage ScaleIO came back like nothing had happened.  Someone noticed some similar behaviour with ScaleIO on Windows?  Thanks in Advance, Davide
ScaleIO - SDS on Windows 2012 R2 - Problem after complete power outage 
simulation