Skip to main contentSkip to navigation
Rossmann Repair Group logo - data recovery and MacBook repair

SAS Drive Recovery

Since 2008 | No Data, No Fee | Nationwide Mail-In | $100–$2,000

SAS (Serial Attached SCSI) drives are the backbone of enterprise servers and SAN arrays. They use a different command set, physical connector, and firmware architecture than consumer SATA drives. Our Austin lab images SAS drives through dedicated SAS host bus adapters and PC-3000 at their native 12Gbps interface speed, preserving access to non-standard sector sizes and SAS-specific diagnostic channels. No data recovered = no charge.

FREE ESTIMATEMail-In Service

No Data, No Fee

Guarantee

2.49M+

Subscribers

4.9

1,837+ Google Reviews

Since 2008

Established

Repairs on Video

Full Transparency

As Featured In

BBC
BBC News
CBC
CBC News
ABC
ABC Australia
WSJ
Wall Street Journal
BIINSIDER
Business Insider
VICE
Vice
FC
Fast Company
404
404 Media
Louis Rossmann
Written by
Louis Rossmann
Founder & Chief Technician
Updated March 2026
10 min read

What Makes SAS Different from SATA

SAS and SATA are physically and logically incompatible interfaces. A SAS drive cannot be plugged into a SATA port. Recovery labs that lack SAS interface hardware cannot image these drives at all, or must use adapter workarounds that bypass the SCSI command layer and lose access to critical diagnostic data.

SCSI vs. ATA Command Set

SAS drives respond to SCSI commands (READ(10), READ(16), MODE SENSE, LOG SENSE), while SATA drives use ATA commands (READ DMA, IDENTIFY DEVICE). Firmware recovery procedures, SMART data extraction, and defect list access all differ between the two protocols. PC-3000 includes dedicated SAS modules that speak native SCSI.

Dual-Port 12Gbps Interface

Enterprise SAS drives have two physical ports for redundant pathing in server backplanes. The 12Gbps SAS-3 interface doubles the throughput of 6Gbps SATA III. This dual-port design enables multipath I/O in production, but also means recovery hardware must support SAS signaling to establish a connection.

Non-Standard Sector Sizes

Many RAID controllers format SAS drives with 520-byte or 528-byte sectors instead of the standard 512 bytes. The extra 8 or 16 bytes per sector store controller checksums, Data Integrity Fields (DIF), or block guard tags. Imaging must capture these metadata bytes for accurate array reconstruction.

Enterprise SAS Failure Modes

SAS drives fail in ways consumer SATA drives do not. Their enterprise firmware, dual-port interface, and role inside multi-drive arrays create failure patterns that require specialized diagnosis.

  • Firmware Zone Corruption After Hot-Swap During Rebuild

    When a SAS drive is hot-swapped into an active array during a RAID rebuild, the controller writes new RAID metadata and parity data simultaneously. If power is interrupted or the backplane connection is marginal, the drive's firmware zone map can become inconsistent: the translator modules reference sectors that were partially overwritten during the rebuild. PC-3000 accesses the drive's firmware area through SAS-native vendor commands to rebuild the corrupted translator entries and restore sector addressing.

  • SAS Expander Backplane Failures

    Enterprise servers use SAS expander chips (LSI/Broadcom SAS3x36, SAS3x28) on the backplane to multiplex 24 or more drives through a single SAS HBA connection. When an expander fails or loses its routing table, the server reports all drives behind that expander as missing. The drives themselves are healthy. We remove the drives from the server chassis and connect them directly to our own SAS HBAs, bypassing the failed expander entirely. No mechanical work required; only reimaging and array reconstruction.

  • Dual-Port Negotiation Lockout

    SAS drives negotiate PHY link speed on both ports during power-on. A backplane signal integrity issue (bent pins, oxidized connectors, damaged interposer board) can cause the drive to enter a state where neither port completes negotiation. The drive appears dead to the server, but the media and electronics are intact. We clear the PHY training state by power-cycling the drive while connected to a known-good SAS HBA, allowing clean link negotiation on a single port.

  • 10K/15K RPM Head Failures

    Enterprise SAS drives spin at 10,000 or 15,000 RPM, compared to 5,400 or 7,200 RPM for consumer drives. The higher rotational speed means heads fly closer to the platter surface on a thinner air bearing. Head failures in 15K drives tend to be more catastrophic: the shorter fly height leaves less margin before a head strike. We perform head swaps on SAS drives using the same 0.02µm ULPA-filtered clean bench used for all mechanical recovery, with donor heads matched by model, firmware revision, and head map configuration.

  • SMART Threshold Exceeded / Grown Defect List Overflow

    SAS drives maintain a Grown Defect List (GDList) in SCSI format rather than the SMART attribute table used by SATA drives. When the GDList exceeds the manufacturer's threshold, the RAID controller marks the drive as predictive-fail and takes it offline. The drive often still contains readable data. We image the drive at sector level through our SAS HBA, working around bad sectors using PC-3000's adaptive read algorithms with configurable retry counts and timeout thresholds.

SAS Drive Models We Recover

We recover data from all major SAS drive families deployed in enterprise servers and storage arrays. The table below lists the models we see most frequently.

ManufacturerFamily / ModelInterfaceCommon Failure
SeagateExos 15E900 (ST600MP0136)12Gbps SAS-3, 15K RPMHead failure after thermal cycling; firmware zone corruption
SeagateExos 10E2400 (ST1200MM0129)12Gbps SAS-3, 10K RPMGrown defect list overflow; SMART threshold triggers
WD / HGSTUltrastar C15K600 (HUC156060CSS20x)12Gbps SAS-3, 15K RPMMotor bearing seizure under sustained vibration
WD / HGSTUltrastar C10K1800 (HUC101818CS420x)12Gbps SAS-3, 10K RPMPCB component failure (TVS diode, preamp IC)
ToshibaAL15SEB series (AL15SEB060N)12Gbps SAS-3, 10K RPMFirmware hang after power loss during write cache flush
SeagateExos X16 / X18 (SAS variant)12Gbps SAS-3, 7200 RPMHead degradation under continuous nearline workload

SAS drives also appear in external JBOD enclosures (Dell MD1420, HP D3700, Lenovo D2212) and storage appliances (Dell EMC Unity, NetApp FAS). Recovery procedure is the same regardless of the host chassis.

How We Recover SAS Drives

SAS recovery follows the same imaging-first discipline as every other drive type, with SAS-specific interface and firmware handling.

  1. Evaluation and interface identification.

    We confirm the drive's SAS generation (SAS-2 at 6Gbps or SAS-3 at 12Gbps), check for non-standard sector sizes, and inspect the PCB for visible damage (burned TVS diodes, cracked preamp ICs). If the drive was pulled from a RAID array, we document its position and any visible RAID controller metadata stickers.

  2. Physical repair (if needed).

    Head swaps and PCB-level component repair on SAS drives follow the same procedures used for SATA drives: work is performed on our 0.02µm ULPA-filtered clean bench. Donor heads are matched by model number, firmware revision, head count, and head map. SAS PCB repair often involves TVS diode replacement or preamp IC soldering.

  3. Sector-level imaging via SAS HBA.

    The drive is connected to our imaging workstation through a SAS HBA (not a SATA port, not an adapter). PC-3000 reads every addressable sector using SCSI READ commands with configurable retry counts and timeout values. For drives with 520-byte or 528-byte sectors, we capture the full sector including the controller metadata bytes.

  4. Firmware repair (if needed).

    SAS drive firmware uses SCSI Mode Pages and vendor-specific diagnostic pages rather than the ATA register interface used by SATA drives. PC-3000's SAS firmware modules access these vendor pages to repair corrupted translator maps, rebuild defect tables, and restore sector addressing after firmware zone corruption.

  5. Array reconstruction (for RAID members).

    If the SAS drive was part of a RAID array, we use PC-3000 RAID Edition to reconstruct the array from the member images. This includes detecting stripe size, parity rotation, member ordering, and sector size translation (converting 520-byte sectors back to 512-byte for filesystem parsing).

  6. Data extraction and verification.

    Recovered data is extracted to a target drive. File integrity is verified by opening representative files from each directory structure. For VMware environments, we deliver extracted .vmdk files that can be directly mounted. For raw filesystem recoveries, we deliver the full directory tree.

Server Platforms Using SAS Drives

SAS drives are standard in rack-mount and blade servers from every major OEM. The RAID controller and backplane vary by vendor, but the SAS drives themselves follow the same T10 SPC/SBC standards.

Dell PowerEdge

PERC H730, H740P, and H755N controllers manage SAS arrays in R640, R740, R750, and PowerEdge T-series towers. PERC controllers write proprietary DDF metadata to each member drive. We reconstruct Dell server arrays offline from imaged members without requiring the original PERC card.

HP ProLiant

Smart Array P408i-a, P816i-a, and E208i controllers manage SAS arrays in DL360, DL380, and DL580 Gen10/Gen11 servers. Smart Array metadata differs from PERC in structure but contains the same critical information: stripe size, parity rotation, and member disk order.

Lenovo ThinkSystem

ThinkSystem SR630, SR650, and ST550 servers use Broadcom MegaRAID 9350 and 9560 controllers (LSI-based). These controllers use the same metadata format as standalone LSI MegaRAID cards, which PC-3000 RAID Edition supports natively.

SAS RAID Controllers and Recovery

The RAID controller determines how data is striped, mirrored, and checksummed across SAS member drives. When the controller fails or its configuration database becomes corrupted, the data is intact on the member drives but inaccessible through normal means.

ControllerOEM UsageRecovery Approach
Dell PERC H730 / H740PPowerEdge R640, R740, R940Image members via SAS HBA, parse PERC DDF metadata, reconstruct array in PC-3000 RAID Edition
HP Smart Array P408i-aProLiant DL360, DL380 Gen10Image members via SAS HBA, parse Smart Array metadata for stripe parameters and member ordering
LSI MegaRAID 9271-8iSupermicro, custom buildsLSI DDF metadata parsed natively by PC-3000 RAID Edition; sector size translation for 520-byte formats
Broadcom MegaRAID 9460-16iLenovo ThinkSystem, Dell (OEM)Same LSI metadata lineage as 9271 series; supports SAS-3 12Gbps and mixed SAS/SATA configurations
Adaptec SmartRAID 3154-8iWorkstations, mid-range serversAdaptec metadata format differs from LSI; manual parameter detection may be needed for older firmware versions

SAS Drive Recovery Pricing

SAS drive recovery uses our standard HDD pricing tiers. The per-drive cost depends on the failure type (logical, firmware, or mechanical), not the interface. If the SAS drives are part of a RAID array, an additional $400-$800 array reconstruction fee applies.

Service TierPriceDescription
Simple CopyLow complexity$100

Your drive works, you just need the data moved off it

Functional drive; data transfer to new media

Rush available: +$100

File System RecoveryLow complexityFrom $250

Your drive isn't recognized by your computer, but it's not making unusual sounds

File system corruption. Accessible with professional recovery software but not by the OS

Starting price; final depends on complexity

Firmware RepairMedium complexity – PC-3000 required$600–$900

Your drive is completely inaccessible. It may be detected but shows the wrong size or won't respond

Firmware corruption: ROM, modules, or translator tables corrupted; requires PC-3000 terminal access

Standard drives at lower end; high-density drives at higher end

Head SwapHigh complexity – clean bench surgery50% deposit$1,200–$1,500

Your drive is clicking, beeping, or won't spin. The internal read/write heads have failed

Head stack assembly failure. Transplanting heads from a matching donor drive on a clean bench

50% deposit required. Donor parts are consumed in the repair

Surface / Platter DamageHigh complexity – clean bench surgery50% deposit$2,000

Your drive was dropped, has visible damage, or a head crash scraped the platters

Platter scoring or contamination. Requires platter cleaning and head swap

50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type.

Hardware Repair vs. Software Locks

Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.

All tiers: Free evaluation and firm quote before any paid work. No data, no fee on simple copy, file system, and firmware tiers. Head swap and surface damage require a 50% deposit because donor parts are consumed in the attempt.

Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. For ultra-high-capacity drives (20TB and above), the target drive costs approximately $400+ due to the large media required. All prices are plus applicable tax.

No Data = No Charge: If we recover nothing from your SAS drive or array, you owe $0. Free evaluation, no obligation.

Array reconstruction: $400-$800 per array, regardless of RAID level or member count. Added on top of per-drive imaging fees. Total scales with the number of drives.

Data Recovery Standards & Verification

Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.

Validated Clean Zone

Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.

Transparent History

Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.

Media Coverage

Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.

Aligned Incentives

Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.

LR

Technical Oversight

Louis Rossmann

Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.

We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.

See our clean bench validation data and particle test video

What Server and Enterprise Clients Say

4.9 across 1,837+ verified Google reviews
“Had a raid 0 array (windows storage pool) (failed 2tb Seagate, and a working 1tb wd blue) recovered last year, it was much cheaper than the $1500 to $3500 Canadian dollars i was quoted by a Canadian data recovery service. the price while expensive was a comparatively reasonable $900USD (about $1100 CAD at the time). they had very good communication with me about the status of my recovery and were extremely professional. the drive they sent back was Very well packaged. I would 100% have a drive recovered by them again if i ever needed to again.”
ChristopolisSeagate
View on Google
“HIGHLIGHT & CONCLUSION ******Overall I'm having a good experience with this store because they have great customer services, best third party replacement parts, justify price for those replacement parts, short estimate waiting time to fix the device, 1 year warranty, and good prediction of pricing and the device life conditions whether it can fix it or not.”
Yuong Huao Ng LiangiPhone
View on Google
“Didn't *fix* my issue but a great experience. Shipped a drive from an old NAS whose board had failed. Rossmann Repair wanted to go straight for data extraction (~$600-900). Did some research on my own and discovered the file table was Linux based and asked if they could take a look. They said that their decision still stands and would only go straight for data recovery.”
Mac Hancock
View on Google
“I've been following the YouTube tutorials since my family and I were in India on business. My son spilled Geteraid on my keyboard and my computer wouldn't come on after I opened it and cleaned it, laying it upside down for a week. To make the story short I took my computer to the shop while I'm in New York on business and did charged me $45.00 for a rush assessment.”
Rudy GonzalezMacBook Air
View on Google
Read all 1,837+ reviews

SAS Hard Drive Recovery: Common Questions

Can you image SAS drives directly, or do you convert them to SATA?
We image SAS drives at their native interface using SAS host bus adapters (HBAs). SAS drives use the SCSI command set, which differs from the ATA command set used by SATA drives. Converting to SATA would lose access to SAS-specific diagnostic commands and non-standard sector sizes (520 or 528 bytes per sector). Our PC-3000 connects through SAS HBAs to communicate with the drive using its native protocol.
How much does SAS hard drive data recovery cost?
SAS drive recovery follows the same pricing as our standard HDD tiers: $250 for filesystem-level recovery, $600 to $900 for firmware repair, and $1,200 to $1,500 for mechanical work like head swaps. Array reconstruction adds $400 to $800 per array. No data recovered means no charge.
Do you recover data from SAS drives with 520-byte or 528-byte sectors?
Yes. Many enterprise RAID controllers format SAS drives with non-standard sector sizes (520 or 528 bytes instead of the standard 512 bytes). The extra bytes store controller-specific metadata like checksums and block guards. We handle sector size translation during imaging and array reconstruction.
Can you recover a single failed SAS drive from a RAID array?
Yes. If one SAS drive has failed in a redundant array (RAID 5, 6, or 10), we image the failed member and return it so the array can be rebuilt. If the array itself has degraded beyond rebuild, we image all members and reconstruct the full array offline using PC-3000 RAID Edition.
What SAS drive models do you most commonly recover?
Seagate Exos (15E900, 10E2400, X16, X18), WD Ultrastar HC530 and HC560 in SAS variants, HGST Ultrastar C15K600 and C10K1800, and Toshiba AL15SEB series. These are the drives most commonly deployed in Dell PowerEdge, HP ProLiant, and Lenovo ThinkSystem servers.
My server shows a drive as 'foreign' or 'unconfigured.' Is data still recoverable?
In most cases, yes. A drive marked 'foreign' by a RAID controller still contains its data and RAID metadata. The controller is reporting that its configuration database does not match the drive's stored metadata. We image the drive through a SAS HBA (bypassing the controller entirely) and reconstruct the array from the on-disk metadata.

Related Enterprise Recovery Services

Server Data Recovery

Dell PowerEdge, HP ProLiant, IBM

RAID Data Recovery

RAID 0, 1, 5, 6, 10, 50, 60

SAN Storage Recovery

Dell EMC, NetApp, HPE arrays

VMware ESXi Recovery

VMFS datastores and vSAN

Hard Drive Data Recovery

All HDD types and brands

NAS Data Recovery

Synology, QNAP, Buffalo

Need SAS drive recovery?

Free evaluation. No data = no charge. Ship your drives from anywhere in the U.S.

Start a CaseServer Recovery Overview
Call NowEmail Us
Call NowEmail Us