JorgeB

Cache filesystem is corrupt, there are some recovery options here.

Just replace or swap with another and see if the problem goes away/follows the cable.

Please use the existing plugin support thread:
 
 

Change the onboard controller from IDE to AHCI/RAID.

Mar 6 12:44:08 Bamboo kernel: BTRFS info (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 510952, gen 0 Mar 6 12:44:08 Bamboo kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 3707, gen 0  
Lots of data corruption being detected on both pools, start by running memtest.

Likely from the syslog server, check settings or disable if not needed, and delete the files.

Diags would be better but screenshot suggests drives were formatted non-encrypted, assuming there's no data there insert the key you want to use, start the array and re-format the drives.
 
 
 

It's not logged as a disk issue, and the disk looks healthy, check/replace cables or swap slots and if the emulated disk is mounting rebuild on top.

See below:
 
 

Looks like the typical onboard controller issue with some Ryzen boards, look for a BIOS updated or use and add-on controller, also note that using USB devices for array or cache is not recommended, and there are also USB disconnects in the log.

-stop array
-unassign the cache device
-start array
-in the console type:
btrfs balance start -f -dconvert=single -mconvert=single /mnt/disk2 -once that finishes type:
btrfs dev del /dev/nvme0n1p1 /mnt/disk2 -once that's done stop the array
-re-assign the cache device
-start array, cache will be unmountable, format to start using it.

That part of of the Fix Common Problems plugin, it's not stock.

Could be this issue:
https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-r1674/?do=getNewComment&d=2&id=1674

See here for some recovery options:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
 

Yes.
 
Yes.

Can't see that in the diags, can see overclocked RAM though.

Disk still appears to be failing, it's not even giving a valid SMART report, good news is that the emulated disk1 is mounting so you just need to replace that disk then assign it to the disk1 slot to rebuild.

Disk4 is OK, it's smaller than the other ones so it slows down sooner, disk3 needs to be replaced.

El controlador Asmedia no se puede inicializar:
 
Mar 4 02:04:44 Tower kernel: ahci 0000:01:00.0: can't change power state from D3hot to D0 (config space inaccessible)  
Aunque el error no es el mismo, puede intentar ver si esto ayuda:
 
https://forums.unraid.net/topic/97628-solved-unraid-on-qnap-ts-453b-mini/?do=findComment&comment=900555
 
 
 
 

That's not the point, point is if any data was written to the emulated disk parity will no longer be valid if we use actual disk instead.
 
In that case and IMHO best way forward would be to do a new config with the new disk2 and the remaining disks and re-sync parity.
 

Mount the old disk with UD then use your favorite tool, you can use krusader, midnight commander (mc on the console), windows explorer, etc.

Disk5 dropped offline so there's no SMART, probably because of the controller, but it does appear to be failing, suggest connecting it to the onboard SATA ports (swap with another disk) and then and since parity isn't valid run ddrescue to try and recover as much data as possible.
 
Pparity looks healthy, though would recommend getting rid of that SASLP controller since they are not recommended for a long time, replace it with an LSI HBA.

Sounds to me like a power/connection problem, if the same devices sometimes work, sometimes don't, problem is probably on the power side.

NVMe device dropped offline:
 
Dec 23 22:48:36 Zigplex2 kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 Dec 23 22:48:36 Zigplex2 kernel: nvme 0000:08:00.0: enabling device (0000 -> 0002) Dec 23 22:48:36 Zigplex2 kernel: nvme nvme0: Removing after probe failure status: -19  
Look for a BIOS update, the below also helps sometimes, failing that try a different brand/model device or board.
 
Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append initrd=/bzroot"
nvme_core.default_ps_max_latency_us=0 e.g.:
append initrd=/bzroot nvme_core.default_ps_max_latency_us=0
Reboot and see if it makes a difference.

Feb 25 18:21:38 SwagServer kernel: BTRFS info (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 67623, gen 0 Feb 25 18:21:38 SwagServer kernel: BTRFS info (device sdd1): bdev /dev/sdc1 errs: wr 3341754, rd 454753, flush 228253, corrupt 0, gen 0 Feb 25 18:21:38 SwagServer kernel: BTRFS info (device sdd1): bdev /dev/sdb1 errs: wr 284514652, rd 245960197, flush 2035012, corrupt 37140664, gen 57  
All pool devices show errors, read/write errors suggest two of them dropped offline in the past, suggest you backup and re-format the pool, then check here for better pool monitoring.