M.2 NVMe drive not listed in Unraid but visible in bios

[scs3jb]

Any ideas?

 

Its listed fine in the bios, and I can boot from it from there

 

But not seen in unraid:

[0:0:0:0]	disk     USB      SanDisk 3.2Gen1 1.00  /dev/sda   30.7GB
[1:0:0:0]	disk    ATA      ST4000VN000-1H41 SC46  /dev/sdb   4.00TB
[1:0:1:0]	disk    ATA      WDC WD40EFRX-68W 0A80  /dev/sdc   4.00TB
[1:0:2:0]	disk    ATA      WDC WD40EFRX-68W 0A82  /dev/sdd   4.00TB
[1:0:3:0]	disk    ATA      HGST HDN724040AL A5E0  /dev/sde   4.00TB
[1:0:4:0]	disk    ATA      ST8000AS0002-1NA AR15  /dev/sdf   8.00TB
[1:0:5:0]	disk    ATA      ST8000AS0002-1NA AR17  /dev/sdg   8.00TB
[1:0:6:0]	disk    ATA      ST12000VN0007-2G SC60  /dev/sdh   12.0TB
[1:0:7:0]	disk    ATA      ST12000VN0007-2G SC60  /dev/sdi   12.0TB
[N:0:6:1]	disk    SAMSUNG MZQL21T9HCJR-00A07__1              /dev/nvme0n1  1.92TB
[N:1:6:1]	disk    SAMSUNG MZQL21T9HCJR-00A07__1              /dev/nvme1n1  1.92TB
[N:2:6:1]	disk    SAMSUNG MZQL21T9HCJR-00A07__1              /dev/nvme2n1  1.92TB
[N:3:6:1]	disk    SAMSUNG MZQL21T9HCJR-00A07__1              /dev/nvme3n1  1.92TB

I might have overlooked something but not sure what it would be?

legion-nas-diagnostics-20230319-1339.zip

[apandey]

how are the nvme drives connected? your motherboard only has 1 m.2 slot. Are you using any of the OCuLink connections? Or a PCI card?

Have you looked at any shared slots in your motherboard manual, where using another connection might disable a nvme drive? Tried swapping the missing drive with another one?

Edited March 19, 2023 by apandey

[scs3jb]

OcuLink for the U.2 SSD Drives, nvme is via the motherboard (PCH).  In terms of sharing one PCI-E sharing/collision, one OcuLink (PCI-E7 / CPU), the rest are all PCH and don't share... in theory.  I wouldn't expect PCH to collide with anything.

 

The M.2 slot is pci-e 3.0 4x and SLOT4 is empty (only other PCIe lane).  I am using the PCIe5.0 for a SAS controller but that's on CPU.

 

PCIe Expansion Slots (SLOT7 close to CPU)
SLOT7 PCIe4.0 x4* [CPU]
SLOT6 PCIe5.0 x16 [CPU]
SLOT4 PCIe3.0 x1 [PCH]
Note *SLOT7 share lanes with OCuLink4. OCuLink4 will disable when SLOT7 is
populated

Other PCIe Expansion Connectors
M.2 slot 1 M-key (PCIe3.0x4) [PCH]; support 2280/2260/2242/2230
form factor

OCuLink 
1 OCuLink (PCIe4.0 x4)* [CPU]
1 OCuLink (PCIe4.0 x4 or 4 SATA 6Gb/s) [PCH]
1 OCuLink (PCIe4.0 x4) [PCH]
1 OCuLink (PCIe3.0 x4) [PCH]
Note *SLOT7 share lanes with OCuLink4. OCuLink4 will disable when SLOT7 is
populated

 

Thoughts?  You think a SAS controller on a CPU port could class with a m.2 slot on PCH?  I don't think it can be the OcuLinks since bios is showing Oculinks and m.2 in the bios.  I guess i can pull it when the parity rebuild finishes, but it seems a bit odd.

 

Maybe I didn't spot something in hidden in the manual?

https://download.asrock.com/Manual/W680D4U-2L2TG5.pdf

Edited March 19, 2023 by scs3jb

[apandey]

Looks ok to me, sorry, I'm out of ideas. Will defer to someone else here

Edited March 19, 2023 by apandey

[scs3jb]

1 minute ago, apandey said:

Looks ok to me, sorry, I'm out of ideas. Will defer to someone else here

No you are on to something, thank you, reading the block diagram its sharing the pci-e 3x and the m.2 and there's:

Quote

(BOM option with M2_1)

Trying to figure out what BOM option with M2_1 means now!

[apandey]

10 hours ago, scs3jb said:

Trying to figure out what BOM option with M2_1 means now!

Never heard of it myself, and can't find anything meaningful when trying to look for it

 

Good catch, but it does not look like a PCI switch in the block diagram. Would be curious if you could share what you find. Maybe ask manufacturer for clarification - this is new kit, so they must be helpful

[scs3jb]

9 hours ago, apandey said:

Never heard of it myself, and can't find anything meaningful when trying to look for it

 

Good catch, but it does not look like a PCI switch in the block diagram. Would be curious if you could share what you find. Maybe ask manufacturer for clarification - this is new kit, so they must be helpful

 

I've raised a support request with AsRock.

Whilst pulling up the details this feels like it might be on the slackware/unraid side, in the BMC it looks fine (I can see both the PCI-E 4 and m.2 slots in use) whilst unraid can't see the drive... very odd.

[scs3jb]

I have tried the following:

1. Removing the SAS controller - no luck, so there's no sharing, etc going on.

2. Removing and reseating the m.2 drive

3. Adding some sysconfig boot parameters

[apandey]

Have you tried booting with another distro - like Ubuntu live CD maybe? Will give an idea whether this is unraid specific or generally a linux issue

[JorgeB]

The other NVMe device is not being detected by Linux, so doesn't look like an Unraid problem, but agree with the post above, try a different Distro.

[m3digi]

Did anyone find a solution to this issue? I have the same motherboard, and have experienced the same issue. Unraid won't recognize my WD Red SN700. If I put my NVME into an NVME to PCIe x4 adapter, Unraid recognizes the SN700 with no problem. 

 

I've tried changing various BIOS settings to get the M.2 slot to work, but I haven't had any success. 

[m3digi]

After another look in the BIOS, I resolved the issue by going to:

 

Advanced > VMD Configuration > Enable VMD Controller

 

Now my NVMe plugged into the M.2_1 slot is detected by Unraid.

 

Thank you.