A technician is attempting to upgrade an older corporate laptop with a new M.2 2280 solid-state drive (SSD). The laptop's technical specifications state that its internal M.2 slot is B-keyed and routed exclusively to an internal SATA III controller. The technician inserts an M-key PCIe NVMe M.2 SSD into the expansion slot using a physical adapter, but the drive fails to register in the UEFI/BIOS system setup screen. Which of the following is the most likely cause of this issue?
- The motherboard slot interface provides only SATA bus connectivity, which cannot communicate with an NVMe PCIe protocol drive.Answer
- BThe technician forgot to enable AHCI mode in the UEFI settings prior to physically seating the NVMe drive.
- CThe system RAM must be reconfigured into dual-channel mode to allocate bandwidth for the NVMe controller.
- DThe technician bypassed the required troubleshooting step of clearing the CMOS before performing any storage hardware installation.
Answer
The motherboard slot interface provides only SATA bus connectivity, which cannot communicate with an NVMe PCIe protocol drive.
Although the M.2 form factor provides a standard card-edge interface, the underlying protocol (SATA vs. NVMe/PCIe) must be supported by the motherboard slot. A slot wired exclusively to a SATA III controller lacks the PCIe lanes required for an NVMe SSD to be initialized and recognized by the system UEFI.
Step-by-Step Solution
Key Concept
M.2 Interface and Protocol Compatibility (NVMe PCIe vs. SATA)