BTRFS warning on new nvme cache drive

[SluggishWorm]

magnus-diagnostics-20210611-1620.zip

Log files attached. Having some weird non issues since adding 10g networking (speeds a lot faster than they should be for shares set to not use cache). Started mover, and my ui locked up for approx 2 minutes. Warning notification showing cache pool missing device. NVME cache drive is installed on my motherboards single nvme slot. It has all come back online, but is there anything that could be the cause? when googling the errors in the syslog.txt file nothing really comes up

[JorgeB]

NVMe device dropped offline:

 

Jun 11 16:14:11 Magnus kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xd9b94000 flags=0x0050]
Jun 11 16:14:41 Magnus kernel: nvme nvme0: I/O 374 QID 1 timeout, aborting
Jun 11 16:14:42 Magnus kernel: nvme nvme0: I/O 786 QID 3 timeout, aborting
Jun 11 16:14:42 Magnus kernel: nvme nvme0: I/O 209 QID 4 timeout, aborting
Jun 11 16:14:42 Magnus kernel: nvme nvme0: I/O 210 QID 4 timeout, aborting
Jun 11 16:15:12 Magnus kernel: nvme nvme0: I/O 374 QID 1 timeout, reset controller
Jun 11 16:15:12 Magnus kernel: nvme nvme0: I/O 2 QID 0 timeout, reset controller
Jun 11 16:16:21 Magnus kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
Jun 11 16:16:21 Magnus kernel: nvme nvme0: Abort status: 0x371

 

Look for a BIOS update, or try a different NVMe device/board, initial error is similar to the typical SATA controller problem with some Ryzen boards.

[SluggishWorm]

1 minute ago, JorgeB said:

NVMe device dropped offline:

 

Jun 11 16:14:11 Magnus kernel: nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0xd9b94000 flags=0x0050]
Jun 11 16:14:41 Magnus kernel: nvme nvme0: I/O 374 QID 1 timeout, aborting
Jun 11 16:14:42 Magnus kernel: nvme nvme0: I/O 786 QID 3 timeout, aborting
Jun 11 16:14:42 Magnus kernel: nvme nvme0: I/O 209 QID 4 timeout, aborting
Jun 11 16:14:42 Magnus kernel: nvme nvme0: I/O 210 QID 4 timeout, aborting
Jun 11 16:15:12 Magnus kernel: nvme nvme0: I/O 374 QID 1 timeout, reset controller
Jun 11 16:15:12 Magnus kernel: nvme nvme0: I/O 2 QID 0 timeout, reset controller
Jun 11 16:16:21 Magnus kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
Jun 11 16:16:21 Magnus kernel: nvme nvme0: Abort status: 0x371

 

Look for a BIOS update, or try a different NVMe device/board, initial error is similar to the typical SATA controller problem with some Ryzen boards.

I know there is definitely one available, im running f10 and f33e is the latest available. Didnt bother upgrading as i saw nothing of importance for my setup but ill give it a shot

[SluggishWorm]

So, this issue quickly escalated overnight. Any time a docker or i tried to access data on that cache drive, it would disconnect and recconect. Webui became completely non reponsive. Took server down and did a bios update, and its been running fine now for 12 hours with no disconnects. Id call  this solved