Storage controllers

Adaptec AAC RAID family (0285)

This Adaptec AAC pair deliberately identifies a family, not one card. The upstream table and guide list many different boards distinguished by their subsystem IDs under the same 9005:0285 pair.

On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

The broad table catch-all matches this pair, while specific subsystem entries include different SCSI, SATA and SAS boards. An exact retail model needs the subsystem vendor/device pair.

Curated identifiers
pci 9005:0285

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

aacraid is the kernel candidate. The driver has separate physical-device exposure and logical-volume behavior, so a successful probe does not mean that every physical member appears as its own block device.

  • aacraid — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

Controller firmware, option ROM and drive firmware can be separate. The reviewed sources do not establish a host-loaded filename for this profile; firmware revision and update policy require the actual controller and OEM identity.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Check the PCI function and bound driver

lspci -nnk -s BDF

Replace BDF with the domain:bus:device.function address. Look for [9005:0285] and Kernel driver in use. aacraid in Kernel modules is only a candidate, not proof of binding.

Inspect visible block-device identities

lsblk -d -o NAME,MODEL,TRAN,HCTL

MODEL describes a block device or a controller-presented logical volume; it is not a PCI-controller identity. HCTL helps distinguish SCSI targets. TRAN can be absent, and this list does not establish the complete physical disk topology.

Read controller and transport messages

sudo journalctl -k -b --no-pager

Elevated access may be needed. Root reads the current boot kernel journal. Associate aacraid messages, port/host identifiers and timeout/reset timestamps with the actual controller. A reset message alone does not prove a bad disk or a firmware defect.

Limitations & related issues

Do not collapse this shared PCI pair into a modern SATA-only card profile. Array health and firmware behavior need the actual board context; reading generic block-device inventory cannot establish redundancy.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.