Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / Trickier jobs / RAID 5 data recovery

Specialist · RAID 5 data recovery

RAID 5 data recovery, Brighton. One parity drive. One margin for error. Usually already spent.

RAID 5 will survive only one failed component. By the time most RAID 5 arrays arrive at our facility, there has already been a failure within the system and a rebuild attempt made. In spite of the initial panic, the reality is that 'two disks down' rarely means 'two disks dead'. All recoverable information contained within the original array can be retrieved through imaging processes with absolutely no additional writes occurring to the affected array. A Brighton RAID 5 set travels as bare disks labelled by bay, and each individual drive is first imaged prior to being combined into the original RAID 5 configuration. Get a quote first, by phone or with the form, then post the disks tracked and insured, or drop them off at our Guildford intake lab, Monday to Friday, 9am to 5:30pm (no appointment needed).

Only pay if we recover your data, on most jobs Free diagnosis & written quote Post-in from anywhere in Sussex

Talk it through with an engineer
01273 964902

What you're seeing, decoded.

Something else? Run the triage →
The problem as describedWhat it meansFirst thing we do
There was one failed drive and the array became degradedThe RAID 5 array is currently operating with zero redundancy protection and therefore every hour of use is unprotectedShut down power before the second failure occurs
Rebuild started, then failedA full surface read revealed bad sectors on a surviving drive, the typical final outcomeStop: do not retry the rebuild process
Two drives showing failedOften, one dead drive and a few bad sectors on another: very different from two dead drivesGet a quote first, then send both; images decide
Drives forced back onlineAdding stale member(s) back into active stripe(s)Stop exactly there
After swapping out a controller, the array no longer appears on the listMetadata discrepancy detected; data still present under the metadata layerRe-assembly territory
Someone used 'RAID recovery' software on the live arrayWrites on evidenceGet a quote first. Then send in the disks anyway, honestly.
Getting it to us from Brighton: get a quote first by phone or with the form. And we will walk you through packing it. Then post your device tracked and fully insured to our intake laboratory at Guildford (free return postage), or drop it off there Monday to Friday, 9am to 5:30pm (no appointment needed). Details for sending are located on the contact details page.

The rebuild problem, without the scaremongering.

What a rebuild really asksThe reading of every sector of every remaining drive, in an array of four drives of 16TB each, means about 48TB of continuous reads from drives the same age as the one that failed. This is the plain risk.
The URE number, honestlyA consumer hard drive is rated to have one unrecoverable read error (URE) every 1014 bits (which equates to about one bad sector in every 12.5TB read); an enterprise-class hard drive is rated at 1015, or ten times better than consumer. That rating is a warranty floor, not a schedule, and most drives do continue to read cleanly beyond their ratings. The rating is based on fact; the 'doom' graphs are marketing tools.
What controllers do when it happensBehaviour varies: older controller systems terminate the rebuild when they encounter a single unrecoverable read error. Modern PERC and MegaRAID controllers puncture the affected stripe(s), allowing them to continue rebuilding. Linux mdadm will log those errors into its bad-block file. One unreadable sector should cost one stripe, not the array.
Why the second failure is usually mechanicalDrives from the same production batch, with the same hours of operation and the same heat, then a rebuild's marathon read. The survivor that was quietly marginal will likely break down during this marathon process. Gentle imaging, weakest regions last, is how we run that marathon instead.

How we recover it, stage by stage.

01

Booked in, diagnosed free Free

Your device is logged under its own case reference as soon as it arrives. An engineer assesses the fault and confirms what is actually recoverable. And you receive a fixed price in writing: no diagnosis fee. No obligation. And no paid work until you say go.

Free diagnosisFixed written quoteNothing to sign
02

Image every member first

Every drive (including both 'failed' ones) is individually imaged, with all bad sectors mapped as well as all weak zones deferred. From here, nothing that follows can make the situation worse than it already is.

All members imagedFailed drives included
03

Derive the geometry

We establish the order of drives, the striping parameters and the parity rotation directly from the data provided by the original source along with any additional metadata that has been written to disk by the controller. No working controller is required and there is absolutely no guesswork involved.

Order & parity derivedVerified before rebuild
04

Rebuild virtually, choose per block

Software is used to assemble the array across the images. Each block is taken from whatever member carries it best (including areas only 'failed' members have). Afterwards, the file system on top is repaired and verified.

Best source per blockVolume verified mounting
05

Verified, returned, signed off

You approve a full listing of everything that came back before you pay the recovery fee. Your data returns on new media with free return postage. And the case only closes once you have confirmed all items open on your side.

File listing approvalNew media includedFree return postage

What the lab checks first

  • Degraded means naked: a degraded RAID 5 has used up its entire failure allowance; it is just one drive failure dressed up as a complete array.
  • Urgency is this fault's marketing problem: RAID 5 emergency situations are among the most profitable cases in the industry, which is why there is a lot of drama over them online. That is why we offer the plain truth and an image-based approach.
  • Punctured stripes are honest wounds: a contemporary controller that creates such a wound simply reports that it has lost one full stripe worth of data and clearly logs this event. This is much preferable to the behaviour of older controllers which would simply abort the entire operation. Furthermore, since it is fully visible during reassembly, it allows us to see exactly where and why it occurred.
  • mdadm keeps receipts: mdadm uses a Linux software RAID bad-block log as well as superblocks to show the system exactly what it is inheriting when re-assembling the array. In many cases software arrays will be the most transparent example of this.

The number worth actually knowing: consumer drives are specified at one unrecoverable read error per 1014 bits (approximately 12.5TB) and enterprise drives at one per 1015. A four-drive 16TB RAID 5 rebuild will require reading approximately 48TB of data from the remaining surviving disks, so the spec tells us this is indeed a risk; field data informs us most drives read well beyond their floor cleanly. Both are true, which is why the professional answer is not 'never rebuild' but rather 'never rebuild before imaging'.

From the casebook.

EX · BDR-2026-0822CHECKED ✓

An accountancy firm's RAID 5, one week before year-end

Drive two died in June. Nobody noticed until drive four followed with a failure in August, mid-rebuild. Imaging of the disks told the truth: drive four had nineteen bad sectors and was not faulty. The stripe rebuilt from three-and-a-nearly-whole members, and the practice filed on time with everything.

19 bad sectors, not 2 dead drives6 days in lab

Before it reaches us.

Do

  • Shut off power immediately if you notice your array has degraded
  • Be sure to label each drive with its bay position before you move any drives
  • Always get a quote before sending all of your drives, including the bad ones
  • Record the make/model number of the controller(s) and note anything you have attempted so far

Don't

  • Rebuild or restart a rebuild on an array that has been degraded
  • Attempt to bring the 'dead' drives back to life to test them
  • Run recovery tools across your active drives
  • Replace the defective drive and hope

Asked on this bench, answered honestly.

Can RAID 5 be recovered after two drives fail?

Very often, yes. A 'failed' drive according to a controller's definition frequently equates to just a couple of unreadable sectors, not a completely non-functional drive, and reconstructing from images will allow each data block to come from whatever drive can read it best. Two absolutely destroyed drives is rare; most times there are two dropped drives.

Should I just rebuild my degraded RAID 5?

No. Image the drives before attempting to rebuild. A rebuild reads every sector of every surviving drive (which puts those drives under tremendous stress) and writes parity as it reads, thus wiping out what reconstruction from images could later utilise. If you image first, you turn a rebuild into a risk-free process.

What is a URE and should I be scared of it?

A drive will report an unrecoverable read error when its own error correction cannot fix a problem reading data from a particular sector. It is specified at approximately once for each 12.5TB of data read from consumer-grade drives and once for each 125TB of data read from enterprise-grade drives. Respect this event as a terminal condition for the affected sector(s); do not be fearful of the event. The specification is a worst-case floor, and modern controllers lose a stripe to a URE, not the entire RAID.

Can you rebuild the array without our RAID controller?

Yes. The geometry of the drives is stored in the controller's metadata, which exists on the drives themselves; thus if the geometry is corrupted we can derive the geometry from data patterns. We have successfully rebuilt arrays from images of drives alone.

Whatever's failed, don't power it on again.

Each time a damaged device starts up again, data is lost. Open a case first; the diagnosis is free either way.

01273 964902