Skip to main content

SAS drives • servers • arrays

Data recovery from SAS drives and server media

SAS drives most often work in servers, arrays, and corporate environments. If the array reports degraded/offline, the volume has disappeared or several disks have read errors, do not initialize the configuration and do not run rebuild without analysis.

SAS 10K/15K RAID / NAS / DAS B2B and NDA

HomeServices › Data recovery from SAS drives and server media

Server media

Who is this path for

This page applies to SAS drives as server media: single drives, array kits, file servers, and corporate environments. It does not replace the general RAID page, but clarifies the cases in which the disk type itself and the working environment matter.

If the failure affects the entire NAS or RAID level, also check the data recovery from RAID and Synology/QNAP.

SAS RAID server array degraded offline

Symptoms

Typical situations with SAS drives

RAID degraded or offline The matrix reports a failure, the volume is missing or the controller sees part of the disks as foreign/failed.
Nieudany rebuild The reconstruction stopped, lasted too long or after the restart the volume was no longer available.
Multiple disk read errors Several media have unstable readings and the system is still trying to work on the matrix.
Company environment The data relates to shares, databases, VMs, accounting, documents or the production file system.

What not to do

What not to do with SAS/RAID

Do not initialize matrix Initialization can overwrite the metadata needed to reconstruct the layout.
Don't accidentally rebuild Restoring without knowing which disk is the source of the problem can aggravate the case.
Do not shuffle the order of the discs Record the order of the bays, ports and controller messages before disassembly.
Do not run write tests Saved service tests are risky when the goal is to recover data.

Diagnosis

How we diagnose SAS drives and arrays

First, we document the configuration and status of the disks, and the reconstruction is carried out on images/copies, not by repairing the production volume live.

1

Symptom Description

We start with a short assessment: media model, symptoms, recent activities and the importance of data.

2

Safe diagnostics

We check the condition of the media without write actions and without system repairs running on the original.

3

Stable reading

If the case so requires, we prepare an image or a working copy and only analyze the data structure from it.

4

File verification

After the analysis, we provide real information about the scope of recovery, risk, time and cost.

Related services

FAQ — SAS drives and server media

Do I need to provide the entire server?

Not always. Often, disks in the correct order and configuration information will suffice, but with an unusual controller, it is worth consulting the scope before disassembling.

Run rebuild if RAID reports degraded?

If the data is valid, do not run rebuild without analysis. Reconstruction can overwrite data or perpetuate an erroneous matrix layout.

What other information do we need?

They help: server or array model, number of drives, RAID level, order of bays, controller messages and history of recent activities.

Do you handle corporate and NDA matters?

Yes. We work with corporate media, databases, shares and environments requiring confidentiality or NDA.

Are you recovering data from a single SAS drive?

Yes, if the problem is with a single SAS media, we diagnose it like other server drives, with an emphasis on stable reading and copying.

Next safe step

SAS disk or array failure?

Stop the destructive operations, note the messages and the order of the disks, and then describe the case in the report.