Lesson 2: SATA, NVMe, PCIe, SAS, M.2, and mSATA

Core path: 42 minutes

One of the most common storage mistakes is treating form factor and interface/protocol as if they mean the same thing.

They do not.

Form factor versus interface

M.2 describes a physical card/slot form factor.

mSATA is an older compact SSD form factor/interface design that looks card-like but is not the same as M.2.

NVMe is a storage protocol designed for high-performance storage over PCI Express.

SATA and SAS are storage interface families.

PCIe is the high-speed interconnect that commonly carries NVMe traffic.

So this statement is incomplete:

It is an M.2 SSD, so it must be NVMe.

You still have to check the device and motherboard slot.

SATA

SATA is widely used for 2.5-inch SSDs and hard drives.

A SATA storage device normally needs:

• a SATA data connection to the motherboard/controller;
• a SATA power connection from the power supply.

NVMe over PCIe

NVMe SSDs commonly connect through PCIe using M.2 slots or expansion cards.

They can provide much greater throughput and lower latency than SATA storage, but compatibility still depends on the motherboard and slot capabilities.

SAS

Serial Attached SCSI (SAS) is common in enterprise/server storage environments. SAS controllers and drives support features/workloads different from ordinary desktop SATA environments.

Technician rule:

Do not assume a SAS drive can be connected to a normal desktop SATA port just because the connector families look related.

Controller support matters.

M.2 dimensions and keying

M.2 modules come in different lengths. A common example is 2280, meaning approximately 22 mm wide and 80 mm long.

The mounting point and slot need to support the module length.

Keying and motherboard support also matter. Never assume every M.2 device works in every M.2-shaped slot.

mSATA recognition

mSATA was used in some older laptops and compact systems. It is physically different from M.2 and should not be treated as interchangeable even when both are small card-style SSDs.

Technician scenario

A student installs an M.2 SSD. It physically fits, but firmware does not detect it.

Possible checks include:

1. verify whether the drive is SATA or NVMe;
2. verify what protocol that motherboard slot supports;
3. verify module seating;
4. inspect firmware storage settings;
5. check whether using that slot disables or shares lanes with another interface.

Do not immediately declare the SSD dead.

Student action

For each proposed drive, record:

• storage type;
• form factor;
• interface/protocol;
• physical connection;
• required power path;
• controller/motherboard compatibility evidence.

Include examples of SATA 2.5-inch, NVMe M.2, mSATA, and SAS.

Evidence checkpoint

You should be able to distinguish:

• SATA and SAS as storage interface families;
• PCIe as a high-speed interconnect path;
• NVMe as a storage protocol commonly carried over PCIe;
• M.2 and mSATA as distinct compact storage form factors/interfaces.