Taking work now — the first look is freeServer and RAID drives posted in from anywhere in the UK, or handed in at ten drop-off pointsQuicker still, give us a ring:0800 6890668
RDDRAID Drive Data Recovery 0800 6890668 Price my job

RAID drive data recovery · UK-wide, by post · SAS, SATA, SCSI, SSD and NVMe

The drives inside servers and RAID sets. One at a time, or all together.

When one drive in a server or a RAID set fails, the rest of the set is only as safe as your next decision. A rebuild reads every sector of every survivor, on drives bought the same day as the one that died; a cleared foreign configuration deletes the set's description; an initialised drive loses its start; a PSID revert loses everything. Power down, label the slots, and post the drive. We image it on the SAS, SATA, SCSI, Fibre Channel or NVMe imager its interface needs, at its native sector size, with heads swapped in clean air where they must be, and hand the image back on fresh media so the set can be rebuilt from a drive that answers every read; or we image every member and rebuild the set from the images. One failed member drive is £300 + VAT. A set of two to four is £500 + VAT upwards, and larger sets, 15K SAS sets and storage shelves start at £1,250 + VAT. The first look is free, the figure is given in writing, and on most jobs no data means no bill.

Put it to an engineer and hear what it would take
0800 6890668

The look is free · a reference for this checkCHECK-····

What kind of drive is it?

Choose the closest match. You get a likely cause, the band it falls in, and the one thing not to do tonight.

Free, and nothing to payAnswered inside a working day
£300 + VATOne failed member drive
FreeThe first look
3–4 daysAt the bench, for one drive
UK-wideBy tracked post
Imaged at native interface and sector sizeOne fixed figure in writingMost jobs: no data, no billImage back on fresh mediaReturn postage paidICO-registered · ZC173784

Four drive jobs closed, and what went home.

Jobs already closed →
UK · RDD-2026-0551JOB LOGGED ✓

An ST1200MM0088 out of a PowerEdge R730, slot 3, clicking, with a RAID 5 set of six that could not rebuild without it and a second drive predictive

Two heads had failed and the controller had marked the drive failed; the owner powered down instead of rebuilding. The clicking drive had a matched head stack fitted on the clean bench and was imaged on the SAS imager head by head; the predictive-failure drive was imaged too, with its weak areas last. Both images went back on fresh drives and the set rebuilt cleanly.

100% of the member recovered4 days here, and back by post
Illustrative example — replace with a genuine case
UK · RDD-2026-0558JOB LOGGED ✓

Six MO1600JVYPR SSDs in a DL380 Gen9 RAID 5, four failed within an hour at 40,000 hours, the other two updated and re-added by an engineer the same afternoon

The free look found two of the four failed drives answering at controller level and two not. Two members of six was not enough to rebuild a RAID 5, and the survivors had been updated and re-added, which had already rewritten what a rebuild could have used. We said so, sent everything back, and did not charge.

0% recovered, and no bill3 days here, and back by post
Illustrative example — replace with a genuine case
UK · RDD-2026-0559JOB LOGGED ✓

Fourteen 520-byte SAS drives from a decommissioned NetApp DS4246, kept in a cupboard for two years, with one aggregate's files needed for an audit

There was no filer left to put them in and every host that saw them offered to initialise them. All fourteen were imaged at 520 bytes on the SAS imager, the images translated to 512-byte sectors, and the RAID-DP aggregate reassembled in software from the translated images. The WAFL volume inside was opened and the audit's files copied out.

100% of the volume recovered10 days here, and back by post
Illustrative example — replace with a genuine case
UK · RDD-2026-0557JOB LOGGED ✓

Four SEDs from an R740 whose PERC H740P had been replaced, leaving the set locked, with the passphrase in a password vault nobody had looked in

The passphrase decided the job. The four drives were unlocked on the SAS imager with it and imaged, one after a head swap on the clean bench, and the images went back on fresh drives with the set reassembled from them. The same job without the passphrase would have ended at the free look, unbilled.

100% of the set recovered6 days here, and back by post
Illustrative example — replace with a genuine case

Begin with the kind of drive,
or with what the controller is saying.

Or begin with the family or the server →

Every kind of member drive

SAS 2.5-inch 10K and 15KST…MM, HUC, AL14: the fast drives in 1U and 2U servers. Heads first→NL-SAS 3.5-inchExos and Ultrastar on a SAS board, in MD1400, D2600 and DS4246 shelves→Enterprise SATA 3.5-inchExos, Ultrastar, MG, Gold: dropped by the controller, readable on a bench that waits→SCSI and Fibre ChannelCheetah, Atlas, Fujitsu MAW: terminated, imaged, donors sought→SAS and SATA SSD membersHPE, Dell, Micron, Samsung: controllers, and clocks in the firmware→520-byte and T10 PI drivesNetApp, EMC, Sun: imaged at native size, never reformatted→Self-encrypting drivesUnlocked with your key; never a PSID revert→

The two jobs that ask more of you

Locked and odd-format drives, and whole sets.

Most member-drive work ends the same way: the drive imaged on the imager its interface needs, the image back on fresh media, the set rebuilt from a drive that answers every read. Two kinds of job add a step. A self-encrypting drive separated from its controller, or a drive from a NetApp or EMC array with 520 bytes in every sector, needs the right key or the right translation before a byte of it makes sense. And a set that has failed as a set needs every member imaged and the array put back together from the images, which is the work our RAID array site describes and the same bench does.

TCG · Opal · FIPS · 520 · 528 · T10 PI

Locked and odd-format drives

A SED that reads as noise after a controller swap is waiting for the passphrase, the exported key or the key manager it was locked with; we unlock it on the imager with what you supply, and without it nobody recovers anything, which is said at the free look. A drive a server reports as 0 GB or incompatible is usually a 520-byte drive from a storage array, and the one command that makes it readable on a PC erases it; we image it at its native size and translate the image.

  • Find the key before you post
  • Never PSID revert, never sg_format
  • Imaged at native sector size; translated on the image
  • One drive £300 + VAT; a shelf from £1,250 + VAT
Through to self-encrypting drives →
RAID 5 · 6 · 10 · 50 · 60 · PERC · Smart Array · MegaRAID · mdadm

Whole sets, and the array site

When the set itself has failed, every member is imaged on this bench, with the weak ones head by head and the failed ones after their head swaps, and the array is reassembled in software from the images: order, stripe size and parity rotation from the controller's metadata on the drives, or from the parity arithmetic where the metadata was cleared. The file system is repaired on the virtual volume and the files copied out. That work is written up in full on our RAID array site.

  • Every member imaged, including the first to drop
  • Reassembled in software; never rebuilt on the originals
  • A set of two to four from £500 + VAT; larger sets from £1,250 + VAT
  • Same bench, same figure in writing
Through to the RAID array site →

What happens after it arrives.

All seven stages in order →

  1. Send the form

    Tell us the server, the controller, the model strings and what the controller says. Back by email come the posting address, the nearest drop-off point, packing notes and a booking sheet to print. The address is not published; it comes by email in reply to the form, and the booking sheet inside the parcel is what matches it to your enquiry when it is opened.

  2. Post it, or hand it in

    The failed drive in its carrier with the slot written on it, or every member where the set is the job, each in an anti-static bag in its own padding. Tracked post from anywhere in the UK, or handed in at the nearest of ten drop-off points; say where you are on the form and it comes by email with the posting details. Nobody collects, and we pay the postage home whichever way the job turns out.

  3. The free look

    The drive is read on the imager its interface needs, never in a server: the firmware, the format, the security state and the defect lists before a sector is. An engineer settles what has failed and how much can honestly be read back. That stage carries no charge, and you may stop at it owing nothing.

  4. One price, written down

    Findings and price arrive together, and nothing chargeable begins until you have agreed to the figure.

  5. You get the drive back, and the files

    The image on fresh media, sector-identical, for the rebuild; or the set reassembled from the images and the files copied out. 3–4 days at the bench for one drive, 5–10 days at the bench for a set. Your case stays open until you have opened the files yourself.

It has failed, and the rebuild button is not the answer tonight.

A rebuild reads every sector of every survivor on a set whose drives were bought together, and a cleared configuration deletes the set's description from drives that were fine. Power down, label the slots, send the form, and back comes an honest account of how much still reads, with the price of getting it home. That account is free, and so is the parcel returning.

0800 6890668

Price my jobPacking and posting