We are booking in new cases · Weekdays, 9am–5:30pm Urgent case? Call 0800 6890668
MHDR Maidenhead Data Recovery 0800 6890668 Send it in
MHDR / Media and kit we recover / Servers & RAID sets

Devices · array sets & servers

RAID and server recovery, Maidenhead. The rebuild does more harm than the failure.

What ends an array is almost never the first failure. It is what follows: a rebuild driving a tired survivor through one long read until it stops, an ejected member forced back into service, disks moved between bays to see what happens. A mirror offers no shelter either, since both halves have run identical hours since installation. Arrays reach us from Maidenhead by tracked post, and we work from images alone, so nothing worsens once the set arrives.

No fee unless the data comes back Diagnosis free, then a fixed quote Post it in from Windsor, Slough or anywhere else

Describe the fault to an engineer
0800 6890668

RAID faults, and what each one means.

Nothing matches? Use the triage →
If you post it in: use a tracked, insured service addressed to our secure intake lab, and the return leg is paid at our end; if you would rather check the packing first, an engineer will go through it by phone. Each step is set out on the postage page.

The RAID cards we see, and the arrays with none.

Dell PERCStandard fitment in PowerEdge servers — Broadcom and LSI silicon wearing a Dell badge, with DDF metadata on each member.
HPE Smart ArrayP-series controllers in ProLiant chassis — RIS metadata and delayed parity, a combination nothing outside HP reads.
Broadcom / LSI & AdaptecMegaRAID and Microchip cards — the usual choice in Supermicro boxes and machines built in-house.
Arrays without a cardmdadm under Linux, Storage Spaces under Windows — no card to fail, and the same arithmetic when a member does.

The words on screen, decoded.

A different fault? →
The symptomThe likely causeStart here
Foreign Configuration Found (Dell PERC)Metadata on the members contradicts the card's own copyTouch neither option; clone first
1786 — Drive Array Recovery Needed (HP)Cover is gone; a rebuild is either waiting or half finishedShut it down, then image it
1784 — Drive Array Drive Failure (HP)A member of the set has diedDo not guess at a replacement disk
1788 — Drive Array Reports Incorrect Drive Replacement (HP)Members have been returned to the wrong slotsSequence decides everything; stop
Virtual Drive is Degraded / OfflineThe volume has lost its cover, or has disappeared entirelyPower the entire set down
1720 — SMART drive detects imminent failure (HP)A working disk is telling you it has not long leftTake a copy that day

What happens between arrival and return.

The most recent cases →
01

Booked in, then assessed at no cost Free

Nothing becomes chargeable until you have said yes to it. Each item takes a case number of its own the moment it arrives, an engineer establishes what has actually failed, and you are given a candid view of which files stand a realistic chance of returning. The single quote that follows is fixed, written down, and costs nothing.

Diagnosis at no costOne fixed quote, in writingNothing signed
02

Clone the whole set first

Each member is read onto dedicated imaging hardware, including those the card had already rejected. All the work that follows happens on those copies, and nothing at any stage is written back to the disks you posted.

Every member imaged firstEven the failed members
03

Stood up again in software

Stripe width, member sequence and the way parity rotates are recovered from the structure of the data itself. The array is then stood up across the images on our own equipment. Your card plays no part in it, and at no point does a rebuild run.

Member order establishedNo original card needed
04

Mend what sits on top

With the set standing, the file system, the virtual-machine containers and the databases are repaired in turn, then verified against a complete listing before anything leaves.

Guests and databases openedChecked before it is returned
05

Opened, verified, and sent home

Nothing is billed until you have seen the recovered file list in full and told us to go ahead. What comes back arrives on new media, with the return journey at our cost, and the case stays open at this end until you have opened every file yourself.

You approve the list firstReturned on fresh mediaThe return post is ours

What tends to show up first

  • Import and Clear are both traps — the first lays a stale member's metadata across stripes that are still sound, the second throws the layout away altogether. Each is one keystroke, each is irreversible, and neither has any business on a set that has yet to be cloned.
  • HP arranged its arrays to suit itself: Reserved Information Sectors written on every member, and parity set one stripe further along than the standard description — delayed parity is the term. Aim a general-purpose RAID 5 tool at those members and the output is meaningless.
  • The geometry travels with the disks — which is why a controller failure looks far worse than it is. Member order, stripe width and the direction of parity can all be read off the members themselves.
  • It is the second loss that does the harm — a rebuild demands one continuous read of every disk still standing, which happens to be the exact task a marginal drive cannot complete.

Why single parity acquired its reputation: a consumer SATA specification permits roughly one unreadable sector for every 1014 bits read, which works out at about one in each 12.5TB. Ask a large single-parity array to rebuild and every survivor has to hand over more than that without a break, which is where rebuilds come apart. The number is the manufacturers' own rather than an engineer's invention, though how sharply it bites in practice remains a matter of argument.

From the casebook, lately.

MH · MHD-2026-6748ON RECORD ✓

Second disk gone mid-rebuild; the factory ran on Monday

Production stopped when a Friday rebuild claimed a second member and locked the live data away. Each disk was imaged separately; the stripe was reassembled from the three that read cleanly plus whatever the fourth would give up, and the line was running by Monday morning.

100% of the vital files1 weekend

Before it comes to the lab.

Do these now

  • Turn the server off and keep it off
  • Write down which bay each disk occupied
  • Post the full set, the failed members too
  • Tell us the array level and the card, if known

Things best not done

  • Start or restart a rebuild on an array already degraded
  • Push an ejected member back into the set
  • Use 'repair' or 'initialise' in the card's configuration menu
  • Run recovery software across the array while it is live

Questions we are asked about RAID recovery.

The card has marked one disk failed. Does it still need to come?

Send the complete set. A condemned member often holds the most recent copy of some stripes, and every block is drawn from whichever image returned it most cleanly.

Nobody recorded which disk sat in which bay. Is that fatal?

It is not. Stripe width, member order and parity rotation are all legible in the data's own structure — routine analysis, not trial and error.

Can entire virtual machines come back, or just files?

They can. Once the set stands, the VMDK and VHDX containers and the database stores come off first, and each is opened on the bench to prove it works rather than logged as present.

The company is at a standstill. How quickly can an array return?

Allow four to seven working days for a set of several disks. When trading has genuinely stopped the work can be run continuously; mention that when you ring, and the intake is arranged around the deadline.

Switched off, it keeps every chance it has.

Each further power-up asks more of a drive that has already begun to fail. Open the case first and let the free diagnosis tell you what is left.

0800 6890668