JorgeB

Apr 25 04:47:34 PLEX-PROD kernel: BTRFS: error (device nvme0n1p1: state A) in __btrfs_free_extent:3072: errno=-2 No such entry Apr 25 04:47:34 PLEX-PROD kernel: BTRFS info (device nvme0n1p1: state EA): forced readonly Cache pool went read only, with btrfs recommend backing up and reformatting the pool.

Run it again without -n, and if it asks for -L use it.

If it's a RAM problem, all data can be affected, but since you don't have any other btrfs or zfs filesystems, only the docker image is detecting data corruption.

Start by running memtest, that could be a RAM problem.

Cache pool is not mounting, see if this helps, type: btrfs rescue zero-log /dev/nvme1n1p1 then re-start the array

Jellyfin container was killed twice because it was using a lot of RAM, and making the server run OOM, check its config or limit its RAM usage.

I would, at least for now, just keep monitoring for the next scheduled checks, but if more errors appear it it should be investigated.

Make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Apr 25 14:26:12 sosie kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff Apr 25 14:26:12 sosie kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Apr 25 14:26:12 sosie kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug Try adding that to the syslinux options, at the end of the append line:

Certainly not normal, if you have the diags from the rebuilds post them.

Make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

NIC is not being detected by Linux, this is not a software issue, try a different PCI slot, or the NIC in another PC to make sure it's working.

If the scrub is aborting best bet is to copy what you can from the pool and then reformat, and I do recommend zfs over btrfs for mirrors, since it's better at recovering from a dropped device.

If the docker containers are using /mnt/user you can use the in the array for now.

RAM usage growing so quickly won't be fixed by swap, you need to find out what's causing it, boot with all services disable then start enabling one by one, including starting containers also one by one.