Hi! I have two NVMe drives in a btrfs cache pool. Today my Unraid WebUI has stopped responding after I tried accessing it, the last thing I saw in the Main tab was that I can't stop the array as btrfs operation was running, but neither of drives had any significant reads/writes. Now the WebUI and my docker containers are completely inaccessible, but I can SSH into it. However it hangs completely as soon as there's anything related to the cache partition like diagnostics, df -h or even autocompleting /mnt/user/ca.

See if you can get the syslog:

cp /var/log/syslog /boot/syslog.txt

On 6/19/2026 at 9:37 AM, JorgeB said:

See if you can get the syslog:

cp /var/log/syslog /boot/syslog.txt

Yeah, i managed to extract the relevant syslog, it shows some btrfs errors starting to show up towards the end

syslog.2

I don't see any btrfs erros, I do see what looks like a bad NVMe device (which ends up crashing the kernel):

Jun 17 23:05:06 Unraid kernel: nvme nvme1: invalid id 220 completed on queue 17

Jun 17 23:05:06 Unraid kernel: nvme1n1: I/O Cmd(0x0) @ LBA 18446744073709551615, 0 blocks, I/O Error (sct 0x0 / sc 0x13)

Jun 17 23:05:06 Unraid kernel: nvme nvme1: request 0xee genctr mismatch (got 0x4 expected 0x5)

The controller is returning completion entries that do not belong to the current queue generation, That usually indicates an NVMe controller firmware bug, failing NVMe SSD, PCIe communication corruption, etc

37 minutes ago, JorgeB said:

I don't see any btrfs erros, I do see what looks like a bad NVMe device (which ends up crashing the kernel)

Yeah, you're right. So is there anything I can do besides hard reset? What is the best way to move forward?

Type reboot in the CLI, but if it doesn't reboot after 5 minutes you may need to force it.