One day your machine boots fine; the next, the BIOS shows no drive at all, or Windows throws a no-boot-device error. An M.2 NVMe SSD that has disappeared from the BIOS is alarming, but in most cases the drive itself is healthy — something is simply stopping the board from seeing it. The trick is to work through the causes in a sensible order rather than panicking and assuming the worst.
This guide walks you through that order, from the simplest fix to the rarest. If your machine won't boot because of this, you may also want to read our companion piece on the inaccessible boot device error, and if you are unsure how NVMe differs from older drives, our explainer on NVMe versus SSD versus HDD is a useful primer.
Start by reseating the drive
The most common cause in Nigeria is the simplest one: the card has worked slightly loose or lost good contact. Heat cycles, dust, and the jolts of transit all conspire to lift an M.2 card a fraction of a millimetre — enough to break detection. Before anything else, reseat it:
- Power off fully, switch off at the wall, and unplug the machine.
- Locate the M.2 slot and remove the small retaining screw holding the drive down.
- The drive will spring up to a slight angle. Pull it gently straight out of the slot.
- Inspect the gold contacts for dust; wipe gently with a dry, lint-free cloth if needed.
- Insert the drive back at the same angle, push it fully home, press it flat, and screw it down.
A surprising number of disappearing-drive cases are solved at this step alone. If the drive reappears in the BIOS, you are done.
Check for M.2 lane sharing — the big one
This is the cause most people miss. On many motherboards, M.2 slots do not have dedicated bandwidth; they share PCIe lanes with certain SATA ports or with a second PCIe slot. Populating one resource automatically disables another, so your NVMe can vanish the moment you plug in a SATA drive or fit a card into another slot.
- Open the motherboard manual and find the storage or M.2 configuration table.
- Note which M.2 slot is disabled when a particular SATA port is in use, or when the second PCIe slot is populated.
- If your NVMe is in a shared slot, either free the conflicting SATA port or PCIe card, or move the NVMe to a slot that is not affected.
- Reboot and check the BIOS — the drive should now appear.
If you are planning to run more than one fast drive, our guide to adding a secondary NVMe covers how to avoid these conflicts before they start.
Confirm the slot actually supports NVMe
Not all M.2 slots are equal. Some are SATA-only, some are NVMe-only, and a few support both. An NVMe drive dropped into a SATA-only slot — or a SATA M.2 drive in an NVMe-only slot — simply will not appear, no matter how firmly it is seated.
- Check the manual for each M.2 slot's supported interface and keying.
- If your NVMe sits in a SATA-only slot, move it to a slot that explicitly supports NVMe.
- Confirm the physical key and form factor match before forcing anything.
If keys, lengths, and form factors are a mystery, our breakdown of M.2 SSD types, 2280 and 2242 explains exactly what to look for so you do not buy or fit the wrong drive again.
Work through the BIOS settings
If the hardware is correct and the drive still hides, the BIOS itself may be at fault — a disabled slot, a wrong storage mode, or a firmware bug:
- Enter the BIOS and make sure the relevant M.2 slot is enabled rather than turned off.
- Confirm the storage controller is set to the correct mode for NVMe.
- Update the BIOS to the latest version; manufacturers frequently fix drive-detection bugs in firmware updates.
- If a setting has been corrupted, clear the CMOS to reset everything to defaults, then re-check.
Make one change at a time and reboot between each, so you know which step actually fixed the problem.
Suspect a failing or overheating drive last
Only after the above should you consider the drive itself. NVMe modules run hot, and Nigeria's ambient heat does not help; an overheating or dying drive can drop out of the BIOS intermittently. To test the drive rather than the board:
- Move the NVMe to a different M.2 slot on the same board, if one is free.
- Better still, fit it into another PC and see whether it is detected there.
- If it fails everywhere, the drive is likely on its way out.
For the wider warning signs, our guide on how to tell a hard drive is failing is worth a read before you write the drive off entirely.
Frequently Asked Questions
Why did my NVMe suddenly disappear after I added a SATA hard drive? Almost certainly lane sharing. The new SATA drive is using a port that disables your M.2 slot. Check the manual, then either move the NVMe or free the conflicting SATA port.
Could heat in Nigeria really stop my drive being detected? Indirectly, yes. Heat cycles loosen a marginally seated card, and a chronically overheating drive can drop out. Reseating fixes the first; better airflow and testing in another machine addresses the second.
Is a missing NVMe always a dead drive? No — it rarely is. Reseating, lane conflicts, wrong-interface slots, and BIOS settings account for the vast majority of cases. A genuinely failed drive is the last thing to suspect, not the first.
The One Thing to Remember
Work in order: reseat first, then check the manual for lane sharing, confirm the slot supports NVMe, sort out the BIOS, and only then suspect the drive. Nine times out of ten the disk is fine — the connection, a conflict, or a setting is the real culprit.
Not sure which slot or drive your build is using, or want a machine assembled so these conflicts never arise? Use our configurator to spec a clean, correctly wired build, or contact our team and we will diagnose the missing drive with you.