Raspberry Pi 5 NVMe HAT V2 with 2-Pin Power Cable

If this is your first Raspberry Pi 5 NVMe setup, follow this order first. Do not start with EEPROM, boot order, or Gen 3.0 tuning until the SSD is detected at the normal baseline setup.

Prepare a Raspberry Pi OS microSD

A working microSD card gives you a known-good operating system for the first hardware test. Prepare and verify it before assembling the NVMe HAT so you can confirm PCIe and SSD detection before changing the boot drive.

1. Download and install the official Raspberry Pi Imager from https://www.raspberrypi.com/software/

2. Insert a microSD card into your computer. In Raspberry Pi Imager, choose Raspberry Pi 5 as the device, select a current 64-bit Raspberry Pi OS release, and then select the microSD card as the storage target.

3. Open OS Customisation and create a username and password. Set a memorable hostname if you plan to connect without a monitor. You can also configure Wi-Fi, locale, and time zone.

Choose Your First Login Method

Wired Ethernet normally connects automatically. If hostname.local does not resolve, find the Raspberry Pi IP address in your router client list. Do not expose SSH directly to the public Internet.

ssh username@hostname.local

4. Check the selected storage name and capacity one more time. Warning: Raspberry Pi Imager permanently erases the selected storage device.

5. Choose Write and wait for both writing and verification to finish successfully. Safely eject the microSD card, install it in Raspberry Pi 5, and use it for the first boot and NVMe detection test.

First Boot Check

Connect a monitor and keyboard, or connect by SSH if you enabled it in Raspberry Pi Imager. Confirm that Raspberry Pi OS starts normally from the microSD card before enabling PCIe or attempting NVMe boot. If the Pi does not boot from this card, fix the microSD or operating-system setup before troubleshooting the NVMe HAT.

Before Installation

Shut down Raspberry Pi 5 completely and disconnect the power supply. Do not install or remove the HAT while the Raspberry Pi is powered.

Prepare the Raspberry Pi 5, NVMe HAT, 40 mm PCIe FPC cable, M.2 NVMe SSD, standoffs, screws, and optional 2-pin power cable.

Check the SSD label and connector carefully. This board requires an M-Key NVMe SSD. Do not use M.2 SATA SSDs.

Quick Hardware Checklist

Hardware Interface

PCIe FPC connector: connects the Raspberry Pi 5 PCIe port to the NVMe HAT. The cable must be fully inserted and locked on both ends.

M.2 M-Key socket: accepts M-Key NVMe SSDs only. Do not force a SATA, AHCI, B-Key, or non-NVMe module into the socket.

SSD mounting positions: use the correct screw point for 2230, 2242, 2260, or 2280 SSD length. The SSD should sit flat after tightening the screw.

PWR/ACT indicator area: the power/activity LEDs help confirm that the board is powered and that storage activity may be occurring. LED behavior can vary by firmware and system state.

2-pin auxiliary power input: use only when the SSD needs additional current support. Follow the board polarity marking exactly.

FPC Cable Direction

Use the included custom FPC cable. Connect the end marked RPI5 to the Raspberry Pi 5 PCIe connector, and connect the end marked HAT to the NVMe HAT V2 connector. The FPC cable must be fully inserted and locked down on both ends.

Power Input and Current Notes

The Raspberry Pi 5 PCIe/FPC path can power many low-power NVMe SSDs in normal use, but some high-capacity or high-performance SSDs can draw more current during boot, large transfers, or thermal recovery.

If the SSD disappears, fails during file copy, boots slowly, freezes the system, or causes filesystem errors, power stability should be checked along with SSD compatibility.

Power Notes

Use the official Raspberry Pi 5 power supply or another high-quality USB-C power supply that can provide stable current. Avoid weak phone chargers, low-quality USB-C cables, and unpowered USB hubs during setup.

The included 2-pin power cable is only for the board auxiliary 5V input. Use it when the SSD appears unstable, disappears under load, or needs extra current support. It is not a data cable and it is not a replacement for the Raspberry Pi 5 USB-C power input.

2-Pin Power Decision Guide

If you use the 2-pin auxiliary power input, connect it only according to the board polarity marking. Do not guess polarity from wire color alone.

Video Guide

Watch the installation video before powering on the Raspberry Pi 5 if this is your first time installing the NVMe HAT.

Important Physical Checks

The FPC cable must be fully inserted. A loose or reversed cable is one of the most common reasons for NVMe detection failure.

Make sure metal case parts, heatsinks, screws, or the SSD do not touch exposed components in a way that could cause a short circuit.

If the board is installed in a case, test the NVMe HAT outside the case first. After confirming it works, install it into the case and test again.

Driver Requirement

No separate driver is normally required when using a current Raspberry Pi OS release. The NVMe HAT uses the Raspberry Pi 5 PCIe interface. The software setup is mainly enabling PCIe and preparing the NVMe SSD for storage or boot.

Choose Your Setup Goal

Enable PCIe

Edit the Raspberry Pi OS configuration file:

sudo nano /boot/firmware/config.txt

Add this line:

dtparam=pciex1

Save the file and reboot:

sudo reboot

Check Detection

After rebooting, run:

sudo apt install -y pciutils
lspci
lsblk

Use lspci to check whether a PCIe NVMe controller appears. If lspci is not available, install pciutils first. Use lsblk to check whether the NVMe storage device appears as a block device. If lspci shows nothing related to NVMe and lsblk does not show the drive, recheck the FPC cable, SSD type, and PCIe configuration.

What Success Looks Like

A healthy lspci result should contain an NVMe or Non-Volatile memory controller entry. A healthy lsblk result should show an NVMe device name such as nvme0n1. Exact names vary by SSD and OS, but these two checks tell you whether PCIe sees a controller and whether Linux sees a usable block device.

Successful Detection Example

After enabling PCIe and rebooting, the exact output depends on SSD brand, Raspberry Pi OS version, and whether the SSD already has partitions. If you see output similar to this, the NVMe HAT and SSD are being detected.

$ lspci
0000:01:00.0 Non-Volatile memory controller: NVMe SSD Controller

$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mmcblk0     179:0    0  59.5G  0 disk
mmcblk0p1   179:1    0   512M  0 part /boot/firmware
mmcblk0p2   179:2    0    59G  0 part /
nvme0n1     259:0    0 238.5G  0 disk
nvme0n1p1   259:1    0 238.5G  0 part

If lspci shows a Non-Volatile memory controller or NVMe controller and lsblk shows nvme0n1 or a similar nvme device, the HAT, FPC cable, PCIe setting, and SSD are being detected correctly. This does not automatically mean the SSD is formatted, mounted, or bootable yet. If lspci sees an NVMe controller but lsblk does not show a disk, suspect SSD compatibility, SSD power, or SSD firmware behavior.

Expected Command Checks

Use as a Data Drive

Use this path if you want to keep booting Raspberry Pi OS from the microSD card and use the NVMe SSD only for files, projects, Docker data, databases, or downloads.

Data Drive Setup

If the NVMe SSD is new, it may not appear in the file manager until it is partitioned, formatted, and mounted. The steps below create one ext4 Linux storage partition.

Step 1: Find the NVMe Device

lsblk

Look for a device named nvme0n1. If the SSD already has partitions, they may appear as nvme0n1p1, nvme0n1p2, and so on.

Step 2: Create a Partition

sudo fdisk /dev/nvme0n1

Inside fdisk, press n to create a new partition, accept the default start and end values for one full-size partition, then press w to write the change. If the SSD already contains data you need, stop and back it up first.

Step 3: Format as ext4

sudo mkfs.ext4 /dev/nvme0n1p1

Step 4: Mount the Drive

sudo mkdir -p /mnt/nvme
sudo mount /dev/nvme0n1p1 /mnt/nvme
df -h /mnt/nvme

Step 5: Allow User Writes

sudo chown "$USER":"$USER" /mnt/nvme

After this, you can use /mnt/nvme as a normal storage folder. For automatic mounting after reboot, advanced users can check the partition UUID with blkid and add a UUID-based entry to /etc/fstab.

Automatic Mounting with UUID

Use this only for the ext4 data-drive partition created above. Do not add this /mnt/nvme entry when the NVMe is your Raspberry Pi OS boot drive. Use the filesystem UUID instead of a device name such as /dev/nvme0n1p1 because Linux device names can change. The mount directory /mnt/nvme must already exist from Step 4 above.

Step 1: Get the Filesystem UUID

sudo blkid /dev/nvme0n1p1

Copy only the UUID value for the verified NVMe partition. Confirm the device model and capacity with lsblk again if you are not certain which partition belongs to the NVMe SSD.

Step 2: Add the Mount Entry

sudo nano /etc/fstab

Add one line at the end, replacing YOUR-UUID with the exact UUID returned by blkid:

UUID=YOUR-UUID /mnt/nvme ext4 defaults,nofail 0 2

In nano, press Ctrl+O, press Enter to save, and then press Ctrl+X.

Step 3: Verify Before Rebooting

sudo findmnt --verify
sudo mount -a
findmnt /mnt/nvme

Do not reboot until sudo findmnt --verify and sudo mount -a complete without an error. After rebooting, run findmnt /mnt/nvme again to confirm that the SSD mounted automatically.

NVMe Boot Step-by-Step

Choose one setup goal only. If you plan to boot from NVMe, do not partition, format, mount, or add the SSD to /etc/fstab as a data drive first. Raspberry Pi Imager and SD Card Copier both overwrite the selected target.

Before Writing: Prepare EEPROM for NVMe Boot

Complete these steps while Raspberry Pi OS is still running from the known-good microSD card and after lspci and lsblk detect the NVMe. Do not postpone the EEPROM settings until after the first NVMe-only boot.

1. Update Raspberry Pi OS and the packaged EEPROM firmware, then reboot:

sudo apt update
sudo apt full-upgrade -y
sudo rpi-eeprom-update -a
sudo reboot

2. Run sudo raspi-config. Select Advanced Options, then Boot Order, then an option that includes NVMe. Menu wording can vary by Raspberry Pi OS version.

3. Open the persistent EEPROM configuration:

sudo rpi-eeprom-config --edit

Add PCIE_PROBE=1 on its own line without deleting the existing BOOT_ORDER, save, and reboot. INV001 is a non-HAT+ PCIe device, so complete this setting before removing the microSD card.

4. After rebooting from microSD, run lspci and lsblk again. Continue only when the NVMe controller and the correct SSD model and capacity are visible.

Method 1: Write a Fresh OS with Raspberry Pi Imager (Recommended)

1. While Raspberry Pi OS is running from microSD, install and open Raspberry Pi Imager:

sudo apt install -y rpi-imager
rpi-imager

2. Choose a current 64-bit Raspberry Pi OS image, configure the username and login method, and select the verified NVMe SSD as the target. Warning: Imager erases the selected target.

3. After writing completes, run sudo poweroff, wait for activity to stop, disconnect power, and remove the microSD card.

4. Reconnect power and boot from NVMe. After login, run lsblk and confirm / and /boot/firmware are mounted from nvme0n1 partitions.

You may also connect the NVMe SSD to another computer with a USB-to-NVMe adapter and write the same current Raspberry Pi OS image with Raspberry Pi Imager. Prepare the Raspberry Pi EEPROM settings above before the NVMe-only test.

Alternative: Clone the Existing microSD System

Use Raspberry Pi OS SD Card Copier only when you want the NVMe to contain a copy of the already configured microSD system.

1. Confirm that the microSD system includes dtparam=pciex1 in /boot/firmware/config.txt and that lspci and lsblk detect the NVMe.

2. Open SD Card Copier, select the microSD card as the source, and select the verified NVMe SSD as the target.

3. Complete the copy, run sudo poweroff, wait for activity to stop, disconnect power, and remove the microSD card.

4. Boot from NVMe and confirm / and /boot/firmware are mounted from nvme0n1 partitions.

EEPROM and Boot Order

If the SSD is detected but does not boot, confirm that the Raspberry Pi 5 bootloader EEPROM is current, the boot order includes NVMe, and PCIE_PROBE=1 remains present. Do not download or flash random EEPROM files from third-party sites for normal setup.

When to Update EEPROM

Use the official EEPROM update method when the NVMe SSD is detected by hardware checks but will not boot, when your Raspberry Pi 5 bootloader is old, when boot order settings are missing, or when Raspberry Pi OS recommends a bootloader update. Also update EEPROM after you have already checked the FPC cable, SSD type, power supply, and OS configuration.

Raspberry Pi documentation recommends updating Raspberry Pi OS first, selecting the latest bootloader with raspi-config when needed, then using rpi-eeprom-update to schedule the update. This keeps the bootloader aligned with the official Raspberry Pi OS package instead of locking users to an old bundled file.

Useful commands:

sudo apt update
sudo apt full-upgrade
sudo rpi-eeprom-update -a
vcgencmd bootloader_version

To edit EEPROM configuration:

sudo rpi-eeprom-config --edit

For PCIe/NVMe boot, Raspberry Pi documentation commonly uses this boot order:

BOOT_ORDER=0xf416

For a non-HAT+ PCIe device, adding PCIE_PROBE=1 allows the bootloader to enumerate the PCIe x1 interface during boot. HAT+ compliant devices can be auto-detected and may not require this setting.

PCIE_PROBE=1

Set Boot Order

Use sudo raspi-config, choose Advanced Options, then Boot Order, then an option that includes NVMe. Reboot after saving the change.

Update EEPROM Firmware

1. Make sure Raspberry Pi 5 is connected to the Internet.

2. Check the current bootloader version:

vcgencmd bootloader_version

3. Update packages and EEPROM firmware:

sudo apt update
sudo apt full-upgrade -y
sudo rpi-eeprom-update -a

4. Reboot, then run vcgencmd bootloader_version again to confirm the update.

Low-Power Shutdown Setting

If the board LEDs or attached SSD continue to draw more standby power than expected after shutdown, edit the EEPROM configuration and set POWER_OFF_ON_HALT=1.

sudo rpi-eeprom-config -e

POWER_OFF_ON_HALT=1

Optional PCIe Gen 3.0

This board can be used in PCIe Gen 3.0 mode on compatible Raspberry Pi 5 and SSD combinations. Raspberry Pi 5 is not guaranteed to be stable with every device at Gen 3.0 speed, so use Gen 2.0 as the baseline for troubleshooting. To try Gen 3.0, add:

dtparam=pciex1_gen=3

Performance Test

A simple write/read test can be run after setup. Run tests only on a mounted NVMe filesystem where temporary files are safe to create. Delete the test file after benchmarking.

How to Run a Clean Benchmark

1. Confirm the NVMe SSD is visible:

lsblk

2. Change into a directory that is actually stored on the NVMe drive, then confirm your location:

pwd

3. Run a larger sequential write/read test:

dd if=/dev/zero of=./Testingfile bs=100M count=50 oflag=direct status=progress
dd if=./Testingfile of=/dev/zero bs=100M count=50 oflag=dsync status=progress

4. Remove the temporary file after the test:

rm ./Testingfile

Performance depends on SSD model, SSD firmware, SSD temperature, filesystem, power supply, PCIe mode, Raspberry Pi OS version, and system load.

Benchmark Reference

The numbers below are reference ranges for a healthy Raspberry Pi 5 NVMe setup. They are not a fixed product guarantee and should not be used as the only pass/fail test. Some SSDs will be slower, some faster, and unstable Gen 3.0 setups should be returned to Gen 2.0.

Performance Expectations

Troubleshooting Decision Tree

Troubleshooting Checklist

Start with the simple checks first: confirm that Raspberry Pi OS is current, confirm PCIe is enabled, confirm the FPC cable is fully inserted, confirm the SSD is M-Key NVMe, confirm stable power, then check EEPROM and SSD compatibility.

A loose FPC cable or an unlocked connector latch is one of the most common causes of SSD detection failure. Compare your cable position with the image below before changing software settings.

SSD Not Detected

Power off the Raspberry Pi 5. Reseat the FPC cable on both ends, reseat the NVMe SSD, confirm the SSD is installed in the M-Key socket, then boot again. Run lspci and lsblk after reboot.

lspci Shows No NVMe Device

This usually points to PCIe not being enabled, an FPC cable seating/direction issue, a missing SSD, or a PCIe negotiation issue. Recheck /boot/firmware/config.txt, test outside the case, and try another known-good NVMe SSD.

lsblk Does Not Show the Drive

If lspci shows an NVMe controller but lsblk does not show a disk, the SSD may be incompatible, underpowered, failed, or not responding correctly to the Raspberry Pi 5 PCIe link. Try a different SSD and check whether auxiliary 5V power is needed.

SSD Is Detected but Will Not Boot

Confirm the NVMe SSD contains a bootable Raspberry Pi OS image, the OS on the NVMe drive has PCIe enabled, the EEPROM boot order includes NVMe boot, and PCIE_PROBE=1 is present if required by your setup.

System Is Slow or Unstable

Remove dtparam=pciex1_gen=3 and test again at default PCIe Gen 2.0 speed. Also check SSD temperature, power supply quality, 2-pin auxiliary power need, SSD controller compatibility, and whether your speed test is running on the NVMe drive instead of the microSD card.

New SSD Does Not Appear in File Manager

A blank SSD may be detected by lsblk but not shown as a usable drive until it has a partition and filesystem. Use Raspberry Pi OS disk tools or command-line partitioning tools to format the SSD before using it as a data drive.

What to Send Support

When asking for help, include your Amazon order ID, Raspberry Pi OS version, SSD brand/model/capacity, photos of the FPC cable orientation, and the output of uname -a, vcgencmd bootloader_version, lspci, and lsblk.

The iUniker INV001 Raspberry Pi 5 NVMe HAT V2 is a PCIe to M.2 NVMe expansion board for Raspberry Pi 5. It uses the Raspberry Pi 5 PCIe interface to add fast M.2 NVMe storage for boot-drive builds, desktop-style Raspberry Pi setups, home lab projects, and maker applications.

This page is the iUniker NVMe HAT V2 setup guide for Raspberry Pi 5. It covers hardware installation, PCIe enablement, NVMe detection checks, NVMe boot setup, downloads, Q&A, and troubleshooting.

The board supports common M-Key M.2 NVMe SSD sizes: 2230, 2242, 2260, and 2280. This makes it suitable for compact embedded projects as well as full-length 2280 SSD storage upgrades.

The package includes the NVMe HAT, a custom FPC cable for the Raspberry Pi 5 PCIe connector, an extra 2-pin power cable, screws, and mounting hardware. The extra 2-pin cable is included for setups that use the board auxiliary power connection; follow the board markings and do not reverse polarity.

This product is for M-Key NVMe SSDs only. It does not support M.2 SATA SSDs, M.2 PCIe AHCI SSDs, B-Key SSDs, or other non-NVMe M.2 devices.

When to Use This Board

Use this NVMe HAT when you want Raspberry Pi 5 to boot from NVMe, run applications from faster storage, reduce SD card wear, build a compact NAS or home server, or create a more reliable storage setup for development and maker projects.

For a current Raspberry Pi OS setup, no additional Linux driver is required. The most important steps are correct physical installation, enabling PCIe, using a compatible NVMe SSD, and keeping the Raspberry Pi bootloader EEPROM reasonably up to date.

Compatible Host Board

Raspberry Pi 5. This board is not for Raspberry Pi 4, Raspberry Pi 3, Raspberry Pi Zero, or older Raspberry Pi boards because those boards do not expose the same Raspberry Pi 5 PCIe connector.

Supported SSD Type

Use M-Key M.2 NVMe SSDs only. The SSD must be NVMe. M.2 SATA SSDs, M.2 PCIe AHCI SSDs, B-Key SSDs, and other non-NVMe M.2 devices are not supported even if the connector shape looks similar.

Supported SSD Sizes

Supported lengths: 2230, 2242, 2260, and 2280.

Board Dimensions

Approximate board dimensions shown in the product image: 87.2 mm x 56 mm, with a 65 mm top mounting span and 43.3 mm lower section width.

Cooling and Stacking Clearance

The installed assembly image shows approximately 19 mm total stacking height and about 16 mm reserved cooling clearance, depending on the Raspberry Pi 5, cooler, screws, SSD, and final assembly.

Operating System

Use a current 64-bit Raspberry Pi OS release. Older releases may not include the Raspberry Pi 5 PCIe and NVMe boot behavior expected by this guide.

Cooler and Case Notes

The board is designed for Raspberry Pi 5 Active Cooler and many passive or active cooler setups when installed with suitable clearance. Always check the full assembly before powering on. Make sure the FPC cable, SSD, screws, cooler, and case do not press against each other or create a short circuit.

SSD Compatibility Notes

NVMe compatibility depends on the Raspberry Pi 5 firmware, the SSD controller, SSD firmware, power stability, and PCIe speed. If one SSD is not detected or is unstable, test with another known-good NVMe SSD before assuming the HAT is faulty.

Some NVMe SSD controllers are known to behave poorly with Raspberry Pi 5 PCIe Gen 2 or Gen 3. Symptoms can include no detection, slow boot, system lag, filesystem errors, or freezes during large file transfers.

Known SSD Compatibility Risks

Avoid assuming that every M-Key NVMe SSD will work perfectly with Raspberry Pi 5. Raspberry Pi 5 PCIe compatibility depends heavily on the SSD controller and firmware, not only on this adapter board.

Models and controller families that have been widely reported by Raspberry Pi 5 NVMe users as risky include some Phison-controller SSDs, some MAP1202-controller SSDs, WD Blue SN580, WD Blue SN5000, WD Black SN770, WD Black SN850/SN850 series, WD SN740, WD SN810, Kingston NV3, Corsair MP600, Inland TN446, Fanxiang S500 Pro, Micron 2450, and Micron 2200. Compatibility can change after Raspberry Pi EEPROM or SSD firmware updates, so this list should be treated as a practical warning list rather than a permanent pass/fail guarantee.

If your SSD is not detected, first test with a common low-power NVMe SSD from another brand before replacing the HAT. If the replacement SSD works, the original SSD is likely a controller, firmware, or power compatibility issue.

SSD Compatibility Table

Other Incompatibility Notes

M.2 SATA SSDs, M.2 PCIe AHCI SSDs, B-Key SSDs, Wi-Fi cards, cellular cards, and other non-NVMe M.2 devices are not supported. A new blank NVMe SSD may also need to be partitioned and formatted before it appears as usable storage in Raspberry Pi OS.