Benemortasia666

@cj_obob I had the same happening sometimes, which was caused by a faulty power-box/power-supply

I am having these issues also. I've been researching it a lot the last couple of days. Still testing out things, but I think it has to do with a Kernel issue since 6.1.46 (commit 8ee39ec): rtsx_pci from drivers/misc/cardreader breaks NVME power state, preventing system boot https://lore.kernel.org/regressions/995632624f0e4d26b73fb934a8eeaebc%40realtek.com/ It first looks like its regarding a realtek card reader but if you read further it turns out to cause this nvme issue. https://lore.kernel.org/regressions/[email protected]/ https://bbs.archlinux.org/viewtopic.php?id=288095 https://lore.kernel.org/all/[email protected]/ And i've been using unraid 6.12.14 where i got the issues, which has kernel 6.1.118, which i think is affected. But I've tried with Unraid 7 with kernel 6.6.68, but that didnt instantly change the situation so i have further testing to do. I got the issue using a Samsung 990 Pro 1Tb. Jan 14 04:37:36 BENEMORTASIA kernel: nvme nvme0: I/O 13 QID 0 timeout, disable controller Jan 14 04:37:36 BENEMORTASIA kernel: nvme nvme0: Device shutdown incomplete; abort shutdown Jan 14 04:37:36 BENEMORTASIA kernel: nvme nvme0: Removing after probe failure status: -4 EDIT: If my theory is correct, then the issues should have started for people with unraid 6.12.4 and higher. So i am going to try a couple of things and see if using unraid 6.12.3 fixes it. EDIT2: In my case it eventually turned out to be a faulty power box. I had to swap the power plug from the power supply to a different slot of my power box, and that fixed the issue. It first showed one drive but after a reboot or 3, everything came back working again and my syslog is cleared of all issues.

I solved it, but because the solution was very odd and not easily found on the forum, I am sharing it. To be clear, I tried everything suggested. 3 Usb sticks, different versions, reset bios, etc etc etc. Until I tried it on an entire different machine, and it worked. What eventually created the bzfirmware checksum error (which I ran into after an update) was my memory... I am using 4x DDR4 8gb memory, and had to pull out 2 to fix the issue... So maybe if memory is rotten in some way and bzfirmware gets checked, it will also give that warning. Anyways, you can close the ticket I got no further questions.

This app worked great for my scenario. -I have a Asus ROG Maximus XI Hero (wifi) with 2 NVMe M2 slots. -One is my Array's Cache device, but i want the other passed-trough to a vm -When I stub it manual on unraid flash with "vfio-pci.ids=xxxx" i lose both. -If i use the plugin, it stubs it on device address (which are unique for the 2 slots) -Now i use that 2nd NVM-e to baremetal boot my windows PC or boot Unraid an use it on My VM Windows PC Perfect for me because im having troubles finding a way to do it manual and now its just one ciick! Thank you

The above replies contained 2 solutions for 2 problems i had figuring out/playing with unraid. -The /disk/by-id/ solution -The info on the NVMe's Note: Even with 2 NVMe's on your desktop motherboard in the same IOMMU group (shown seperate) but with the same ID you use for blacklisting. I still got one 100% passedthrough and shown as the real device in taskmanager, while the other NVMe is used as cache in my Array. I use a 1Tb and 2Tb Samsung 970 Evo Plus on a ROG MAXIMUS XI HERO (WI-FI), Version Rev 1.xx It is all possible, only thing NOT possible is for example on my motherboard. To split up the 6 SATA ports on the mobo so you can passthrough 1 port so the TaskManager on the VM will see the real Device Name. That only works with NVMe('s), for example my mobo. But if you follow the disk/by-id/ata- solutions given, it will be detected on a new VM without loading drivers to see the disk. The performance is good (SET it in unraid Menu at SATA device), but it will be seen as QEMU HARDDISK. The NVM's will say the real name like on a BareMetal situation.