Adaptec ASR-71605 Data Recovery: 71605, 71605Q and 71605E Failures, Error Messages, and Upgrade Traps

The Adaptec ASR-71605 is the most widely deployed card in Adaptec’s Series 7 family: sixteen internal 6 Gb/s SAS/SATA ports on a low-profile card, built into countless 16-bay storage servers, surveillance and media systems, and — since the cards began selling secondhand for about the price of a lunch — home labs and budget NAS builds. That long life means the 71605 fails in ways that have nothing to do with its original design: it overheats in cases it was never meant for, it arrives from the used market in a mode or firmware its new owner does not expect, and it gets replaced by a newer Adaptec card that cannot read its arrays.

This page covers what is specific to the 71605, 71605Q, and 71605E. The complete catalog of Series 7 messages — POST screens, arcconf states, maxView events, Linux aacraid and Windows arcsas log entries, each rated by risk — is on our Adaptec Series 7 recovery page.

71605, 71605Q, 71605E: Three Cards That Fail Differently

	ASR-71605	ASR-71605Q	ASR-71605E
Internal ports	16 (4 × SFF-8643)	16 (4 × SFF-8643)	16 (4 × SFF-8643)
Cache	1 GB DDR3	1 GB DDR3	256 MB DDR3
Flash cache protection	AFM-700 optional	AFM-700 pre-installed	Not supported
RAID levels	0, 1, 1E, 5, 6, 10, 50, 60, Simple Volume	Same as 71605	0, 1, 1E, 10 only
SSD caching	No	maxCache 3.0 (up to 8 SSDs, 2 TB)	No
Host interface	PCIe 3.0 x8, PMC-Sierra PM8015 RAID-on-chip, up to 256 drives with expanders

Which variant you have changes what can go wrong. A 71605E cannot have a failed RAID 5 or RAID 6 because it cannot build one; its arrays are mirrors and stripes, and its risks center on unprotected cache. A 71605Q can hold write data on its SSD cache pool that has not yet reached the hard drives. A plain 71605 may or may not have a flash module — and many secondhand cards have had theirs removed.

Heat: The 71605’s Defining Failure Mode

The 71605 was designed for rack servers with front-to-back airflow across the PCIe slots. Adaptec’s specification for Series 7 cards is an operating range of 0–55 °C with 200 linear feet per minute of airflow, reduced to 0–50 °C with the flash module installed. In a tower case, a NAS enclosure with a single rear fan, or a server whose fans have failed, the card’s heatsink does not get that airflow.

Owners in home-lab communities describe the card as drawing roughly 15 watts continuously and needing a dedicated fan over the heatsink. One widely read forum thread about two “dead on arrival” used 71605s concluded that many decommissioned cards had overheated in service, and noted that the heatsink on these cards is attached with an adhesive thermal compound — so a heatsink knocked loose in handling can damage the chip beneath it. Other owners report the card’s onboard alarm “squealing” when it runs hot.

What overheating looks like before the array fails

• Intermittent aacraid: Host adapter abort request and Host bus reset request. SCSI hang ? messages on Linux, or Event ID 129 resets from the arcsas source on Windows, especially under sustained load.
• Drives dropping out of arrays and reappearing, producing “degraded” arrays whose members all test healthy.
• “Write-through (temporary disabled)” on cards with an AFM-700, because the supercapacitor’s over-temperature protection has disabled the backup unit.
• Eventually, a card that hangs at “Booting the Controller Kernel” or no longer completes POST at all.

What to do

If the array is still online, back it up before improving the cooling — opening the case and reseating things is itself a risk. If the card has already stopped posting, the drives are almost always fine and the array configuration is on them. The danger is the replacement: see choosing a replacement card below.

Sixteen Ports, Four Connectors, and the “Four Drives Failed at Once” Symptom

The 71605’s sixteen ports are grouped into four mini-SAS HD connectors, CN0 through CN3, each carrying four drive lanes when direct-attached. That grouping is a useful diagnostic: if exactly four drives drop out at the same moment and all four sit on the same connector, the likely culprit is the cable, the backplane segment, or the connector — not four simultaneous drive failures. If those four drives were spread across your array’s members, that single fault can take a RAID 5, RAID 6, or even RAID 60 offline instantly.

That array is usually fully recoverable, provided no one “fixes” it by initializing the dropped drives or forcing the array online with members that came back at different times. Before touching the array, record which connector and which bay each drive occupies. Series 7 arrays identify members by metadata rather than by port, but the physical map helps establish the sequence of events.

Behind an expander backplane, the 71605 can address far more than sixteen drives. Adaptec documents a separate problem there: some expanders do not finish discovering drives before the controller firmware looks for them, so a logical device can come up marked failed after a reboot even though every drive is healthy. The fix is a minimum expander scan duration setting — a configuration change, not a data operation.

The Secondhand-Card Trap: Controller Modes

Secondhand 71605s are popular because they can run as a plain HBA without the firmware cross-flashing some other brands require — the mode is a setting in the card’s configuration utility. The available modes on current firmware are RAID: Expose RAW, RAID: Hide RAW, HBA, Auto Volume, and Simple Volume. The trouble is that a used card arrives in whatever mode its last owner left it, and the listing often says only “HBA mode” or “IT mode.”

• Auto Volume automatically converts drives that have no Adaptec metadata and no OS partitions into Simple Volumes, writing Adaptec metadata to them. Drives that do carry OS partitions are passed through.
• Simple Volume disables RAID entirely and presents only single-drive Simple Volumes.
• HBA passes every drive through raw. Adaptec’s guidance is to select it only when no drives with Adaptec metadata are attached — switching a card that holds RAID arrays into HBA mode exposes the raw members to the operating system.

One home-lab owner described installing a 71605 believed to be in HBA mode, moving existing data drives onto it, and discovering after the first boot that the card had been in Simple Volume mode and the drives were no longer mountable — after which a file system repair replaced a primary superblock. The lesson generalizes: check and set the controller mode before any drive with data on it is connected to a used 71605.

Checklist for installing a used 71605 without risking data

1. Install the card with no drives attached. Boot into the Ctrl-A utility or UEFI setup and confirm the controller mode.
2. Check the firmware build (ARCCONF GETVERSION or the utility’s controller details). See firmware below.
3. Confirm cooling before loading it with sixteen drives.
4. Connect one expendable drive first and confirm how the card presents it.
5. Only then connect drives carrying data.

Firmware on the 71605

The 71605 shares the Series 7 firmware line (7.5.0). A few builds have particular significance for 71605 owners:

Build	What 71605 owners should know
32033 (August 2014)	At least one storage integrator told 71605 customers to move past this build, citing multiple drives reported degraded at once when they were not defective, and volumes disappearing from the operating system.
32084	The build integrators recommended at the time.
32106 (2016)	Reported on 71605 cards to leave write cache stuck at “Write-through (temporary disabled)” regardless of the flash module’s condition. The reported workaround was rolling back to 32084.
32114 (2017)	Patch release fixing RAID 5 and RAID 6 logical drives that would not rebuild, a firmware stack overflow triggered by a faulty drive, write cache that could not be enabled without a flash module, and “Error: Controller Kernel Stopped Running” at POST.
32118 (2018)	The last build on Adaptec’s public 71605 support page.
7.6-0 (32136)	Found on many 71605 cards sold secondhand, and not a public Adaptec release; owners believe it is an OEM build. Users have reported recurring aacraid: Host adapter abort request errors on it, and reported rolling back to 32118 without bricking the card.

A firmware change on a 71605 that currently holds a degraded or failed array should wait until the data is safe. The fixes in 32114 are real, but a firmware update is the wrong moment to discover that the card is unstable.

Choosing a Replacement Card (and the 81605ZQ Problem)

When a 71605 dies, the natural replacement is “the next Adaptec” — often a Series 8 card such as the ASR-81605ZQ, which has the same port count and a newer 12 Gb/s interface. It will not read the old arrays.

One administrator documented this exact migration in detail: a 71605 running build 32118, replaced with an 81605ZQ, both cards set to RAID: Expose RAW. All eleven drives appeared in arcconf getconfig 1 pd as Ready rather than Foreign. No arrays were listed under Manage Arrays, no logical drives were visible in Windows 11 or maxView, and neither the POST screens nor the Ctrl-A utility offered any “scan for foreign configuration” or import option. That is consistent with how Series 8 treats earlier-generation Adaptec metadata.

The drives in that situation are intact. Three things destroy them from there:

1. Creating a new array on the Series 8 card with the old drives, in an attempt to “recreate” the original layout.
2. Initializing the “Ready” drives so the new card can use them.
3. Letting Windows or a Linux installer see the raw drives — in Expose RAW mode they are passed straight through — and initializing or partitioning them.

If you still have access to a working Series 7 card with compatible firmware, it will normally read the arrays: power down, move the drives, confirm the card is in RAID mode, and do not accept any configuration-change prompt at POST until every member shows up. If you do not, or if the original card failed mid-rebuild or after members had already dropped out, the arrays should be reconstructed offline from drive images.

The 71605E: No Parity, Less Cache, No Protection

The 71605E is the entry-level variant: sixteen ports, 256 MB of cache, no flash backup support, and only RAID 0, 1, 1E, and 10. That changes the failure profile:

• RAID 0 and RAID 10 stripes on a 71605E are common in video and scratch storage. A single failed drive in RAID 0, or both drives of a mirror pair in RAID 10, takes the volume offline. The failed drive can often be repaired enough to image in a cleanroom.
• Unprotected write-back cache. With no flash module, any write-back caching configured on a 71605E holds data only in volatile memory. The card displays a cache warning when write caching is enabled without protection. After a power loss or hard crash, the file systems on its arrays can be missing writes the operating system believed were complete. Running a file system repair on such a volume without first imaging the drives can turn a small inconsistency into a large one.

The 71605Q: Send the SSDs Too

The 71605Q adds maxCache 3.0, which uses up to eight SSDs as a read and optional write cache in front of the hard-drive arrays. Adaptec’s configuration default for maxCache write caching is disabled; when it is enabled, the SSD cache can hold writes that have not yet been copied to the hard drives.

For recovery, that means the cache SSDs may be part of the data. If a 71605Q array fails, ship the maxCache SSDs along with the hard drives, labeled by port. Do not delete the maxCache device, remove the SSDs from the pool, or reinitialize them in an attempt to get the hard-drive array back online.

71605 Messages: Quick Index

The most common messages 71605 owners search for, with links to the full explanation and risk rating on our Series 7 page:

• “Controller detected configuration change” / “The following arrays have missing members and cannot be configured”
• “Booting the Controller Kernel” hang
• arcconf “Status of logical device”: Degraded, Suboptimal, Impacted, Failed
• “Failed stripes : Yes”
• “Initializing Channel 0, Device 7 will erase its metadata…”
• Force online (Ctrl+F, maxView, arcconf setstate optimal)
• “aacraid: Host adapter abort request”
• “Device offlined – array failed”
• Windows Event ID 129, 11, 9 from arcsas
• “Write-through (temporary disabled)”

If Your 71605 Array Is Down Right Now

1. If the volume is still accessible, copy the most important data off it before any rebuild or cooling work.
2. Capture ARCCONF GETCONFIG 1 AL and ARCCONF GETLOGS output, or photograph the POST and Ctrl-A screens, before changing anything.
3. Label every drive with its bay and its connector (CN0–CN3), and note serial numbers.
4. Do not change the controller mode, flash firmware, or move the drives to a Series 8 or SmartRAID card.
5. Do not connect member drives to a Windows or Linux computer.
6. On a 71605Q, keep the maxCache SSDs with the hard drives.

How We Recover 71605 Arrays

We image every member drive — hard drives and any maxCache SSDs — on write-blocked hardware in our ISO 5 Class 100 cleanroom, repairing physically damaged drives with donor parts first. Our HOMBRE reconstruction software reads the Series 7 metadata from each image, establishes member order, stripe size, and parity layout, and determines which members dropped out and when. The array is assembled virtually — no 71605, no replacement controller, no firmware involved — and the file systems are recovered from the assembled volume. The full Series 7 recovery approach is described on our Adaptec Series 7 page.

ASR-71605 Documentation

• Serial Attached SCSI RAID Controllers Installation and User’s Guide — 71605, 71605Q, and 71605E specifications, AFM-700 installation, and the Ctrl-A utility
• Adaptec RAID Controller Command Line Utility (arcconf) User’s Guide
• Series 7 / Series 8 Readme — controller modes and known limitations
• Adaptec RAID 71605 firmware/BIOS download page (build 32033)
• Adaptec KB: RAID, Auto Volume, HBA, and Simple Volume modes

ASR-71605 Frequently Asked Questions

Is the 71605 an HBA or a RAID controller?

Both. It is a hardware RAID controller that can be switched into HBA mode, where every drive is passed through raw, without reflashing. That flexibility is why so many are in home labs — and why a used card’s mode must be checked before data drives are connected.

Four drives disappeared from my array at once. Are they all dead?

Almost certainly not. On a 71605, four drives share each connector. Four simultaneous drops on one connector point to a cable, backplane, or connector fault. Do not initialize the drives or force the array online; record the layout and power down.

My 71605 runs hot. Can I keep using it?

Only with proper airflow across the heatsink. Adaptec specifies 200 linear feet per minute. Overheating 71605s tend to degrade gradually — resets, dropped drives, then POST hangs — so treat heat-related log messages as an early warning and back up.

Will an ASR-81605ZQ or SmartRAID card read my 71605 arrays?

No. The drives show as Ready with no import option. Do not create or initialize anything on the new card. Use another Series 7 card, or have the arrays reconstructed from images.

My used 71605 has firmware 7.6-0. Is that a problem?

It is not a public Adaptec release, and some users have reported abort errors on it. Owners report rolling back to 32118, the last public build. Do any firmware change with no data drives attached.

What should I send you?

Every drive that was attached to the card, labeled by bay and connector — including maxCache SSDs on a 71605Q. We do not need the server, and in most cases we do not need the controller.

Start Your ASR-71605 Recovery

Power the system down, label the drives, and do not initialize, force, recreate, or migrate anything. Our engineers image every member and reconstruct the array without the controller. Gillware has been recovering RAID arrays for more than two decades.