February 1, 20233 yr Amongst numerous issues even getting windows installed, passing through my 3070 (get to that later), I passed through a nvme drive to use as my boot drive/C drive for my windows 11 VM because I thought that might be better than a Vdisk like I've used in the past and after a failed VM (internal error: Unknown PCI header type '127' for device '0000:02:00.0') launch, it disappeared from both the (new) VM template and apparently system devices. I am no expert, but I have never had this much trouble with Unraid. I have recently started a new build with a Xeon and X99, maybe that's been the issue. Anyway I'll attach the vfio log and my diagnostics. I would really like this disk back then I can tackle all the other issues I've had with my still uncreated VM. Thanks. text error warn system array login Loading config from /boot/config/vfio-pci.cfg BIND=0000:00:1b.0|8086:8d20 0000:02:00.0|1987:5016 0000:03:00.0|1106:3483 0000:05:00.0|10de:2484 0000:05:00.1|10de:228b 0000:08:00.0|8086:08b3 0000:09:00.0|1b21:1242 --- Processing 0000:00:1b.0 8086:8d20 Vendor:Device 8086:8d20 found at 0000:00:1b.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:00:1b.0/iommu_group/devices/0000:00:1b.0 Binding... Successfully bound the device 8086:8d20 at 0000:00:1b.0 to vfio-pci --- Processing 0000:02:00.0 1987:5016 Error: Device 0000:02:00.0 does not exist, unable to bind device --- Processing 0000:03:00.0 1106:3483 Vendor:Device 1106:3483 found at 0000:03:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:03:00.0/iommu_group/devices/0000:03:00.0 Binding... Unbound 0000:03:00.0 from xhci_hcd Successfully bound the device 1106:3483 at 0000:03:00.0 to vfio-pci --- Processing 0000:05:00.0 10de:2484 Vendor:Device 10de:2484 found at 0000:05:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:05:00.0/iommu_group/devices/0000:05:00.0 /sys/bus/pci/devices/0000:05:00.0/iommu_group/devices/0000:05:00.1 Binding... Successfully bound the device 10de:2484 at 0000:05:00.0 to vfio-pci --- Processing 0000:05:00.1 10de:228b Vendor:Device 10de:228b found at 0000:05:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:05:00.1/iommu_group/devices/0000:05:00.0 /sys/bus/pci/devices/0000:05:00.1/iommu_group/devices/0000:05:00.1 Binding... 0000:05:00.0 already bound to vfio-pci 0000:05:00.1 already bound to vfio-pci Successfully bound the device 10de:228b at 0000:05:00.1 to vfio-pci --- Processing 0000:08:00.0 8086:08b3 Vendor:Device 8086:08b3 found at 0000:08:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.0 Binding... Successfully bound the device 8086:08b3 at 0000:08:00.0 to vfio-pci --- Processing 0000:09:00.0 1b21:1242 Vendor:Device 1b21:1242 found at 0000:09:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:09:00.0/iommu_group/devices/0000:09:00.0 Binding... Unbound 0000:09:00.0 from xhci_hcd Successfully bound the device 1b21:1242 at 0000:09:00.0 to vfio-pci --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Feb 1 03:40 0000:00:1b.0 -> ../../../../devices/pci0000:00/0000:00:1b.0 lrwxrwxrwx 1 root root 0 Feb 1 03:40 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:02.0/0000:03:00.0 lrwxrwxrwx 1 root root 0 Feb 1 03:40 0000:05:00.0 -> ../../../../devices/pci0000:00/0000:00:03.0/0000:05:00.0 lrwxrwxrwx 1 root root 0 Feb 1 03:40 0000:05:00.1 -> ../../../../devices/pci0000:00/0000:00:03.0/0000:05:00.1 lrwxrwxrwx 1 root root 0 Feb 1 03:40 0000:08:00.0 -> ../../../../devices/pci0000:00/0000:00:1c.3/0000:08:00.0 lrwxrwxrwx 1 root root 0 Feb 1 03:40 0000:09:00.0 -> ../../../../devices/pci0000:00/0000:00:1c.4/0000:09:00.0 drizzt-diagnostics-20230131-2201.zip Edited February 4, 20233 yr by Hardware Dynasty
February 1, 20233 yr Community Expert Only the cache NVMe device is being detected by Linux, this is not a software issue, try re-seating the other one or using a different PCIe slot.
February 4, 20233 yr Author The nvme reappeared after a reset (which I swear I tried already). Might've been a pcie issue.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.