Yeah, I've seen this error pop up more times than I care to count. It's frustrating as hell — you're building a RAID 5 array in Disk Management or Storage Spaces, and Windows just slaps you with 0XC038005C. The system flat-out tells you it doesn't support RAID 5 volumes. Let me save you the headache.
Direct Fix: Stop Using RAID 5 (Seriously)
The quickest fix is to not use RAID 5 at all. I know that sounds dismissive, but hear me out. This error happens because you're on a system where the storage stack can't do parity calculations properly — usually consumer-grade hardware, older SATA controllers, or software RAID without a proper driver stack.
Here's what you do instead:
- Switch to RAID 0 or RAID 1 — These are simple mirroring or striping. No parity math needed. Windows supports them natively without special hardware.
- If you absolutely need RAID 5, get a dedicated hardware RAID controller. I like the LSI/Broadcom 9260 series or a newer 9361. They handle parity on the card, not the CPU.
- For Storage Spaces, use a
Simple(RAID 0) orMirror(RAID 1) layout. Parity layout requires a certified controller or you'll hit this error.
Run this command in PowerShell to check current Storage Spaces health:
Get-StoragePool -FriendlyName "YourPoolName" | Get-StorageSubSystemIf that shows HealthStatus: Unhealthy with OperationalStatus: 5, you've confirmed it.
Why This Happens
RAID 5 requires XOR calculations across disks. Most onboard SATA controllers (Intel RST, AMD RAIDXpert) can't do this at the hardware level. They fake it with software drivers that break under load. Windows Storage Spaces detects this and throws 0XC038005C to stop you from creating a volume that'll corrupt data later.
The error code 0XC038005C maps to STATUS_VOLMGR_5_NOT_SUPPORTED. VolMgr is the volume manager component in Windows. It checks the storage stack before committing any parity-based layout. If the underlying hardware doesn't report parity support, VolMgr refuses to proceed. Smart move, actually — better than a silent failure.
Less Common Variations
Sometimes you get this error even on hardware that should support RAID 5. Here's a few edge cases I've debugged:
- Driver mismatch — You installed the wrong storage driver version. Uninstall the driver, reboot, and let Windows Update pick the correct one. For Intel RST, stick to version 16.x or newer.
- Mixed disk sizes — RAID 5 needs disks of identical size. If you mix 1TB and 2TB drives, Windows gets confused and rejects the configuration.
- Firmware bug — Some older Dell PowerEdge or HP ProLiant controllers (PERC H310, Smart Array P420) have buggy firmware that reports wrong capability flags. Update to the latest firmware from the vendor site.
- VM or container environment — If you're running Storage Spaces inside a Hyper-V VM or Docker container, the hypervisor might not pass through parity support. Use
Simplelayout instead.
Prevention for Next Time
Don't rely on motherboard RAID for anything except RAID 0 or 1. If you need RAID 5, 6, or 10, buy a proper controller. I've had good luck with Adaptec Series 8 or LSI 9300. They're not cheap, but neither is losing a terabyte of data.
Before creating any RAID volume, check the controller's spec sheet. Look for hardware XOR engine or native RAID 5 support. If it doesn't say that, assume it'll fail.
One more thing — always run Windows Storage Spaces in Simple or Mirror mode on non-server hardware. Parity is a server-tier feature. Consumer Windows 10/11 doesn't handle it well, even with modern drivers.
That's it. Skip the RAID 5 dance on budget gear. Your data will thank you.