CM3588 NAS Board only detecting one NVME drive

  • I bought several of the CM3588 NAS kits and 4x 2TB NVME drives to populate them. However, when I go to setup software RAID in the GUI, it only shows one of the NVMEs. This is happening on multiple boards and multiple drives. I've even tried swapping drives between boards to confirm that the drives themselves are not bad. While it's possible that I got multiple bad boards, I find that highly unlikely. Is there something I will need to do to get the system to recognize more drives? Even lsblk only shows one drive.


    Thank you!

  • ryecoaaron

    Hat das Thema freigeschaltet.
    • Neu
    • Offizieller Beitrag

    I had one m2 nvme stick and one m2 to five sata adapter board on mine and could see all six drives. Do you see any errors in dmesg?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Here's an excerpt with a few errors, I don't really understand what it's telling me though:


    [ 7.305170] mali fb000000.gpu: Probed as mali0

    [ 7.306343] input: gpio-keys as /devices/platform/gpio-keys/input/input5

    [ 7.307303] RKNPU fdab0000.npu: Adding to iommu group 0

    [ 7.307454] RKNPU fdab0000.npu: RKNPU: rknpu iommu is enabled, using iommu mode

    [ 7.307591] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree

    [ 7.308170] RKNPU fdab0000.npu: Looking up mem-supply from device tree

    [ 7.308668] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff]

    [ 7.308699] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff]

    [ 7.308717] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff]

    [ 7.309067] [drm] Initialized rknpu 0.9.2 20231018 for fdab0000.npu on minor 1

    [ 7.309456] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up nputop-supply from device tree

    [ 7.309484] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up nputop-supply property in node /power-management@fd8d8000/power-controller failed

    [ 7.309566] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu1-supply from device tree

    [ 7.309585] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu1-supply property in node /power-management@fd8d8000/power-controller failed

    [ 7.309651] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu2-supply from device tree

    [ 7.309671] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu2-supply property in node /power-management@fd8d8000/power-controller failed

    [ 7.309890] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree

    [ 7.309908] vdd_npu_s0: could not add device link fdab0000.npu: -EEXIST

    [ 7.309916] vdd_npu_s0: Failed to create debugfs directory

    [ 7.311283] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)

    [ 7.311513] RKNPU fdab0000.npu: RKNPU: bin=0

    [ 7.311706] RKNPU fdab0000.npu: leakage=9

    [ 7.311746] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree

    [ 7.311763] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!

    [ 7.318314] RKNPU fdab0000.npu: pvtm=890

    [ 7.322680] RKNPU fdab0000.npu: pvtm-volt-sel=4

    [ 7.322771] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree

    [ 7.322793] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!

    • Neu
    • Offizieller Beitrag

    Did you see anything in the log I posted?

    Not really. Have you tried two nvme sticks to see if they show up? I didn't get a chance to try anything on my board last night.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Not really. Have you tried two nvme sticks to see if they show up? I didn't get a chance to try anything on my board last night.

    I have tried it and it doesn't work. No combination of drives shows any more than one drive. Interestingly, it can be a different drive on reboot.

    • Neu
    • Offizieller Beitrag

    Are all of your nvme drives identical? I'm curious if two different nvme drives would work. I still haven't had a chance to try yet.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Neu
    • Offizieller Beitrag

    They are all identical. this is what I have. Not yet works higher quality but I’ve used them before without issue. And it’s hard to believe that 6 out of 8 would be bad.

    I wasn't saying any of them are bad. I am wondering if the cm3588 board only "sees" one when they are identical.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I don't have this cm3588 but, is it possible that they are operating in SATA PCIe? I don't want to lead you down the wrong path, so don't put too much time in figuring that out. Post the output of fdisk -l, dmidecode and lspci, maybe there's something in there.


    Looks like a decent board.

    • Neu
    • Offizieller Beitrag

    is it possible that they are operating in SATA PCIe?

    Doubtful. I have no problem with two different mini pcie devices.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Could that 1 header be operating at x4, disabling the other 3 headers? It *might* be that you have the camera enabled, but I can't tell if that consumes those lanes (every board should have a block diagram).


    PCIe:

    • up to 4 x PCIe interfaces
      • 2 x PCIe 2.1 x1 and 2 x PCIe 3.0 x2
      • or 2 x PCIe 2.1 x1 and 1 x PCIe 3.0 x4
      • or 1 x PCIe 2.1 x1, 1 x PCIe 3.0 x2, and 2 x PCIe 3.0 x1
      • or 4 x PCIe 3.0 x1

    CM3588 - FriendlyELEC WiKi

  • I don’t know how to manipulate the lanes. I really think it’s something like that but I can’t get it to work and there’s no bios or anything to configure.


    I’ll try to get the output you asked for.

    • Neu
    • Offizieller Beitrag

    Using the Friendly OMV 7, I wasn't able to reproduce this issue with three nvme sticks (two identical) and the m2-to-sata adapter. I was able to format all three ext4 and pool them with mergerfs. I am powering it with a 90W 19V brick.



    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I can see all the drives via the cli nvme tool, but only one has a namespace (and which one changes on reboot). I very highly suspect it's because all the drives have the same id. I have returned these drives and ordered some Crucial P3 drives...I'll report back once I know if they fix the issue.

    Trying to document my experience here a bit because I've not found any resources on this issue anywhere and want to help others avoid my pain.

    I used dmesg to see the message about nsid.

    • Neu
    • Offizieller Beitrag

    That is strange that you have nvme sticks without a namespace. If you created namespaces, you could set the nsid when you attach it to the controller. https://narasimhan-v.github.io…ging-NVMe-Namespaces.html

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!