RAID Stripe Consistency Check Failed – Fix It Now
This error pops up when your RAID controller finds data mismatch across stripes. It's often from a failed drive or bad cable. Here's how to fix it.
When This Error Shows Up
You’re running a server or workstation with a hardware RAID controller — maybe an LSI MegaRAID, Adaptec, or a Dell PERC. Everything’s fine until your server logs show “RAID stripe consistency check failed” or the RAID management software throws that error during a patrol read or consistency check. It often happens after a drive replacement, a power outage, or when you’ve mixed drive brands in the same array.
What’s Really Going On
RAID (especially RAID 5 or RAID 6) stores data in stripes across multiple disks with parity. A consistency check reads everything and compares the parity against the data. If a mismatch shows up, it means at least one stripe isn’t consistent — data might be corrupted or a drive wrote bad data. This can happen if a drive dropped offline and came back, if a cable is loose, or if a drive is starting to fail but isn’t dead yet.
Don’t ignore this. A single bad stripe can spread corruption during a rebuild. The fix depends on whether the array still has redundancy.
Step-by-Step Fix
I’ve walked through this with dozens of people. Here’s what works.
Step 1: Check Drive Health
Open your RAID management tool — MegaRAID Storage Manager, Adaptec Storage Manager, or Dell OpenManage. Look at each drive’s status. If any drive shows “Predictive Failure”, “Bad”, or “Unconfigured Bad”, replace it before you do anything else.
Step 2: Verify Cables and Connections
This tripped me up the first time too. A loose SATA cable or a partially seated SAS connector can cause intermittent errors. Power down the server, reseat all drive cables and backplane connections. Also check power cables to drives. A drive that loses power mid-write will leave a bad stripe.
Step 3: Run a Consistency Check With Repair
Most RAID controllers can fix mismatches by rewriting parity or data. In your management tool, find the “Consistency Check” option for the virtual disk. Choose “Repair” or “Correct Errors”. Let it run — it might take hours for a large array.
Example for MegaRAID using storcli:
storcli64 /c0 /v0 start consistency check repairStep 4: If Repair Fails
Sometimes the repair itself fails because the stripe is too corrupt. In that case:
- If the array is RAID 1 or RAID 10, you can break the mirror and rebuild. Back up first.
- For RAID 5 or 6, try a
fsck(Linux) orchkdsk(Windows) on the volume AFTER the consistency check completes, even if it reports errors. This fixes filesystem corruption. - If the array won’t come online, you may need to restore from backup.
Step 5: Update Firmware and Drivers
Old RAID controller firmware can cause flaky consistency checks. Check your hardware vendor’s site for the latest firmware. Also update your management software. I’ve seen a firmware update fix a recurring stripe error overnight.
If It Still Fails
If the error keeps coming back after a repair and drive replacement, suspect the RAID controller itself. Try moving the drives to a spare controller if you have one. Also check the backplane — a bad backplane can corrupt data on all drives. In rare cases, a buggy controller firmware revision has a known issue with certain drive models. Search your controller model plus “stripe consistency check failed” on forums.
And remember: this is a warning sign. If you don’t have a recent backup, make one now. Your array might be telling you it’s on its last legs.
Was this solution helpful?