Skip to content
AS

RAID Recovery

A failed array is rarely a single-disk problem. AS images every member disk, reconstructs the array virtually, and recovers from the reconstruction so the originals are never rebuilt or written to.

When you need this

  • Multiple disks failed and the array is offline
  • Rebuild started or completed onto the wrong disk
  • Controller failed or configuration was lost
  • Array reports healthy but volumes are unreadable
  • Accidental re-initialisation or reconfiguration
  • Ransomware on a RAID-backed server

What we do

Member disk imaging

Each disk is imaged independently, including failing members, so recovery works from copies.

Virtual reconstruction

Stripe size, disk order, parity rotation and offsets are determined and the array is assembled virtually — including custom and vendor-specific layouts.

Volume and file system recovery

Volumes, LVM/Storage Spaces layers and file systems are recovered from the reconstructed array.

Stale-member analysis

Where disks dropped out at different times, we identify which members hold current data to avoid mixing old and new blocks.

How it works

  1. Step 1

    Consultation and scope

    We establish what failed, what has been tried, and which data matters most. This shapes a targeted plan rather than a generic one.

  2. Step 2

    Secure imaging and diagnosis

    Where possible the source media is imaged before any work, so the original is never altered. Diagnosis then determines the safest recovery method.

  3. Step 3

    Recovery

    Data is extracted from the image or source using methods matched to the failure — logical, structural or hardware-level as required.

  4. Step 4

    Verification

    Recovered data is checked for integrity and completeness, and a file list is shared so you can confirm what matters is there.

  5. Step 5

    Secure delivery

    Verified data is returned through an agreed secure method, with guidance on validation before it goes back into production.

What affects the outcome

Outcomes are never guaranteed. Every case is assessed on its own condition, and we tell you what is realistic before you commit.

  • Physical condition of the media and the extent of any damage
  • Whether the media has been written to, reformatted or re-initialised since the failure
  • Encryption, corruption or partial overwriting of the data
  • Availability of source data such as images, backups, logs or transaction records
  • Attempts made before assessment (rebuilds, repair tools, repeated reboots)
Related AS software

AS RAID Recovery

For arrays with healthy disks and a lost configuration, the software can reconstruct the array and recover data on your own hardware.

Frequently asked questions

Should I let the controller rebuild the array?

Not before assessment. A rebuild with a stale or failing disk can overwrite good data permanently. Power down and preserve the disks as they are.

Do you need the RAID controller?

Usually not; the array is reconstructed from the member disk images. Controller details help but are rarely required.

Can you recover a RAID 0 with one dead disk?

Only if data can be extracted from the failed disk. RAID 0 has no redundancy, so the outcome depends on that disk's condition.

Request assessmentEmergency