Dwight

Did that previously. Seemed to be tied to the slot the NVME drives were inserted in. I am loath to swap them around, since the one that is visible now has pool data on it. Might plug it into my other workstation where both drives are visible and clone the one with data over to the other one. I thought it was similar to this problem, because from the syslog.txt, it is throwing the missing or invalid SUBNQN field error. Feb 2 13:30:25 RimviewServer kernel: nvme nvme0: pci function 0000:0a:00.0 Feb 2 13:30:25 RimviewServer kernel: scsi host1: ahci Feb 2 13:30:25 RimviewServer kernel: scsi host2: ahci Feb 2 13:30:25 RimviewServer kernel: nvme nvme0: missing or invalid SUBNQN field. Feb 2 13:30:25 RimviewServer kernel: nvme nvme0: Shutdown timeout set to 8 seconds

I have this same problem with two SAMSUNG 970 EVO Plus SSD 2TB NVME drives that are installed on a Dual NVMe PCIe Adapter, RIITOP M.2 NVMe SSD to PCI-e 3.1 x8/x16 Card installed in an HP Proliant MicroServer Gen10+ server running Unraid 6.12.6. Both nvme devices are detected by the BIOS, and both are listed in the list of devices that could be booted from. Note that I see the same issue when I boot a more or less standard Linux (Linux Mint 21.3) from the USB and also when I boot up a fairly recent version of PartedMagic. But, when I put the card and drives into an older HP Z210 workstation, both drives are visible under both Windows 10 and an older version of Linux Mint. I guess that I am surprised that Samsung drives would see this issue. rimviewserver-diagnostics-20240202-1340.zip