Maor Posted December 1, 2023 Share Posted December 1, 2023 I have a brand new KC3000 SSD. Unraid detects the PCIe device 02:00.0, but does not recognise it as a NVMe drive. # lspci 00:00.0 Host bridge: Intel Corporation Device 4617 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [UHD Graphics] 00:0d.0 USB controller: Intel Corporation Device 464e 00:14.0 USB controller: Intel Corporation Device 54ed 00:14.2 RAM memory: Intel Corporation Device 54ef 00:15.0 Serial bus controller: Intel Corporation Device 54e8 00:15.1 Serial bus controller: Intel Corporation Device 54e9 00:16.0 Communication controller: Intel Corporation Device 54e0 00:1c.0 PCI bridge: Intel Corporation Device 54b8 00:1c.1 PCI bridge: Intel Corporation Device 54b9 00:1c.6 PCI bridge: Intel Corporation Device 54be 00:1d.0 PCI bridge: Intel Corporation Device 54b0 00:1d.1 PCI bridge: Intel Corporation Device 54b1 00:1d.2 PCI bridge: Intel Corporation Device 54b2 00:1e.0 Communication controller: Intel Corporation Device 54a8 00:1e.3 Serial bus controller: Intel Corporation Device 54ab 00:1f.0 ISA bridge: Intel Corporation Device 5481 00:1f.4 SMBus: Intel Corporation Device 54a3 00:1f.5 Serial bus controller: Intel Corporation Device 54a4 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01) 02:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. KC3000/FURY Renegade NVMe SSD E18 (rev 01) 03:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) 06:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) I am unable to add the drive into array nor pool: Any idea how to make the KC3000 SSD available to unraid? diagnostics-20231201-2042.zip Quote Link to comment
Maor Posted December 2, 2023 Author Share Posted December 2, 2023 (edited) I have found this in dmesg nvme nvme1: Removing after probe failure status: -12 I suspect it can be caused by ASPM or IOMMU settings in bios. Edited December 4, 2023 by Maor Quote Link to comment
JorgeB Posted December 2, 2023 Share Posted December 2, 2023 It's possible, it's failing to initialize but it's not logged why. Quote Link to comment
Maor Posted December 4, 2023 Author Share Posted December 4, 2023 I have gone through all the settings in BIOS. The SSD works when ASPM option is disabled in BIOS. Quote Link to comment
Recommended Posts
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.