Asrock M.2 Second Slot Not Showing Up | Quick Fix Steps

Asrock M.2 Second Slot Not Showing Up Fixes And Checks

The phrase Asrock M.2 Second Slot Not Showing Up describes a cluster of issues rather than one single fault. On many Asrock boards the second M.2 connector sits on different lanes than the first slot, may only accept SATA based M.2 drives, or shares bandwidth with specific SATA ports. A detail in the manual can decide whether your second solid state drive appears in the firmware screen and inside the operating system.

Before you assume that the second M.2 position is dead, treat the problem like a short checklist. You want to confirm that the drive itself works, that the slot supports the exact type of module you installed, that no shared SATA port or PCIe slot disables it, and that the firmware has the right settings for that connector. Once those parts line up, most systems detect the extra storage without drama.

Check The Basics On Your Asrock Board

Start with the simple items around the hardware. Small placement mistakes can leave even a brand new solid state module invisible, so a careful pass here saves time later on deeper steps.

• Reseat the drive fully — Remove the M.2 module, inspect the gold contacts, then slide it back into the second slot at a shallow angle until you feel a firm click before tightening the screw.
• Move the drive to the first slot — Put the same M.2 module into the primary slot that already works; if the system sees it there, the drive itself is fine and the focus shifts to the second connector.
• Test another known good drive — Use a spare M.2 drive, even a small one, in the second slot to see whether any device at all is detected in that position.
• Look for visible damage — Check the second connector for bent pins, missing plastic, or debris; a bit of dust or a misaligned standoff can block good contact.

If the same drive shows up in the main slot but still leaves the second slot blank in the firmware screen, you have already proven that storage and cable pieces are fine. That narrows the cause to slot design rules, lane sharing limits, or firmware options.

Confirm Slot Type, Lane Sharing, And Drive Support

Many owners find that the second M.2 position stays empty simply because the drive type does not match the connector. A large pool of Asrock boards pairs one PCIe based Ultra M.2 slot with a second SATA only M.2 slot. In that layout, a PCIe NVMe drive in the SATA based slot will never appear, while a SATA M.2 drive works without trouble on that connector.

Another frequent quirk involves shared lanes with regular SATA connectors. Several support pages and community threads explain that the second M.2 position often shares bandwidth with a single numbered SATA port. When that SATA port holds a 2.5 inch drive, the second M.2 slot turns off; remove the cable or shift the drive to a different SATA header and the M.2 device wakes up again.

Symptom	Likely Cause	Quick Check
Drive works in M.2_1 but not M.2_2	M.2_2 is SATA only on that board	Install a SATA M.2 drive or use a PCIe adapter
Second slot and one SATA port never work together	Lane sharing between M.2_2 and a SATA connector	Unplug that SATA port or move the 2.5 inch drive
No M.2 drive shows in either slot until firmware update	Old BIOS with weak M.2 or NVMe support	Update firmware from the Asrock support page

If you are not sure whether a module is NVMe or SATA, check the label and part number. Most vendors print terms such as NVMe, PCIe, or SATA clearly on the sticker, and online spec sheets confirm the interface in seconds. Keying also helps: an M key only module points toward NVMe on most recent drives, while some older SATA modules carry a B and M key notch pattern. That check removes guesswork early.

Pull out the paper manual or download the PDF from the product page for your exact model and revision. Check the storage section where Asrock lists M.2 socket names such as M2_1 and M2_2, then read the notes under the table. Lines that mention PCIe only, SATA only, or lane sharing with SATA3_3 or SATA3_4 describe limits that control whether the second socket can show an NVMe module at all.

Bios Settings That Control The Second M.2 Slot

When the manual confirms that the second slot should support your drive type, shift attention to firmware setup. Recent beta and stable firmware versions for several Asrock B450 boards add an option named something like Force M2_2 To Support PCIe Type Device. Without this switch enabled, the second connector may sit in SATA mode and ignore PCIe NVMe modules.

• Update to a recent firmware build — Visit the support page for your exact board, download the newest stable or recommended beta version, then flash it through the Instant Flash tool inside the existing firmware.
• Load default settings once — After an update, choose the option to load default values so that old experiments do not hide newer storage options.
• Enable the M.2_2 PCIe support option — Inside the advanced storage or chipset menu, turn on any entry that states that M2_2 or the second M.2 slot should support PCIe type devices, then reboot.
• Check CSM and boot mode — Some boards show NVMe drives only when the firmware runs in full UEFI mode with Compatibility Support Module turned off or at least set to UEFI first for storage.

Older firmware builds for the same board family often show missing or incomplete wording for these options. Community threads covering Asrock B450 Pro4, B450M Pro4 F, and B450 Steel Legend describe how the second slot starts reporting PCIe NVMe drives only after an update that adds the force PCIe toggle. In short, if your menu lacks anything that mentions M2_2 and PCIe, a newer firmware build is worth a try. In many builds that simple step works.

Initialize The Second M.2 Drive Inside The Operating System

Once firmware and slot rules are in order, the new drive may still stay invisible inside the file browser because it has no partition table yet. At that stage the second M.2 shows up in firmware screens and storage tools, but the desktop has nowhere to mount it. A short session with a disk utility finishes the setup.

• Open the system disk tool — On Windows, press the Windows key and R, type diskmgmt.msc, then confirm to open Disk Management; on Linux, use tools such as lsblk and graphical partition managers.
• Find the uninitialized drive — Look for a disk that matches the size of the new M.2 module, marked as not initialized or with unallocated space.
• Create a partition table and volume — In the context menu, choose to create a GPT or MBR table, then create a new simple volume that fills the drive and assign a drive letter.
• Confirm that the drive mounts — After the format completes, open the file manager and copy a small test folder to confirm steady writes.

On Windows in particular, many reports of an Asrock M.2 Second Slot Not Showing Up inside the file browser come down to this missing initialization step. The module is active at the hardware level and inside the firmware, yet the operating system ignores it until you prepare it inside the disk tool.

Check Cpu, Pcie Slots, And Shared Lanes

Some layouts tie the second M.2 connector to lanes that also feed extra PCIe slots. On certain boards, once a second graphics card or a high bandwidth capture card uses those lanes, the remaining link lacks the width to drive a second NVMe module at full speed or at all. A few owners report that the second slot only starts working again once they remove a large expansion card or move it to a different slot.

• Review the block diagram in the manual — Check how many lanes come from the processor and chipset, and which slots share paths with the M.2 connectors.
• Test with extra cards removed — Shut the system down, pull non essential PCIe cards, then boot with only the graphics card and both M.2 drives installed.
• Watch for bandwidth limits — If the board notes that a certain PCIe slot drops from x16 to x8 or disables M2_2 when another slot is in use, choose the layout that keeps both storage devices alive.

Asrock support material for boards such as the B450M Steel Legend shows that one M.2 socket may run at PCIe Gen3 x4 while the second runs at SATA mode only. When extra cards claim lanes on top of that split, the second connector has even less headroom. A leaner expansion card layout gives the second M.2 slot the lanes it needs.

When The Asrock M.2 Second Slot Might Be Faulty

After you follow through the checks above, the second slot may still stay empty. At that point you have confirmed that the drive works in another connector or system, that the firmware is up to date, that the slot type matches the module, that no SATA or PCIe sharing rule disables it, and that the operating system already knows how to mount it. The remaining path points toward a hardware level fault.

• Test the drive in another machine — Move the M.2 module to a friend’s system or a spare machine; if it behaves normally there, the fault leans toward the board.
• Check the board for past mishandling — Review whether the system faced shipping knocks, liquid exposure, or repeated drive swaps that may have stressed the connector.
• Use a PCIe adapter as a workaround — A simple x4 M.2 adapter card in an open PCIe slot often delivers full speed and sidesteps quirks around the second onboard socket.
• Contact Asrock or retailer support — If the board is still under warranty and every other path is exhausted, log the steps you have taken and request a repair or replacement.

For a fair share of owners, the situation never reaches that stage because firmware updates, SATA port changes, or the PCIe force toggle resolve the loss of detection. When a stubborn case around the Asrock second M.2 slot survives all of those changes, it is reasonable to treat the connector like any other faulty port and plan for either a repair or an alternate storage layout.