Examkin

Question

Difficulty: MediumStorage Devices and Interfaces

A technician is installing a secondary M.2 solid-state drive into a desktop motherboard. According to the motherboard user manual, the target M.2 slot is connected exclusively to four PCI Express lanes (PCIe x4) and does not route SATA controller lines. The technician installs an M.2 SSD that uses the SATA interface protocol. After turning on the system, the drive is not recognized in the UEFI/BIOS settings. Which of the following best explains why the drive is not detected?

  1. The M.2 slot lacks SATA protocol support, making it incompatible with SATA-based M.2 drives.Answer
  2. B
    NVMe storage controller drivers must be installed in the operating system before the motherboard firmware can register M.2 drives.
  3. C
    All M.2 form factor drives automatically default to NVMe speeds when inserted into an M-key socket.
  4. D
    The installed M.2 drive requires a separate 15-pin SATA power connector plugged directly into the drive module.

Answer

The M.2 slot lacks SATA protocol support, making it incompatible with SATA-based M.2 drives.
Although M.2 defines the physical card dimension and keying, the underlying data interface depends on motherboard trace routing. If an M.2 slot is wired exclusively for PCIe (NVMe) lanes, a SATA-protocol M.2 drive will not be recognized by the chipset or UEFI/BIOS firmware because there are no SATA data lines connected to that slot.

Step-by-Step Solution

1
Analyze the motherboard specifications and physical slot configuration.
The target M.2 slot is wired exclusively for PCIe x4 lanes and has no SATA controller lane connections.
M.2 host slots vary by motherboard model; some support both SATA and PCIe protocols, while others support PCIe/NVMe only.
2
Evaluate the drive's protocol requirement against slot capability.
The installed drive relies on the SATA protocol, which cannot transmit signal data over dedicated PCIe bus lines.
Protocol compatibility is required at the electrical and firmware level for the drive to initialize during POST.
3
Determine why the UEFI/BIOS fails to list the device.
The drive fails to initialize because no SATA controller interface exists on that specific M.2 connector.
Without electrical protocol support from the motherboard controller, the device cannot communicate with firmware.

Key Concept

M.2 Protocol vs. Form Factor Compatibility (SATA vs. NVMe/PCIe)
Rate this question

Topics

Storage Devices and Interfaces

More questions from this topic