Storage troubleshooting · 4 min read

ASRock B550 Phantom Gaming 4: M2_3 or SATA drive missing

Resolve M2_3 sharing with SATA3_5/6 on the non-ac B550 Phantom Gaming 4 and distinguish its Key-E Wi-Fi socket from SSD connectors.

On the non-ac B550 Phantom Gaming 4, M2_3 shares lanes with SATA3_5 and SATA3_6. The manual says using one side disables the other. Its M2_2 connector is for a Wi-Fi/Bluetooth module, not a third SSD socket.

Follow the non-ac model in the shared manual

ASRock's manual covers both B550 Phantom Gaming 4 and B550 Phantom Gaming 4/ac. Their storage layouts differ. This article applies to the model without /ac, which has six SATA ports and the additional M2_3 storage position.

Check the complete name printed on the board before using a diagram. The fact that a manual cover lists both models does not mean every feature described inside belongs to both.

Write down the SSD model and interface, the occupied M.2 labels, and each SATA cable's motherboard port. This gives you a usable storage map before anything is unplugged.

Distinguish the three M.2 labels

For the non-ac board, M2_1 is the CPU-connected PCIe storage socket. M2_3 accepts SATA M.2 storage or PCIe storage up to the documented Gen3 x2 connection. It is this M2_3 position that shares with SATA3_5/6.

M2_2 is the Key-E position for a 2230 Wi-Fi/Bluetooth module. It is not another general-purpose SSD connector. Do not count every M.2 label on the board as an available NVMe storage position or try to force a storage module into a different key.

The module's physical length and interface both matter. An M.2 SATA SSD and an M.2 PCIe SSD can have similar dimensions while requiring different electrical support.

Resolve the M2_3 and SATA3_5/6 conflict

The storage table explicitly states that M2_3 and SATA3_5_6 share lanes and using either makes the other unavailable. If an SSD or SATA drive vanished immediately after another drive was added, check this combination before assuming a failed disk.

For ordinary independent drives, one possible arrangement is to keep the M2_3 SSD and move affected SATA connections to available SATA3_1 through SATA3_4. Label cables first, shut down and unplug mains power before moving them, and preserve each drive's power connection.

If the disks belong to a RAID array or another managed storage configuration, consult its documentation and preserve the original arrangement before making changes. Do not apply a simple cable-moving checklist blindly to an array.

Distinguish reduced speed from disappearance

M2_3's PCIe Gen3 x2 connection is narrower than M2_1's documented PCIe path. A compatible PCIe SSD can therefore run below its advertised maximum in M2_3 without being defective.

That performance limit is different from the socket becoming unavailable through sharing. Test the actual symptom: does firmware list the disk, does it contain an existing boot entry, and does the operating system see it after the shared-port conflict is removed?

Verify the old data rather than recreating it

After changing the layout, inspect firmware storage detection first. Then select the existing operating-system boot entry if necessary and check that expected files remain available.

Do not initialize or format a previously used drive merely because File Explorer does not show it. A blank drive and an existing drive with inaccessible partitions require different handling. If detection still fails with compatible interfaces and no sharing conflict, record the final connector arrangement and test the suspect drive through another known-compatible connection before replacing hardware.

Original sources

Check the exact model, PCB revision and current manufacturer instructions before acting.

Source-linked editorial guide · Reviewed 2026-10-29 · Not hardware-tested

How this guide was prepared · Report a correction