JorgeB

Not that I know of.

Note that you'll need to change the xfs UUID to be able to mount both disks at the same time, you can do that for the disk outside the array with: xfs_admin -U generate /dev/sdX1

Transid error with btrfs is usually fatal, and it's usually caused by writes not being completely flushed to disk, there are some recovery options here, btrfs restore is likely the best one for this. There are constant ATA errors with disk3, and possibly the reason for the fs becoming corrupt: May 10 22:48:22 MitchFlix kernel: ata6.00: status: { DRDY } May 10 22:48:22 MitchFlix kernel: ata6.00: failed command: READ FPDMA QUEUED May 10 22:48:22 MitchFlix kernel: ata6.00: cmd 60/40:78:20:bf:1e/05:00:31:00:00/40 tag 15 ncq dma 688128 in May 10 22:48:22 MitchFlix kernel: res 40/00:a0:c8:d6:1e/00:00:31:00:00/40 Emask 0x50 (ATA bus error) May 10 22:48:22 MitchFlix kernel: ata6.00: status: { DRDY } May 10 22:48:22 MitchFlix kernel: ata6.00: failed command: READ FPDMA QUEUED May 10 22:48:22 MitchFlix kernel: ata6.00: cmd 60/a8:80:60:c4:1e/02:00:31:00:00/40 tag 16 ncq dma 348160 in May 10 22:48:22 MitchFlix kernel: res 40/00:a0:c8:d6:1e/00:00:31:00:00/40 Emask 0x50 (ATA bus error) May 10 22:48:22 MitchFlix kernel: ata6.00: status: { DRDY } May 10 22:48:22 MitchFlix kernel: ata6.00: failed command: READ FPDMA QUEUED May 10 22:48:22 MitchFlix kernel: ata6.00: cmd 60/40:88:08:c7:1e/05:00:31:00:00/40 tag 17 ncq dma 688128 in May 10 22:48:22 MitchFlix kernel: res 40/00:a0:c8:d6:1e/00:00:31:00:00/40 Emask 0x50 (ATA bus error) May 10 22:48:22 MitchFlix kernel: ata6.00: status: { DRDY } May 10 22:48:22 MitchFlix kernel: ata6.00: failed command: READ FPDMA QUEUED May 10 22:48:22 MitchFlix kernel: ata6.00: cmd 60/40:90:48:cc:1e/05:00:31:00:00/40 tag 18 ncq dma 688128 in May 10 22:48:22 MitchFlix kernel: res 40/00:a0:c8:d6:1e/00:00:31:00:00/40 Emask 0x50 (ATA bus error) Check/replace cables.

As a way to be able to compare the data on the rebuilt disk vs old disk, then if all OK you can rebuild again on the old disk (or do the new config).

There's no reason to think that any data is missing/damaged but It's up to you, though IMHO instead of doing that a better option would be to rebuild to a spare disk.

Not normal but likely the disk was used with zfs before, xfs partition is still mounting correctly, check contents look correct, don't forget to unmount before the new config.

Yes, you can test one by one

No. First: Then: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed. You can even check "parity is already valid", then just run a correcting check since a few sync errors are expected.

You can still write and use the user shares normally while avoiding the overheard by writing directly to a disk share, just enable disk shares and then write to: \\tower\cache\your_share instead of \\tower\your_share

Check filesystem on disk5.

Syslog starts over after a reboot, if it keeps happening try this.

In this case I would do a new config and re-sync parity, still make sure actual disk1 is mounting correctly before doing it, you can do that with UD, disk1 must unassigned and array stopped.

What warning?

User shares always add some overheat, but for some unknown reason (at least to me) some users are much more affected than others.

Please post the diagnostics: Tools -> Diagnostics

Yes. Yes.

Likely related to this, there are some common issues with the Ryzen SATA controller under heavy load, usually during a parity check or rebuild, there are some reports that updating to v6.9-beta1 helps due to the newer kernel.

The device errors look more like a connection problem with this SSD: Device Model: CT240BX500SSD1 Serial Number: 1919E1816D1E Replace/swap both cables.

If the latest xfs_repair can't fix the filesystem don't have any other ideas besides the ones suggested above. P.S. don't forget to delete the "extra" folder on the flash drive.

Almost certainly a disk problem, you can run an extended SMART test to confirm.

Please post the diagnostics: Tools -> Diagnostics

Forgot to mention, CPU is overheating and throttling down, check cooling.

Syslog starts over after a reboot, try this.

Looks more like a controller problem, you're using a Marvell controller with/connected to SATA port multipliers, either one is not recommended, and especially not both together, still good idea to run an extended SMART test on parity.

Same if you boot in safe mode? P.S. in the future please attach diags directly to the forum.