Windows raid 5 resyncing progress

Some quick math would indicate that, at this rate, the entire resync will take about a month! I simply can't believe that's correct; I'm assuming something is wrong. I don't have much experience with Win7 mirrored volumes, so I'm hoping someone has some insight.

Hardware RAID is not an option. Any ideas? Thanks for the detailed reply! I think the issue was likely due to a Windows Update-related reboot as you suggested; I think the system was automatically rebooted due to an update shortly before I noticed the resyncing. Assuming this is the case, it's a mystery why Microsoft hasn't fixed it yet. I eventually gave up, crossed my fingers, and just rebooted the system.

When it came back up it appeared to have already started the resync process on its own. I was initially disappointed as it had started over from the beginning; however, I then noticed it was resyncing much faster.

The Performance Monitor similarly showed much faster read and write speeds, and within a few hours the percent complete status indicator was already well into the double-digits. Now that you understand how storage resync works, let's look at how this shows up in Windows Server We have added a new fault to the Health Service that will show up when your storage is resyncing.

This is a new fault in Windows Server , and will appear in PowerShell, in the cluster validation report, and anywhere else that builds on Health faults. Notably, Windows Admin Center uses Health faults to set the status and color of cluster nodes. So, this new fault will cause cluster nodes to transition from red down to yellow resyncing to green up , instead of going straight from red to green, on the HCI Dashboard.

By showing the overall storage resync progress, you can accurately know how much data is out of sync and whether your system is making forward progress. When you open Windows Admin Center and go to the Dashboard , you will see the new alert as follows:. If you navigate to the Servers page in Windows Admin Center, click on Inventory , and then choose a specific server, you can get a more detailed view of how this storage resync looks on a per-server basis.

If you navigate to your server and look at the Storage chart, you will see the amount of data that needs to be repaired in a purple line with exact number right above. This amount will increase when the server is down more data needs to be resynced , and gradually decrease when the server comes back online data is being synced.

When the amount of data that needs to be repair is 0, your storage is done resyncing - you are now free to take a server down if you need to. A screenshot of this experience in Windows Admin Center is shown below:.

As you can see, this alert is particularly helpful in getting a holistic view of what is happening at the storage layer. It effectively summarizes the information that you can get from the Get-StorageJob cmdlet, which returns information about long-running Storage module jobs, such as a repair operation on a storage space.

An example is shown below:. This view is a lot more granular since the storage jobs listed are per volume, you can see the list of jobs that are running, and you can track their individual progress.

When the server came back online, the status was "resynching," so I assumed that everything was going well, and if I watched it long enough that the percent completed would appear there, too. I left it overnight and it still just says "resynching. It still just says "resynching," and "reactivate volume" is still valid in the context menu.

Sounds like a hardware issue. I would recommend contacting your hardware vendor. Also, keep in mind that initial sync can take some time. Firstly, if it's a hardware issue, then wouldn't there be something in the event log? When a disk fails, or a controller stops responding, there is definitely an event. There is no warning icon next to any of the drives indicating a bad block or anything like that.

Secondly, there is no hardware vendor to contact because I built this server. The drives all test OK, and the controller tests OK, so contacting those vendors won't get me anywhere. You should contact RAID controller or hard drive manufacturer. They can provide with to some vendor specific diagnostic tools. Could it be that you're using consumer drives instead of enterprise drives?