The lab is taking new cases · 9am–5:30pm, Mon–Fri Urgent? Ring 0800 6890668
SDR Southampton Data Recovery 0800 6890668 Open a case
SDR / Harder cases / RAID 5 data recovery

Specialist · RAID 5 array recovery

RAID 5 recovery in Southampton. One drive's worth of parity. One failure allowed. Nearly always already spent.

RAID 5 can survive the loss of one member and no more, and most arrays that reach us have already used up that allowance and had a rebuild started. What the panic hides: two disks marked as failed seldom means two disks destroyed, and whatever survives can be pulled off clones without a single further write.

Only pay if we recover your data, on most jobs Free diagnosis & quote in writing Postal intake across all of Hampshire

Speak to an engineer about it
0800 6890668

What those signs actually mean.

Not listed? Try the fault finder →
The complaintWhat that tells youFirst step
A disk has failed, so the array is degradedRedundancy has been exhausted: from now on each hour of operation will be without protectionSwitch off before the second
A rebuild began and then stalledReading the entire surface hit bad sectors on a marginal surviving disk: this is the common endingHalt there; no second attempt
Two members marked as failedMore often than not it is a single really dead disk alongside another disk that contains a few unreadable sectors, which is not the same as losing both outrightQuote first, then send both in
Members forced back into the setOut-of-date disks dropped into current stripesGo no further
Array removed from list after changing the controllerThe metadata disagrees; the information below is fineA job for reconstruction
'RAID recovery' software was run against the live disksWrites landed on the evidenceTell us plainly, get a quote, then send the disks
Posting it: first, get a price quotation from us, by phone or with the form. Then send your item to us via tracked, fully insured post to our secure intake laboratory where it will be processed (we pay for return postage). Alternatively, you may also bring it to our Guildford intake laboratory Monday to Friday, 9am to 5:30pm, no appointment needed. Ring us and we would be happy to assist you with packaging, and there are postage details available on the postal details webpage.

Why rebuilds kill arrays, without the drama.

What a rebuild demandsEach sector on each of the remaining drives has to be read: approximately 48TB of continuous work on a four-drive 16TB set, through hardware as old as the member that just failed. Plainly put, that is what you are exposed to.
The URE figure, straightEnterprise disks have higher reliability specs: they are rated for about 1 unrecoverable read error per 1015 bits. That's ten times better than typical desktop (consumer) drives, which are rated for roughly 1 unrecoverable read error every 1014 bits, or 1 bad sector for every 12.5TB read. Think of this spec as a warranty minimum, not a countdown: most drives will go far beyond that mark without issues. The spec holds; the scare charts are salesmanship.
How different controllers respondThey are different. Old cards stop rebuilding as soon as they see a single unrecoverable read error (URE), but newer PERC and MegaRAID firmware will “puncture” the stripe and continue, while Linux mdadm will add it to a “bad block list”. A single unreadable sector should only cost a stripe, not an entire RAID array.
Why disk two tends to go mechanicallyOne batch, one cycle, one rack, then the endurance read of a rebuild. It is the disk that has been quietly borderline that fails when loaded with work. Cloning slowly, leaving the weak areas until last, is the way we cover all the same ground.

How the recovery runs, step by step.

01

Logged in, checked at no cost Free

Your item will have a unique case number assigned to it immediately after we receive it. An engineer will diagnose the issue, tell you what can genuinely be recovered and then provide you with one fixed price in writing. The diagnosis itself is completely at no cost to you. You are under no obligation to allow us to do any work that would incur a charge.

No-cost diagnosisQuote fixed in writingNothing to commit to
02

Clone each disk before anything else

Every single one of the disks, including the two the controller condemned, is copied completely, sector by sector. Unreadable areas are charted and fragile regions are left until the very end. Once this step is done, nothing we do can make things worse.

Every member imagedFaulty drives covered
03

Work out the array layout

The member order for the RAID set, the stripe width and how parity is rotated through the array are all extracted directly from the data and the metadata the controller wrote to the disks, so no live controller is needed and nothing is assumed.

Layout & parity worked outChecked before reassembly
04

Reassemble in software, block by block

We rebuild the entire set across the clones, with each block taken from the member that reads it cleanest and recalculated from parity for the parts no member can read, including areas that only the condemned disks still hold. The file system above is then repaired and verified.

Cleanest copy of each blockVolume mount confirmed
05

Checked, returned, signed off

Once you have the complete listing of all the recoverable files back from us, you can "sign-off" and your recovery fee becomes due. Once you've signed-off, all the files will be posted out to you on new media (with postage included) and the case will remain open until you confirm that they can be opened properly at your location.

Sign-off on the file listNew media providedReturn postage on us

First checks on the bench

  • Degraded is unprotected: once a RAID 5 has dropped to degraded, there is no tolerance left for any further failure; now there is but one disk in an array costume.
  • This fault gets sold on panic: array emergencies are among the highest paying jobs in the trade, therefore the internet is crowded with over-dramatisation about them. We offer instead factual dullness and our “clone before anything” approach.
  • A punctured stripe is a clean cut: when a current controller punctures a stripe, the damage stops at that stripe and is logged; much gentler than the old “abort everything” response and clearly visible in reconstruction.
  • mdadm shows its working: the bad-block logs and superblocks that Linux software RAID keeps spell out exactly what we inherit. Typically, the most transparent patients we encounter are software RAIDs.

The figure that actually matters: a consumer hard drive is rated for a single unrecoverable read error every 1014 bits (about 12.5TB), while an enterprise hard drive is rated for 1015. When rebuilding a four-drive 16TB RAID 5, approximately 48TB will be pulled off the surviving drives; so on paper, the risk is genuine. In practice, most disks run well beyond that floor without errors. Both claims are correct, which is why the honest response is not “never rebuild” but “do not rebuild until you have image copies”.

Out of the casebook.

EX · SDR-2026-0822SIGNED OFF ✓

A RAID 5 at an accountancy firm, seven days from year-end

The second disk failed in June and nobody noticed until the fourth dropped out in August, mid-rebuild. After imaging each of the disks, the real issue with drive four became apparent: 19 bad sectors, but the disk itself was not dead. The stripe came back from three members and a nearly whole fourth, and the practice still filed everything on time.

19 bad sectors, not 2 failed drives6 days on the bench

While it's still with you.

Do

  • Shut the array down as soon as it goes degraded
  • Label the bay order before you move any disk
  • Get a quote first, by phone or with the form, then send us every member disk, above all the ones marked as failed
  • Note the controller model and what has already been tried

Avoid

  • Start or resume a rebuild on a degraded array
  • Force your 'failed' disk back into an "online" state just to test it
  • Point recovery tools at the live disks
  • Drop in a new disk, hoping it will re-initialise and all be good again

Bench questions, straight answers.

Is RAID 5 recoverable once two drives have failed?

Yes, usually. Much of what controllers call “failure” is a small number of bad sectors rather than a dead drive, and rebuilding from images of each member means every block comes from the member that reads it cleanest. It's extremely rare to have two truly destroyed drives; most of the time you'll see two drives dropped from the array.

Is rebuilding a degraded RAID 5 the right move?

Not until you have imaged the disks in your array. A rebuild touches every sector on all surviving disks, which is exactly the strain that kills marginal drives, and it writes parity as it goes, wiping out what reconstruction would have relied on. If you image first, then that same rebuild carries no risk whatsoever.

URE — what is it, and how worried should I be?

An unrecoverable read error (URE): a sector so damaged that the drive's own built-in correction cannot save it. This is estimated at roughly one in every 12.5TB of data read on consumer drives and one in every 125TB on enterprise drives. Take it seriously, but do not panic when you see these figures. They are worst-case floor estimates, and current controllers will give up a stripe to a URE, not the entire array.

Do you need our RAID controller to rebuild it?

No. The array geometry resides on the disks themselves, held in the controller's metadata. If that gets corrupted, the patterns in the data reveal it. We rebuild arrays at the bench from the images we create and nothing else, so your original card is never needed here.

Whatever has gone wrong, keep it switched off.

Powering a damaged device up again costs you data. Start by opening a case instead; diagnosis is always free, regardless of your decision.

0800 6890668