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 / Media and devices we handle / Arrays and servers

Devices · Servers & RAID sets

RAID data recovery, Southampton. Redundancy delays the crisis. It never cancels it.

The first death in an array seldom kills the entire set. It is the next event which usually leads to disaster: a rebuild that fails another tired disk, an administrator's gamble on forcing the set back online, or a healthy disk pulled from the wrong bay. Everything we do runs on images, so nothing gets worse once it reaches our bench.

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

RAID faults, and which ones still end well.

Can't see yours? Try the fault finder →
Posting it: first get a quote, by phone or with the form (we'll walk you through packaging), then send your device by tracked and fully insured post to our secure intake lab (return postage is free), or drop it off at the Guildford intake lab, Monday to Friday, 9am to 5:30pm, no appointment needed. Postage details are on the posting details page.

RAID controllers and server makes we handle.

Dell PERCPowerEdge cards: Broadcom/LSI in Dell badging, with the layout held on the members as DDF metadata.
HPE Smart ArrayProLiant P-series: HP's own RIS metadata and delayed parity; only HP cards will import these.
Broadcom / LSI & AdaptecMegaRAID and Microchip controllers, commonly used within Supermicro and self-assembled servers.
Arrays done in softwaremdadm and Windows Storage Spaces, which have no card involved but use the same maths for failures.

The precise wording your screen shows.

A different symptom? →
The exact wordsWhat that tells youFirst step
Foreign Configuration Found (Dell PERC)The metadata on your drives does not agree with what the card has recorded.Not Import, not Clear — image
1786 — Drive Array Recovery Needed (HP)Redundancy is lost; a rebuild is pending or was interrupted somewhere along the way.Power off, then image
1784 — Drive Array Drive Failure (HP)One of the disks has diedNo hopeful hot-swapping
1788: Slot X Drive Array Reports Incorrect Drive Replacement (HP)Disk replaced in wrong baySequence counts — halt
Virtual Drive is Degraded / OfflineThe volume has either no parity protection left, or it has been taken offlineShut the array off
1720: SMART drive detects imminent failure (HP)A live disk is warning it will fail soonArrange imaging now

How the recovery runs, step by step.

Browse recent cases →
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

Every member copied

Each of your disks, including any the controller threw out, will be put on a dedicated piece of hardware for imaging. From then on we touch only copies; your originals are never written to.

All members imagedFaulty drives covered
03

Rebuilt in software

Member sequence, stripe size and the direction parity rotates all come from the data on the disks. The set is then assembled across our images on our own machines (no card involved, and no rebuild ever started).

Sequence and parity readNo card needed at all
04

Repair the volume above it

File system, virtual machine containers and database stores are repaired on that reconstruction and then checked against a listing before release.

Databases and VMs openedVerified before release
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

  • The Import / Clear prompt is a fork with two bad prongs: Import will push an outdated member's metadata onto live stripes, while Clear will delete the layout altogether. Both are a single keystroke, neither can be reversed, and both must wait until every disk has been imaged.
  • HP's layout is deliberately its own: each member holds Reserved Information Sectors, and parity resides one stripe later than you would expect (delayed parity). Set your favourite utility to plain RAID 5 against those disks and it will yield nothing but garbage.
  • Layout is put onto the members rather than onto the card, so a burnt-out controller is rarely the end of anything. The sequence, stripe size and parity rotation can all be read back from the disks.
  • It's your second failure which matters: the rebuild will pull every sector from each of the survivors, and it is this full-surface read that finishes off an already-marginal disk.

The origin of RAID 5 warning messages: a consumer SATA drive is specified at approximately one unreadable sector for each 1014 bits read off it, roughly one for every 12.5 terabytes. When restoring a large single-parity array, the remaining drives are asked to deliver more than that in one pass, which is how a rebuild can kill itself. The figure is published, not folklore, but what it really means for RAID 5 systems is still widely debated.

Out of the casebook.

EX · SDR-2026-0748SIGNED OFF ✓

Two dead disks in a factory RAID 5, back inside a weekend

A Friday rebuild swallowed a second drive and left the production data on the server unreachable. We imaged all four disks, rebuilt the RAID 5 stripe using three images and a portion of another, and the factory was running again by Monday.

100% essential data1 weekend

While it's still with you.

Do

  • Shut down your server and do not restart
  • Write down each disk's bay number prior to removal
  • Include all members, even the dead ones
  • Tell us what RAID level it is and what card you are using, if you know.

Avoid

  • Start or resume a rebuild on a degraded array
  • Force a rejected member online
  • Reinitialise or "repair" anything in the card's setup options
  • Point scanning tools at your array while it is still assembled.

Bench questions, straight answers.

One drive was failed by the controller — should I still send it?

Yes: get a quote first, by phone or with the form on this site. Then send all the disks, each one labelled by its bay. Even though a drive may be listed as "failed", it could contain the latest copy of some areas, and the rebuild takes the best source for each block from anywhere within the group.

Nobody remembers which order the disks were in. Is that fatal?

No: all of these (disk order, block size, parity rotation) can be deduced from the patterns in the data residing on those disks. This is standard analysis, not an educated guess.

Can whole virtual machines come back, not only files?

Yes. Once the array is reassembled, VMDK, VHDX and database stores are treated as primary targets, and each one is checked for whether it will successfully mount rather than whether it simply exists.

What's the turnaround on an array with the business down?

You should expect four to seven working days when multiple drives are involved; however, if your business is genuinely down, work can run continuously. Let us know by phone and we will build the intake around what you need.

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