"No bootable device" or a drive missing from the firmware setup can mean a failed SSD, a firmware setting, an incompatible drive or a board fault in the slot's power or signals. Because the cheapest explanation is often a setting and the most expensive is a dead drive full of data, it pays to work through the possibilities in order. This guide covers M.2 SATA and NVMe drives and the board circuits behind them.
Step 1: is it detected anywhere?
| Where the drive appears | Meaning |
|---|---|
| In the firmware setup, but the system will not boot | The drive is detected; boot configuration or the installed system is the issue |
| In the firmware setup, but not in the operating system installer | Storage mode setting or missing driver |
| Nowhere | Drive, slot, power or signals |
Only the last case is a board-level question.
Step 2: storage mode settings
Some laptops configure storage in a mode where the drive sits behind a storage controller layer — often called RAID or a volume management mode on Intel platforms. In that mode, some operating system installers do not see the drive until a driver is loaded, even though the firmware does. Changing the mode affects an existing installation, so note the original setting before experimenting.
Step 3: SATA or NVMe — the right drive for the slot
M.2 slots come in different keys and support different interfaces:
| Slot | Supports |
|---|---|
| M key, PCIe only | NVMe drives |
| M key, SATA only (older designs) | M.2 SATA drives |
| M key, both | Either |
| B+M drives | Usually SATA; fit some slots physically but not electrically |
A drive that fits the slot is not necessarily supported by it. Check the schematic or service manual: an NVMe drive in a SATA-only slot, or the reverse, will not be detected. The connector is described under m2 slot, and the interfaces under nvme and sata.
Step 4: test with a known-good drive
A known-good drive of the type the slot supports is the quickest decision:
- Known-good drive detected — the original drive has failed.
- Known-good drive not detected — the board or a setting is at fault.
If the original drive holds important data and is not detected, avoid repeated power cycles and experiments with it; data recovery is a separate job.
Step 5: power at the slot
The M.2 slot takes 3.3 V on several pins, often through a load switch enabled when the system starts. With the laptop on:
- measure 3.3 V at the slot pins or their capacitors;
- if missing, check the switch's input and enable;
- with power removed, check the slot rail to ground for a short.
A drive with an internal short can pull the slot supply down; remove the drive and measure again.
Step 6: PCIe reset and clock
NVMe drives are PCIe devices. Like a wireless card, the drive needs:
- a released reset from the chipset (PERST# or similar);
- a reference clock, requested through a clock-request line on many designs;
- working transmit and receive pairs.
Measure the reset line with the laptop on — it should be at its released level. Check the clock-request line for continuity and its pull-up. The PCIe link in general is described under pcie, and the same signal checks for wireless cards are in Laptop Wi-Fi Card Not Detected: Board-Level Causes.
SATA drives
For M.2 SATA drives the checks are similar but the signals differ: a pair for transmit and a pair for receive, with coupling capacitors, plus the slot's 3.3 V supply. There is no PCIe reset or clock request; detection depends on power and the two pairs reaching the chipset intact.
Step 7: compare the lines
With power removed and the drive out, measure the slot's PCIe or SATA lines to ground in diode mode. Lines of the same type should read alike. An open line points at a broken trace, a missing coupling capacitor or a damaged slot pin; a shorted line points at a damaged part or chip pin.
Heat and intermittent detection
NVMe drives get hot, and some throttle or drop off the bus when they overheat. A drive that disappears after some minutes of heavy use and returns after cooling may simply need its thermal pad or heat spreader refitted. Check that any pad between the drive and the chassis or heatsink is in place before suspecting the slot.
Step 8: the slot itself
- Bent or burnt contacts.
- A cracked slot after a drop.
- A drive not fully seated, or a missing screw letting it lift.
- Corrosion.
Data first
When the original drive is not detected and holds data the owner needs, treat it carefully. Do not format, initialise or repeatedly power it in different machines. If a known-good drive shows the board is at fault, repair the board and try the original drive again. If the original drive itself has failed, data recovery is a specialised job; the less the drive is stressed beforehand, the better the chances.
Firmware and compatibility
Some laptops' firmware supports only certain drive types or capacities, especially older models with newer NVMe drives. A firmware update for the laptop can add support. Drives also have their own firmware; a drive with a known firmware problem may disappear intermittently until updated. Check both before replacing hardware, particularly when the drive works in other computers.
Soldered storage
Some thin laptops have the storage soldered to the board. There is no drive to swap; the same checks apply to the storage chip's supplies, reset and clock. A failed soldered storage chip usually means data loss and a board-level replacement with BGA work, and on encrypted designs the data is tied to the original chips.
Example: a new NVMe drive not detected
A user upgrades a laptop with a new NVMe drive, and it is not detected anywhere. The original drive, an M.2 SATA model, is still detected when refitted. The schematic shows the slot wired only for SATA: the PCIe lanes are not connected to it. The new drive fits mechanically but cannot work in that slot. A larger M.2 SATA drive solves the upgrade. The board was fine all along.
Example: no drive after a liquid spill
A laptop shows "no bootable device" after a spill. A known-good drive is also not detected. The slot's 3.3 V is present, but the PCIe reset line stays low with the laptop on. Following it from the slot towards the chipset in the boardview, a small series resistor is corroded and reads open. A new resistor lets reset release, and both drives are detected again.
FAQ
Why does the installer not see my drive when the firmware does?
The storage mode may need a driver. Load it or change the mode with care.
Can an M.2 SATA drive go in any M.2 slot?
No. The slot must support SATA. Check the schematic or service manual.
How do I know if the drive or the board is faulty?
Test with a known-good drive of the type the slot supports.
Can a shorted drive affect the board?
It can pull the slot's supply down. Remove it and measure.
What if the drive holds important data?
Avoid repeated experiments with it, and treat recovery as a separate task.
Bottom line
Check where the drive is visible, then storage mode settings and slot compatibility. Test with a known-good drive. If the board is at fault, check the slot's 3.3 V, the PCIe reset and clock request, the lines in diode mode and the slot's contacts. Soldered storage follows the same logic but needs BGA work.