Home / Devices / RAID Array

RAID Data Recovery Swindon

Degraded for months, then the second disk quit twenty minutes into the rebuild — or the controller failed and its configuration vanished with it. RAID array recovery is a fixture of this bench: sets at RAID 0, 1, 5, 6 and 10 out of servers, workstations and NAS units across Swindon and the M4 corridor, imaged first and reconstructed virtually, with business-down cases moved to the head of the queue — including urgent RAID server data recovery for Wiltshire businesses.

Free diagnostic on every raid array job. One fixed quote in writing before any work begins.

No fix, no fee all jobs except electronic and mechanical failures, chip level work, DVR and Forensic jobs. Full pricing is on the data recovery cost page.

// top 20 faults we recover from

The twenty ways they fail

Every raid array job starts by matching the symptoms to the fault — these twenty cover almost everything that reaches the bench.

Second RAID 5 casualty

One loss is designed for; the rebuild then kills the weakest survivor — the defining disaster of RAID array recovery.

Rebuild died partway

A half-run rebuild poisons the parity it relied on; the reach of the damage is mapped from the images.

Controller amnesia

A dead card takes the configuration to the grave — geometry is re-derived from the members with no card required.

Stale member forced online

A member carrying months-old data gets forced back in, and the file system tears itself apart on the mismatch.

Overwritten configuration

Someone built a fresh array on top of the old — halt it before initialisation runs its course and plenty survives.

Multi-drive power event

One surge fells several members at once; every drive gets its own repair and its own capture before the arithmetic starts.

Backplane ghost failures

Whole banks of drives 'fail' together when the chassis wiring is the true casualty — so diagnosis comes before alarm.

Broken file system, healthy RAID

The stripe maths is perfect; the NTFS, ext4 or VMFS on top isn't — parser-level rebuild wins it.

Deleted volume / LUN

Definitions removed in error come back while the blocks they described stay intact.

Write-hole corruption

Flat cache batteries plus a power cut desynchronise parity from data — reconciled at image level.

PERC / Smart Array config loss

An H710 or P420 dies with the definition aboard — the layout is recovered from the members, no replacement card needed.

Clicking member drive

A member with dead heads visits the clean bench first, then joins the imaging queue with the others.

IronWolf sets wearing in step

Same-batch ST8000VN004s in small-business arrays age together — parallel imaging beats the second failure to the punch.

mdadm / Storage Spaces tangles

Software arrays shed superblocks and pool metadata — rebuilt from the raw members, structure by structure.

Grown-defect avalanche

A member remapping sectors daily is failing in slow motion; catching it at imaging time rescues the whole set.

RAID 10 mirror pair loss

Losing both halves of one mirror beats the redundancy — yet lab imaging often revives one half enough to close the stripe.

Hot spare that was already failing

The automatic rebuild lands on a spare that's been spinning idle for years — and dying quietly the whole time.

Foreign-config import gone wrong

An 'import foreign configuration' click against the wrong metadata scrambles the set — the true layout is recovered from the drives.

Desktop drives in a server array

Blues and Barracudas without error-recovery limits drop from arrays under load — imaged patiently, then the set rebuilt.

ZFS / Proxmox pool damage

Power loss corrupts pool metadata on hypervisor builds — walked back through transaction history from full member images.

Image first — the rule with no exceptions

Before anyone theorises, each member drive is captured in its entirety, and the originals never spin inside an array again. The geometry — member order, stripe size, rotation, parity offset — is deduced from those captures, the volume is stood up virtually on top, and the file system is walked from that assembly. Stale members inside a RAID 5, RAID 6 double losses, nested 10s and controllers that forgot everything: that's an ordinary week of RAID array recovery here.

Three clicks that finish off arrays

Forcing an offline member back into the set, rebuilding onto a disk that's already dying, and letting someone try one final experiment — those three turn salvageable arrays into scrap far more often than the original fault does. If your array is down: power off, mark every drive with its bay, and pick up the phone. Tell us the business is stopped and the assessment jumps the queue the day the drives arrive.

// the equipment we use

A professional lab, not software guesswork

RAID array recovery runs on one non-negotiable rule — image everything first — and this bench enforces it:

Parallel imaging bays

Every member drive is captured simultaneously on dedicated hardware before analysis — originals never rejoin any rebuild.

PC-3000 RAID / Data Extractor

Works on the images to solve member order, stripe size, rotation and offsets, then mounts the assembled array virtually.

PC-3000 UDMA + clean bench

A failed member gets full hard-drive treatment — heads, firmware, electronics — so it can be imaged alongside the healthy ones.

Virtual RAID reconstruction software

Entropy and parity checks prove the solved geometry before a single file is lifted from the assembled volume.

File-system parsers

NTFS, ReFS, ext4, XFS, BTRFS and VMFS opened natively — virtual machine disks stored on top included.

Hardware write-blockers

Member imaging is read-only by physical enforcement; the drives return to you untouched.

// manufacturers & models

Server & controller brands we recover

HP ProLiant (Smart Array)Dell PowerEdge (PERC)SupermicroIBM / LenovoAdaptecLSI / BroadcomIntel RAIDArecaPromise3ware (legacy)

Arrays and controllers seen most

Hardware card, software layer or chipset RAID — the geometry lives on the member drives, and the members are the source it gets read from. PERC and Smart Array cards have a habit of dying with the definition still aboard, matched-batch NAS drives like the ST8000VN004 have a habit of failing in formation, and desktop-grade members drop out of sets under load — three different roads to the same bench, all ending in parallel imaging on arrival day.

// before you post it

Sending it in — remove the drive if you can

Power the server or shelf down before touching anything, then mark each member with its slot while it comes out — reconstruction leans on the original order being known. Only labelled drives travel; the controller and chassis remain at yours, and a phone snap of the bays as they stood is worth taking.

// getting your device to us

Post or courier your device — it's simple

Most customers post or courier their media to us.

Sending a drive from a computer, laptop, MacBook, iMac, CCTV / DVR or server? Please remove the internal hard drive or SSD and send us just the drive — we don't provide an internal drive-removal service. We don't recover storage soldered to a motherboard (e.g. Apple Silicon Macs and some thin laptops) — only drives that can be removed and sent to us.

  • Wrap the device in bubble wrap or a padded envelope — no need to include cables or power supplies.
  • Print and enclose the booking-in & shipping form (PDF) with your name, phone number and a brief description of what happened.
  • Send by Royal Mail Special Delivery or any tracked courier for full insurance in transit.
  • Prefer to hand it over in person? You can drop it in at reception at the address shown, Mon–Fri 9:00am–5:30pm.
// send your device to your nearest location

Oxford Data Recovery

John Eccles House, Oxford Science Park
Robert Robinson Avenue, Littlemore
Oxford, OX4 4GP

↓ Print the booking-in & shipping form (PDF)

Mark the package for the attention of Oxford Data Recovery and we'll call you as soon as we diagnose your media.

Not sure what to send? Call 0800 689 0668 first or use the free online diagnostic.

// raid array recovery questions

Common questions

Good, more often than not. The first 'failure' is typically a stale drop-out from months ago, and the recent casualty can usually still be imaged here, on hardware built to wait for it. That image plus the survivors lets the parity maths complete and the volume stand up virtually.
Save your money — no. The layout sits implicit in the member drives themselves, and order, stripe, rotation and offset are derived from the data alone. Labelled drives are the only things that need to travel.
Usually plenty. A partial rebuild overwrites some stripe regions and never reaches the rest; we map that boundary from the images and extract accordingly, your priority folders first.
Constantly — ProLiant, PowerEdge, Supermicro, custom builds, plus the small-office NAS arrays. Urgent cases get assessed first: say 'business-critical' on 0800 689 0668 and the fastest safe route in gets arranged on that call.
// related services

Also recovered here

// specialist pages

Go deeper

Ready when you are.

Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.