Problems After Integrating NVMe with Seeed R2000

[Oshadha_Marasinghe]

Hi everyone,

After adding an NVMe to my Seeed R2000, I started running into an issue. The Hailo device failed to initialize.

Initially, I tried running the following command to identify the Hailo device.

eli@raspberrypi:~ $ hailortcli fw-control identify
eli@raspberrypi:~ $

But it returned nothing. After checking the dmesg logs, I found this error in the screenshot related to the Hailo device.

After encountering this problem, I ran sudo apt update && sudo apt full-upgrade, which resolved the issue with the Hailo device. However, now the NVMe no longer shows up with the lsblk command.

eli@raspberrypi:~ $ lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
mmcblk0     179:0    0 58.3G  0 disk 
├─mmcblk0p1 179:1    0  512M  0 part /boot/firmware
└─mmcblk0p2 179:2    0 57.8G  0 part /
eli@raspberrypi:~ $

Has anyone faced a similar issue after adding an NVMe ? Any suggestions on how to resolve this?

Thanks in advance for your help!

[ahsrabrifat]

It looks like you ran into a device conflict issue after adding the NVMe SSD to your Seeed R2000, which caused the Hailo accelerator to fail with:

hailo 0000:06:00.0: Failed to enable MSI -28
hailo 0000:06:00.0: Failed enabling interrupts -28

The -28 error typically maps to ENOSPC (No space left on device), which often means that system resources like interrupt lines or MSI (Message Signalled Interrupts) are exhausted or misconfigured—likely due to the addition of the NVMe device.

Then, after you did a full upgrade, the Hailo device started working—but now the NVMe is not detected by lsblk.

[PJ_Glasso]

Hi there,

Just remove the Hailo device , and go again, Adding it LAST!
Have a look at the WIKI also, for more information.
Do follow the steps and only use images from there.

HTH
GL PJ