JorgeB

Enable the syslog server and post that if it happens again.

If xfs_repair - v asks for -L use it.

Backup current /config folder and recreate the flash drive using the USB tool (with v6.11.1), if OK restore the config folder, if it also fails replace the flash drive.

Stop the array, unassign cache2, start array, stop array, re-assign cache2, start array, post new diags.

In this thread please:
 
 

Not familiar with those shelfs but post the diags to see if the HBA is being correctly detected, also make sure for now you only connect one cable from the HBA to the 1st module on the shelf.

Install the tips and tweaks plugin and set vm.dirty_background_ratio to 1 and vm.dirty_ratio to 2, that's been known to help for servers with a lot of RAM.

It's not a limitation, it's a bug , it's already been fixed and v6.11.4 should be available soon.

It's a known problem with v6.11.2, upgrade to v6.11.3 and try again.

If the current issue is limited to the log tree like that log snipped appears to indicate it might be solved by zeroing it, but first, and if backups are not up to date, recommend first using option #1  here to backup anything important, then try:
 
btrfs rescue zero-log /dev/nvme0n1p1  
If it works and since btrfs was detecting some corruption
you should run a scrub after mount.

Set appdata to cache=prefer, disable docker service, run the mover.

Are these shucked drives? If yes they might have the 3.3v issue, you can test by connecting one of them using a molex to sata adapter. 

Known issue with v6.11.2, update to v6.11.3

Still in maintenance mode type:
xfs_repair -vL /dev/md7 and post output

Yes, that should help since the logged call traced appeared to be related to macvlan.

Without rebooting since the last diags but with the array stopped type:
wipefs -a /dev/nvme1n1p1 Then start array and post new diags.

https://www.ghacks.net/2022/05/13/how-to-bypass-the-microsoft-account-requirement-during-windows-setup/
 
https://forums.unraid.net/topic/129806-windows-11-vm-unable-to-boot/?do=findComment&comment=1182249
 

As long as the LSI is in IT mode it's plug and play.

Using user shares it will only show the 1st copy of any duplicate files.

First lets try and fix the pool, looks like one the NVMe devices dropped offline in the past and it was never synced, stop the array, type:
wipefs -a /dev/nvme0n1p1 then unassign both pool devices
start array
stop array
reassign only the Sabrent NVMe
start array
post new diags.

You can then hide again if you want, or just edit.
 

Looks more like a power/connection problem but since the disk dropped offline there's no SMART, check/replace cables and see if it comes back online, then post new diags.

If there's data you can rebuild the disk again after updating to v6.11.3 and you won't lose any data, if there isn't you can just format the disk since it's much faster.

SMART looks OK and since the emulated disk is mounting and assuming contents look correct you can rebuild on top.

Delete and recreate the docker image, that does not require you to start over.