Lab accepting new cases ·  Mon–Fri, 9am–5:30pm Urgent? Call 01273 964902
BDR Brighton Data Recovery 01273 964902 Start a case
BDR / What we recover / Servers and disk arrays

Devices · RAID arrays & servers

RAID and server recovery, Brighton. Redundancy buys time. It doesn’t buy immortality.

Most RAID failures are due to what happens after a drive fails: the rebuild stress that kills a second marginal drive, the forced-online gamble, or someone pulling out the wrong disk. As we deal exclusively with images, your array can't get worse while in our possession. For Brighton servers and RAID sets, please get a quote first, via phone or through our quote form. Then send us only the bare disks, clearly labelled as to which bay each drive came from, never a fully populated chassis, posted tracked and insured, or dropped 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

If you're seeing this, you're in the right place.

Not listed? Run the triage →
Getting it to us from Brighton: after getting a quote first, by phone or using our quote form, post your device to our intake laboratory at Guildford using a tracked method with full insurance cover (we provide free return postage), or drop it off there directly, Monday to Friday, 9am to 5:30pm (no appointment needed). If you begin over the phone, we will guide you through how to properly pack your item. More information about sending it can be found on our contact page.

The makes and models on this bench.

Dell PERCRebadged PowerEdge RAID controllers (Broadcom/LSI) store geometry as part of the DDF metadata on each drive.
HPE Smart ArrayHP ProLiant P-series RAID arrays use proprietary RIS metadata and delayed parity, therefore they will only be imported onto an HP controller.
Broadcom / LSI & AdaptecMegaRAID and Microchip cards used in various combinations on Supermicro and white-box servers.
Software RAIDWindows Storage Spaces, mdadm: no RAID card, same maths for failures.

The exact message on your screen.

Seeing something else? →
The messageWhat it meansFirst thing we do
Foreign Configuration Found (Dell PERC)The controller has access to array metadata which does not match the configuration in its memoryNeither Import nor Clear: take an image
1786 — Drive Array Recovery Needed (HP)A rebuild will be necessary or was disrupted; redundancy is lostStop-and-image event
1784 — Drive Array Drive Failure (HP)A physical drive in the array has failedDon't hot-swap and pray
1788 — Slot X Drive Array Reports Incorrect Drive Replacement (HP)The new disk is installed in the wrong bay, or the incorrect disk was removedOrder matters — stop
Virtual Drive is Degraded / OfflineRunning without redundancy or not running at allPower down the array
1720 — SMART drive detects imminent failure (HP)A member of the array is about to fail within a currently active arrayPlan the imaging now

How we recover a RAID or server, stage by stage.

See recent recoveries →
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

Individual images of each drive (including the 'failed' ones) are created via hardware-based imaging tools. No writing occurs to your original disks. All processing occurs on copied disks.

Every member imagedFailed drives included
03

Reconstruct virtually

From the copies of the data (with drive order, block size and parity rotation identified), the original array is re-assembled using software. The controller is not used during this process, and therefore no rebuild occurs.

Order and parity derivedNo controller required
04

Recover the volume on top

All file system repairs, VM restores and database recoveries are performed on the re-assembly and then verified against an inventory list prior to sign-off.

VMs and databases mountedChecked before sign-off
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

  • The Import / Clear prompt is a trap: importing a stale drive places old metadata onto live stripes; clearing removes the entire map. Both options require only one keystroke to execute and neither option is reversible. Neither option should be executed until each member has been imaged.
  • HP does it differently on purpose: Reserved Information Sectors on each drive and parity offset by one stripe (delayed parity); therefore when an HP array is placed into recovery software that is configured to recover 'standard RAID 5', it appears as though the array is full of garbage.
  • The array's geometry lives on the drives, not the card, so you will rarely lose data when a controller fails. The drive order, the size of blocks and parity rotation can all be obtained from the disks themselves.
  • The second failure is the story, because all sectors of each surviving disk are scanned during a rebuild; this is exactly how marginal disk drives die while being rebuilt.

The real number behind the RAID 5 warnings: the data sheet specifications for consumer SATA drives indicate there is approximately one unrecoverable read error every 1014 bits, or approximately every 12.5TB of data read. Since a large RAID 5 rebuild reads much more than this from its surviving members, single-parity arrays fail their own rebuilds. This is a figure quoted in the datasheets, not folklore, although how doomed this makes RAID 5 is still being debated.

From the casebook.

EX · BDR-2026-0748CHECKED ✓

A factory's RAID 5 with two dead members, recovered over a weekend

Production data was held on a server where the second disk died while rebuilding, on a Friday. All four disks were imaged, the stripe was reconstructed from three-and-a-bit good images, and by Monday morning the factory was up and running again.

100% critical data1 weekend

Before your RAID set or server reaches us.

Do

  • Shut down the array and keep it shut down
  • Label each disk with its bay location before removing it
  • Get a price quote before sending all the disks; include those marked as 'failed'
  • If you know, tell us what RAID level you're using and what kind of controller you have

Don't

  • Rebuild or restart a rebuild on an array that has been degraded
  • Force failed disks back into service
  • Reinitialise or 'Repair' the RAID in the controller BIOS
  • Let anyone run recovery programs on your live array

Asked on this bench, answered honestly.

The controller marked a drive failed — do you still need it?

Yes: get a quote first (by phone or with the form), then send all members. 'Failed' drives typically hold the newest copy of some regions, and reassembly will choose the healthiest source for each block across all drives.

We don't know the original drive order any more. Fatal?

No: all information required to recreate the correct drive order and to establish the correct block size and parity rotation is embedded in the pattern of data stored on each individual disk. This is standard analytical work, based on evidence, not guesswork.

Can you recover the virtual machines, not just files?

Yes. After we have rebuilt the array, we can use VMDK, VHDX and database stores as primary targets for recovery and verify they mount (not just that they exist).

How fast can a business-down array be turned around?

Jobs involving more than one drive generally take four to seven working days. If this is an emergency business-down situation, we can work continuously. Tell us when you call and we'll schedule intake around your needs.

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