JorgeB

Yes, that should do it.

I'm not familiar with Dell controllers but I think that's also a RAID controller, and looks like an old model, so likely limited to 2TiB.

The complete diagnostics.zip

Delete this file, you just then have to re-stub any needed hardware. About domain, you meant you can't deleted from the flash?

Could be a RAM issue, without ECC RAM you can get a bit flipped anytime, and one in the wrong place can really corrupt a btrfs filesystem.

It's this issue: Some workarounds discussed there, mostly disable NFS if not needed or you can change everything to SMB.

Yes. Probably best, since you're running single device pool and if you don't need any of the btrfs features, though in my experience most btrfs issues are caused by hardware, still xfs is usually more tolerant if there are any issues.

Yes, should be the same.

It should be possible to flash it to IT mode, and if not it should still work in RAID mode, but IT would be better.

Cache filesystem is corrupt, best bet is to backup and re-format, there some recovery options here if needed.

The boot issue with rc2 is likely unrelated to that.

Try connecting the UPS to a different USB port/controller.

Looks like some lost writes, probably due to known firmware issues with some WD drives, to use them reliably with btrfs you should disable write cache.

Please post the diagnostics.

9240-8i is a megaRAID controller, but it can be flashed to 9211 IT mode.

Intel chipset works fine, I have an X11SPL-F with the same, SAS is LSI 3008, so it's also fine, but ideally in IT mode.

No idea but like mentioned at the top (underlined) you now shouldn't need to change the bus, just add discard=unmap.

Not for now, likely it will be possible in the future.

Nov 4 18:19:24 FrostyUnraid kernel: ata2.00: failed to set xfermode (err_mask=0x1) Nov 4 18:19:29 FrostyUnraid kernel: ata2: hard resetting link Nov 4 18:19:30 FrostyUnraid kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 4 18:19:30 FrostyUnraid kernel: ata2.00: failed to set xfermode (err_mask=0x1) Nov 4 18:19:30 FrostyUnraid kernel: ata2.00: limiting speed to UDMA/100:PIO3 Nov 4 18:19:35 FrostyUnraid kernel: ata2: hard resetting link Nov 4 18:19:35 FrostyUnraid kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 4 18:19:35 FrostyUnraid kernel: ata2.00: failed to set xfermode (err_mask=0x1) Nov 4 18:19:35 FrostyUnraid kernel: ata2.00: disabled Cache device dropped offline, replace cables and try again.

It's been a known issue with that plugin that affects some users.

This is usually a hardware problem, e.g., bad RAM.

this

Xfs_repair looks successful, was the array started in normal mode after the repair? If yes and it didn't mount please post diags.

Not unless you use the --ignore-times flag, then it will only compare sizes, by default rsync doesn't compare contents.

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/