Marvell 88SE9230 SATA IDENTIFY Failures

Summary

Linux systems using the Marvell 88SE9230 4-port SATA controller can show simultaneous ATA IDENTIFY/I/O failures across all attached SATA drives, making the problem look like multi-drive failure even when the controller itself is still visible in PCI enumeration (#43857).

Frequency

1 ticket

Common Causes

1. Controller/path-level failure or compatibility behavior when all attached SATA devices fail SMART/IDENTIFY in lockstep and filesystems drop read-only after journal aborts (#43857).
2. Linux/platform interaction with the Marvell 88SE9230 on ASUS ESC8000A-E12-class systems where Support associated repeated IDENTIFY failures, SATA link reset cycles, and missing block devices with known controller-specific behavior (#43857).
3. Asset/quote mismatch blocking replacement decisions when the reported platform and the provided quote or serial do not match Exxact records (#43857).

Diagnostic Steps

1. Confirm whether the Marvell 88SE9230 appears in lspci, because this failure mode may still enumerate the controller even while all downstream SATA devices fail IDENTIFY (#43857).
2. Compare BIOS storage inventory, lsblk, SMART/IDENTIFY attempts, dmesg ATA reset/IDENTIFY errors, and whether all attached SATA channels fail together rather than one drive at a time (#43857).
3. On the ASUS ESC8000A-E12 path, check BIOS Generic Mode and update/test a newer kernel before assuming full system replacement is required (#43857).
4. Validate the Exxact serial, quote, or PO and request system photos if records do not match the reported platform before initiating replacement or system RMA (#43857).

Solutions

1. Try BIOS Generic Mode plus kernel update first for the known Marvell 88SE9230/Linux pattern on ASUS ESC8000A-E12-type systems (#43857).
2. Escalate to system RMA or replacement evaluation if Generic Mode and kernel update do not resolve the simultaneous IDENTIFY failures and asset validation confirms the covered system (#43857).
3. Do not treat four simultaneous SMART/IDENTIFY failures as four independent drive failures without controller/path isolation; all channels failing in lockstep points toward the controller or platform path (#43857).

Edge Cases

• The controller can still be identified by lspci while every attached SATA device fails IDENTIFY, contradicting the simpler HBA-failure pattern where the add-in card disappears entirely from BIOS/OS inventory (#43857).
• This ticket closed no-response, so the wiki should treat BIOS Generic Mode and kernel update as suggested next steps rather than confirmed resolution (#43857).

Related Issues

• HBA Card Failure
• Defective Storage Drives
• BIOS Firmware Update