Advanced Host Controller Interface
||This article needs additional citations for verification. (August 2012)|
The specification describes a system memory structure for computer hardware vendors to exchange data between host system memory and attached storage devices. AHCI gives software developers and hardware designers a standard method for detecting, configuring, and programming SATA/AHCI adapters. AHCI is separate from the SATA 3 Gbit/s standard, although it exposes SATA's advanced capabilities (such as hot swapping and native command queuing) such that host systems can utilize them.
As of October 2010[update], the current version of the specification is v. 1.3.
 Operating modes
Many SATA controllers offer selectable modes of operation: legacy Parallel ATA emulation, standard AHCI mode, or vendor-specific RAID (which generally enables AHCI in order to take advantage of its capabilities). Intel recommends choosing RAID mode on their motherboards (which also enables AHCI) rather than AHCI/SATA mode for maximum flexibility. Legacy mode is a software backward-compatibility mechanism intended to allow the SATA controller to run in legacy operating systems which are not SATA-aware or where a driver does not exist to make the operating system SATA-aware.
 Operating system support
AHCI is supported out of the box on Windows Vista and newer versions of Windows, Linux-based operating systems (from kernel 2.6.19 onwards), OpenBSD (version 4.1 onwards), NetBSD, FreeBSD, OS X, eComStation (version 2.1 onwards), and Solaris 10 (8/07 and onwards). DragonFlyBSD based its AHCI implementation on OpenBSD's and added extended features such as port multiplier support. Older versions of operating systems require hardware-specific drivers in order to support AHCI. Windows XP does not provide support out of the box.
 Boot issues
Some operating systems, notably Windows Vista and Windows 7, do not configure themselves to load the AHCI driver upon boot if the SATA-drive controller was not in AHCI mode at the time of installation. This can cause failure to boot, with an error message, if the SATA controller is later switched to AHCI mode. For this reason, Intel recommends changing the drive controller to AHCI or RAID before installing an operating system. (It may also be necessary to load chipset-specific AHCI or RAID drivers — from a USB Flash drive, for example — at installation time.)
On Windows Vista and Windows 7, this can be fixed configuring the
msahci device driver to start at boot time (rather than on-demand). Setting non-AHCI mode in the BIOS will allow the user to boot Windows, where the required registry change can be performed. The BIOS can then be changed to AHCI.
On Windows 8 and Windows Server 2012, the name of the controller has changed from
storahci, and the procedure to upgrade to the new controller to it is similar to that of Windows 7. On Windows 8 and Windows Server 2012, changing the SATA mode to AHCI without updating the registry will make the boot drive inaccessible.
A similar problem can occur on Linux systems if the AHCI driver is built as a module, rather than included in the kernel, as it may not be loaded into the initrd (initial RAM disk) created when in legacy mode; the workaround is to build a new initrd containing the AHCI module.
 Power management
Power management is handled by the Aggressive Link Power Management (ALPM) protocol.
- "Intel Matrix Storage Technology - Changing and/or choosing Serial ATA Modes". Intel. Retrieved 2007-09-30.
- "What's New in the Solaris 10 8/07 Release - Driver Enhancements". Oracle. Retrieved 2010-10-20.
- "Error Message when you start a Windows 7 or Windows Vista-based computer after you change the SATA mode of the boot drive: "STOP 0x0000007B INACCESSABLE_BOOT_DEVICE"". Microsoft. Archived from the original on 24 May 2011. Retrieved 2011-04-20.
- "StorAHCI replaces MSAHCI (Windows)". Microsoft.
- "Improving performance of SATA drives on Windows 2012".
- "How to ADD one module to initrd using mkinitrd". ServerFault. Retrieved 2011-04-20.[unreliable source?]
- "SATA disks as AHCI". FedoraForum. Retrieved 2011-04-20.[unreliable source?]