JorgeB

You can use rsync with --remove-source-files, this way it will remove the already existing files on the destination, it would work best if the share or folder you're syncing fits on the destination, or rsync will abort possibly leaving a couple of dupes.

I believe so, there were previous btrfs related call traces and the last one was when trying to unmount cache.

You have a problem with your cache pool, it's failing to add a second device. Jun 10 11:38:02 Tower kernel: BTRFS info (device sdq1): relocating block group 1821087105024 flags data Jun 10 11:38:03 Tower kernel: BTRFS info (device sdq1): found 1412 extents Jun 10 11:38:05 Tower kernel: BTRFS info (device sdq1): found 1412 extents Jun 10 11:38:05 Tower kernel: BTRFS info (device sdq1): relocating block group 1820013363200 flags metadata Jun 10 11:38:07 Tower kernel: BTRFS: Transaction aborted (error -28) Usually easiest to backup and redo the pool, you can use this thread if you need help with the backup. You're also having issues with your NVMe device: Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 768 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 769 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 770 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 771 QID 7 timeout, aborting Jun 10 11:07:39 Tower kernel: nvme nvme0: I/O 772 QID 7 timeout, aborting Jun 10 11:08:09 Tower kernel: nvme nvme0: I/O 768 QID 7 timeout, reset controller Jun 10 11:08:40 Tower kernel: nvme nvme0: I/O 16 QID 0 timeout, reset controller Jun 10 11:10:11 Tower kernel: nvme nvme0: Device not ready; aborting reset Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:10:11 Tower kernel: nvme nvme0: Abort status: 0x7 Jun 10 11:11:12 Tower kernel: nvme nvme0: Device not ready; aborting reset Jun 10 11:11:12 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Jun 10 11:11:12 Tower kernel: nvme0n1: detected capacity change from 1024209543168 to 0

Anyone using btrfs can also just setup regular snapshots, they can be read-only so a good protection against ransomware.

Try the cable first, if it's not that then the cage is the next most likely candidate.

Because disk18 still has more free space than disk19.

It does need some airflow around it, remember these controllers are designed for servers with excellent ventilation, I usually have a 120mm or larger side case fan blowing air on them.

No, current cache needs to be btrfs like it says on the notes. Yes, unless something goes wrong, that's way it's always good to backup any important data. Yes.

Those are hardware errors and a general support problem, not a bug report, use the Nerdpack plugin to install mcelog, it may give some more info.

https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?do=findComment&comment=545988

That should be cache "yes", not cache "prefer".

When a share is created it creates the folder on the first disk configured for that share, did you delete it?

I believe so but I never had to update mine, as it was already 2.something, also I believe you need an HP controller to do the update.

No such limit when crossflashed to LSI IT mode, LSI firmware limit is 256 non raid devices.

Correct, use the 2 Intel SATA3 ports for the SSDs, SATA2 is enough for HDDs.

Post your diags and we can see.

No, those are the SCU ports, Marvell ports are the first 4 white ports 18-21

It's a 5 bay external SAS enclosure with a built in expander.

Yep, no problem, I have one on a server connected to 9 internal disks plus 5 external, and it's good for 150MB/s+

Yes. It's SAS2 but unlike most SAS2 expanders it's SATA2 max, not SATA3 (and it requires a certain firmware, IIRC 1.80+), so half the total bandwidth of a SATA3 expander, 1100MB/s for single link, twice that for dual link.

Yes. There's no 2TB limit.

That's a flash drive problem, if using an USB 3.0 port try a 2.0, it can also be a failing flash drive.

A clean shutdown wouldn't create diags, they are only created unRAID coudn't do a clean shutdown after the set timeout.

?

Post your diagnostics.