Yes, most M.2 or PCIe to SATA adapters support SMART data passing, but this depends entirely on the adapter’s chipset and whether it implements proper command passthrough. You can verify support by running diagnostic tools like CrystalDiskInfo or smartctl; if the drive attributes appear correctly without errors, the adapter is successfully relaying SMART information from the SATA drive to your system.
Understanding How Adapters Handle SMART Data
When you connect a standard SATA hard drive or SSD through an M.2 or PCIe expansion card, the operating system does not communicate directly with the storage device. Instead, all commands must pass through the adapter’s controller chip. For SMART technology to function, the adapter must be capable of translating the ATA Command Set features into the interface protocol used by the host bus (such as NVMe or proprietary PCIe protocols) and back again. This process is known as command passthrough. Not all controllers are created equal. High-quality adapters typically use well-documented chips from manufacturers like ASMEDIA or JMICRON, which have robust firmware designed to handle complex ATA commands. However, cheaper or older adapters may lack the necessary firmware logic to interpret SMART requests. In these cases, the adapter might ignore the request or return generic error codes instead of the actual health status data. This limitation means that while the physical connection works for reading and writing files, the crucial predictive failure indicators provided by SMART remain inaccessible to software utilities. It is also important to distinguish between native M.2 NVMe drives and SATA drives connected via an M.2-to-SATA bridge. Native NVMe drives have their own distinct SMART implementation over the NVMe protocol. The question here specifically addresses SATA drives plugged into an M.2 slot using an adapter. These SATA drives still rely on the traditional AHCI/ATA SMART standards, making the adapter’s ability to pass these specific legacy commands critical. If the adapter fails to pass these commands, you lose visibility into real-time health metrics like temperature, power-on hours, and reallocated sector counts. For users concerned about data integrity, relying on an adapter that does not support SMART is risky. Without access to these metrics, you cannot detect early signs of drive degradation, such as increasing bad sectors or failing read/write heads. Therefore, verifying adapter compatibility is a vital step before deploying critical storage solutions in RAID configurations or as primary boot drives. If you suspect your current setup lacks support, testing with multiple diagnostic tools can help confirm whether the issue lies with the software configuration or the hardware limitations of the adapter itself.Common Chipsets That Support SMART Passthrough
To ensure reliable SMART monitoring, look for adapters featuring specific, widely supported chipsets. The ASMedia ASM1061 and ASM1062 are among the most common and reliable choices for PCIe to SATA bridges. These chips are mature, well-supported by major operating systems, and explicitly designed to handle full ATA command sets, including SMART. Similarly, many modern M.2 NGFF to SATA converters utilize the JMicron JMS578 or JMS579 chips, which also offer excellent compatibility with SMART data retrieval. If you are purchasing an adapter, checking the product specifications for the chipset model is more reliable than trusting general marketing claims. Reviews often mention whether SMART was tested successfully with specific tools. Avoid adapters that do not disclose their internal controller, as these are likely using generic or poorly documented silicon that may drop non-essential commands like SMART queries to save processing overhead.How to Verify SMART Support on Your Adapter
Verifying whether your adapter supports SMART requires using dedicated diagnostic software rather than relying on the operating system’s basic disk properties. On Windows, tools like CrystalDiskInfo provide a user-friendly interface that displays detailed SMART attributes for each detected drive. On Linux, the command-line toolsmartctl from the smartmontools package offers deep inspection capabilities. macOS users can utilize DriveDx or the built-in Terminal command system_profiler SPStorageDataType, though third-party tools often provide more granular details for external bridges.
Start by installing CrystalDiskInfo and launching it with administrative privileges. Look at the list of drives. If your SATA drive connected via the M.2 adapter appears with its correct model name and shows tabs for "Health Status," "Temperature," and "Power On Count," then SMART is working. If the drive appears as "Unknown" or shows no health data, the adapter is likely blocking the commands.
For Linux users, open a terminal and run sudo smartctl -a /dev/sdX, replacing sdX with your target drive identifier. A successful response will include a section titled "SMART overall-health self-assessment test result: PASSED" followed by a table of attribute IDs and values. If you receive an error stating "SMART command failed" or "Device does not support SMART," the adapter does not support passthrough for this specific drive or controller combination.