Windows 10: Parity Raid Error but all Physical drives are OK

I have a RAID configured in Microsoft Storage Spaces, it's a Parity RAID with 3 different hard drives outside of my main drive that the OS sits on. I recently lost access to the RAID, when I go to look at the Storage Pool, I can see the 'Storage Spaces' Section says 'Error Reduced resiliency; check the Physical drives section' next to my RAID.When I check the 'Physical Drives' section, the health for all 3 hard drives shows as green, and they all say 'OK' so to me it doesn't seem like any of the drives have failed?Back on the 'Storage Spaces' section there is a 'Bring Online' Option, which I c

:)

 

Storage Spaces Parity Repair?

Hi: I'm a newbie here... using an OWC Thunderbay 6 DAS with Thunderbolt 3 for video/photo files using (Win 10 Home) Storage Spaces for the past 6 weeks without problems. Using Parity option in Storage Spaces to emulate RAID 5 protection.

Today, got Parity Error in Manage Storage Spaces, though all 6 drives show "OK". Both Hard Disk Sentinel and CrystaDiskInfo also show normal drives. No pertinent drive events in Event Viewer.

From reading other posts from folks with Storage Spaces issues, I'm inclined to "repair" this parity error if possible, and then consider migrating to DrivePool to avoid repetition or other future issues with SS. Can anyone walk me through how to do a parity repair?

If not doable, then can someone detail a step-by-step process for migrating my 24Tb currently on Storage Spaces to Drivepool? Many thanks!

 

RAID-3 on the cheap -- is it possible?

Hi, Ganesh,

Can you name one? A URL would do.

I'm sure you mean RAID-5.

Yes, you have it right.

What I'm looking for is a RAID-3 driver that compresses the parity drive on-the-fly on write, and expands the parity drive on-the-fly when (if) the RAID must be rebuilt. Do you know of such a driver? ... It would mean that the parity drive would only need
to be half the size of the drives that make up the RAID-0.

 

Storage Spaces Parity Repair?

Many thanks, muchomurka!

- - - Updated - - -

Unfortunately, following your suggested procedure it appears the Storage Spaces parity error persists.





Any other suggestions?