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

Storage terminology has a bad habit of mixing physical shape, electrical interface, transport path, and protocol into one conversation.

That is why people say things like:

"It is an M.2 drive, so it is NVMe."

No.

M.2 and NVMe do not describe the same layer.

Once you separate the layers, the naming becomes much easier to reason about.

Start with four different questions

When looking at a storage device, ask:

1. What physical form does it use?
2. What connector or bus carries the traffic?
3. What protocol or command set does the storage use?
4. What does the motherboard or controller actually support?

Those questions prevent most compatibility mistakes in this topic.

System process animation

A storage request crosses seven boundaries

Trace one request down to physical media before naming the failed layer.

RestartPreviousPlay sequenceNext

1. 1ApplicationA program requests a file or block operation.
2. 2FilesystemNames and metadata map the request to stored blocks.
3. 3OS storage stackThe kernel queues and schedules I/O.
4. 4ControllerA controller translates and schedules device commands.
5. 5InterfaceSATA, PCIe/NVMe, USB, or network transport carries the command.
6. 6DeviceDrive firmware processes the command.
7. 7MediaFlash cells or magnetic media store and return bits.

Technician question: What separates a filesystem fault from a device fault?

SATA is a storage interface family

SATA has been widely used for:

• 3.5-inch hard drives;
• 2.5-inch hard drives;
• 2.5-inch SATA SSDs;
• some optical drives;
• some M.2 SATA SSDs.

A typical 2.5-inch SATA SSD needs two separate paths:

motherboard/controller
        ↓
SATA data cable
        ↓
       SSD
        ↑
SATA power cable
        ↑
power supply

That gives us separate data and power failure boundaries.

A device can be mounted perfectly and still be invisible because one of those paths is missing.

PCIe is the high-speed interconnect

PCI Express, or PCIe, is a high-speed communication path used by many devices, not just storage.

You already saw PCIe with expansion cards.

Storage can use PCIe too.

NVMe SSDs commonly communicate over PCIe, often through an M.2 slot or an expansion-card form factor.

This is why saying "NVMe is faster than M.2" does not make sense.

One is a protocol commonly carried over PCIe. The other is a physical form factor.

They are answering different questions.

NVMe is a storage protocol

NVMe was designed for nonvolatile storage using PCIe and modern parallel storage behavior.

Compared with SATA-based storage, PCIe/NVMe devices can offer much higher throughput and lower latency, depending on the implementation and workload.

But NVMe support still depends on the system.

You need to verify:

• the M.2 slot supports PCIe/NVMe if that is the device type;
• the slot supports the module length;
• firmware can detect and boot from the device when required;
• lane sharing or port conflicts do not disable another device unexpectedly.

Fast hardware still has to fit the platform design.

M.2 describes a physical card and slot family

M.2 modules come in different lengths.

A common size is 2280:

• 22 mm wide;
• 80 mm long.

Other lengths exist.

The board needs the correct mounting point and slot support.

M.2 keying and interface support also matter.

Most importantly:

An M.2-shaped SSD may use SATA or PCIe/NVMe.

The shape does not settle the protocol question.

mSATA is a different older compact design

mSATA is an older compact SSD form and interface used in some laptops and small systems.

It is not the same as M.2.

Both can look like small exposed circuit-board storage modules, which is exactly why people confuse them.

Do not use appearance as compatibility evidence.

Check the connector and system documentation.

SAS belongs to a different storage environment

SAS stands for Serial Attached SCSI.

It is common in enterprise and server storage environments.

SAS systems may use dedicated controllers, backplanes, redundant paths, and features designed for enterprise workloads.

A SAS drive should not be treated as a normal desktop SATA drive just because parts of the connector family look related.

Controller support matters.

Again, visual similarity is weak evidence.

The same form factor can hide different paths

Consider two M.2 SSDs.

Drive A:

M.2 form factor
SATA storage path

Drive B:

M.2 form factor
PCIe path
NVMe protocol

Both may look similar from a distance.

The motherboard may support both, only SATA, only PCIe/NVMe, or different capabilities in different slots.

That is why the slot documentation matters more than the marketing photo.

Lane sharing can create surprising side effects

Some motherboards share PCIe lanes or chipset resources between storage connectors.

Installing one M.2 device may disable:

• a SATA port;
• another M.2 slot;
• part of an expansion-slot configuration.

This does not mean the motherboard is defective.

It may be working exactly as designed.

If a SATA drive disappears immediately after installing an M.2 SSD, read the board documentation before replacing anything.

The change history gives you a clue.

Worked example: M.2 drive fits but firmware cannot see it

Evidence:

module: fully seated
physical size: supported
firmware: no drive detected
new drive: M.2 SATA
motherboard slot: PCIe/NVMe-only

Is the drive dead?

No evidence proves that.

The earlier compatibility boundary already fails: the slot does not support the drive's storage interface.

The device can fit mechanically and still have no usable communication path.

Worked example: NVMe installed, old SATA drive vanishes

Evidence:

before change: SATA drive detected
new change: NVMe SSD installed in M.2 slot 2
after change: SATA port 5 device missing
motherboard manual: M.2 slot 2 shares resources with SATA port 5

What happened?

The board's resource-sharing design disabled the SATA port when that M.2 slot became active.

This is not random failure.

The system state changed because the platform rules changed.

Move the SATA device to a supported active port or choose a different storage configuration according to the documentation.

Build a storage-interface map

For each of these device classes, record:

• physical form factor;
• interface or transport path;
• protocol when relevant;
• power path;
• controller or motherboard requirement;
• one common compatibility mistake.

Include:

• 2.5-inch SATA SSD;
• M.2 SATA SSD;
• M.2 NVMe SSD;
• mSATA SSD;
• SAS drive.

Do not write "SSD" as if that answers every row.

Before you move on

You should now be able to correct these statements:

M.2 means NVMe.

Any small card-style SSD fits any small card-style slot.

SAS is just faster SATA.

If the drive physically fits, the board should detect it.

The better model is:

form factor
   +
interface/bus
   +
protocol
   +
controller/platform support
   =
a usable storage path

Next we move from one drive to several and deal with another common misconception: RAID is not backup.