RAID Array Offline and the Business Down? Stop — Don't Rebuild.
UK emergency RAID data recovery since 2002. Multiple drive failures, aborted rebuilds, controller faults — all RAID levels and controllers. Same-day collection for emergency cases, 24–48 hour emergency turnaround. Free diagnosis and a fixed-price quote before any work starts.
What this means and what to do next
An offline RAID array is almost never a total loss — but it is a situation where the next action taken decides the outcome. RAID 5 and RAID 6 arrays go offline when the number of failed member drives exceeds what the parity scheme can absorb: two drives in a RAID 5, three in a RAID 6. In practice the second ‘failure’ is often not a dead drive at all, but a drive the controller dropped weeks earlier without anyone noticing, or one with a handful of unreadable sectors that the controller hit during a rebuild.
That distinction matters, because it means the raw data is usually still present across the member drives. What has been lost is the controller's willingness to assemble them. The lab approach is to take the controller out of the equation entirely: image every member drive sector-by-sector on hardware imagers that tolerate bad sectors, then reconstruct the array virtually from the images — stripe size, disk order, parity rotation and offset — without ever writing to the originals.
The cases that arrive unrecoverable are almost always the ones where someone kept trying things first: repeated rebuilds, drives moved between bays without labelling, configuration cleared and re-created, or recovery software run against the degraded array overnight. If the data matters and the business is down, the fastest safe route is also the simplest one: stop, power down, and get the drives to a lab. Our emergency data recovery service exists for exactly this scenario.
The four most common reasons a RAID array goes offline
1. Second drive failure during a rebuild. Symptom: one drive failed, a replacement was fitted, the rebuild started — then stopped at some percentage and the array went offline. Cause: a second member drive has latent unreadable sectors, and the rebuild's full-surface read found them. Recovery: image all original members including the partial rebuild target, then reconstruct virtually using parity to fill the gaps. This is the single most common emergency RAID case we see.
2. A stale drive nobody noticed. Symptom: the array reports two failed members, but one of them ‘failed’ weeks or months ago. The array had been running degraded ever since, and the recent failure took it offline. Recovery: the stale drive's data is out of date and must be excluded or used only for the sectors that never changed — which is why forcing all drives back online corrupts files. Correct member selection during virtual reconstruction is what separates a clean recovery from a damaged one.
3. Controller or backplane failure. Symptom: several drives drop simultaneously, or the array configuration vanishes after a reboot or power event. The drives themselves are usually healthy — the controller, backplane or expander has failed, or the controller's stored configuration is corrupt. Recovery: image the drives on independent hardware and reconstruct from the RAID metadata each drive carries. The original controller is not required.
4. Power event mid-write. Symptom: after a power cut or failed UPS, the array comes back degraded or offline, or mounts with a corrupt filesystem. Writes that were in flight — including the controller's write-back cache — never completed, leaving parity inconsistent. Recovery: reconstruct the array from images, then repair the filesystem on top of the reconstruction, choosing the parity interpretation that yields consistent data.
How Data Clinic handles an emergency RAID recovery
It starts with a triage call. We'll ask what the array is (controller model, RAID level, number of drives, capacity), what the failure looked like, and — critically — what has been tried since. From that call we can usually tell you whether the case is suitable for the emergency service and what the realistic outcome is, before anything is shipped. The diagnosis is free and the quote is fixed before any recovery work starts.
For emergency cases we arrange same-day courier collection from any UK address — the whole server, or just the drives, labelled by bay. Work starts as soon as the media arrives at our Bury, Manchester lab: every member drive is imaged in parallel, mechanically failed drives go through our hardware-repair bench first, and the array is reconstructed virtually from the images. Your original drives are never written to.
Once the virtual array mounts, we verify the data that matters most to you first — databases, virtual machines, shared folders — and deliver the recovery on new media. The emergency service targets a 24–48 hour turnaround; Priority (2–5 days) and Standard (5–20 days) tiers are available where the pressure is lower. More on our RAID data recovery service →
Get a free initial diagnosis in 60 seconds
In the tool below, choose RAID/NAS/Server and the symptom closest to what you're seeing — array offline, multiple failed drives, or rebuild aborted. Emergency cases are routed straight to our RAID recovery team.
What our customers say
"Three years of family photos on a drive that suddenly failed. Data Clinic collected next day, kept me updated through the cleanroom work, and got everything back. Worth every penny."
"Honest, fixed-price, no-fix-no-fee. Quoted by another lab at three times the price. Recovered 100% of my files."
"Reasonable cost, clear communication, and they were straight with me about what was recoverable and what wasn't. Recommended."
Frequently asked questions
How quickly can you recover an offline RAID array?
The emergency service targets 24–48 hours from the media arriving at the lab, with same-day courier collection from any UK address. Whether that target is achievable depends on the condition of the drives — mechanically failed members that need donor parts can extend it, and we will tell you on the triage call rather than after collection. Priority (2–5 working days) and Standard (5–20 working days) options are available too.
Two drives have failed in my RAID 5. Is the data gone?
Usually not. In most two-drive RAID 5 failures, at least one of the ‘failed’ drives is readable in a lab — either it was dropped by the controller for slow response rather than a true failure, or its bad sectors can be worked around during imaging. With one drive fully imaged and the second mostly imaged, parity fills the gaps. The main threat to your data is not the second failure — it's rebuild and repair attempts made after it.
Should I try to rebuild the array before sending it to you?
No. A rebuild writes to the array, and if it aborts — which it will if any surviving drive has unreadable sectors — the array is left partially overwritten. The same goes for forcing drives online, re-creating the configuration, and running filesystem repair tools. Power the system down and leave it down; that alone protects everything a lab can recover.
Do you need the server and controller, or just the drives?
Usually just the drives, labelled with their bay positions. We reconstruct the array from the drives' own RAID metadata, so the original controller isn't needed. If it's easier to send the whole server — or you're not comfortable removing drives — our courier collects the complete unit. Collection is free either way.
What does an emergency RAID recovery cost?
Every case is quoted individually after the free diagnosis — the drive count, failure mode, turnaround tier and the amount of mechanical work involved all affect it. The quote is fixed before you approve any recovery work, so there are no surprises at the end.