JorgeB

Not as far as I known, this works with SAMBA and zfs or btrfs but you need to have regular snapshots scheduled, you can then revert any file to any of those.

Do you have another source computer you could try with?

One is enough.

There's a pinned thread discussing exactly that, you can read it for some ideas:

Copy all the bz* files from test flash to other flash overwriting existing ones.

No driver for your NIC in v6.8, you can update to v6.9-beta25.

This is still above the max officially supported RAM speed for your CPU.

System/event log might have more info, check your BIOS, e.g.:

Mount them with the UD plugin in read-only mode and check contents.

Temperature reporting is not a stock Unraid feature, you need to report that on the existing plugin support thread.

LSISAS2308: FWVersion(17.85.00.00) Current firmware is 20.00.07.00

Still no devices being detected, the HBA is initializing correctly, though it does log this which is not normal: Sep 15 15:18:15 unRaid kernel: mpt2sas_cm1: Temperature Threshold flags 0 exceeded for Sensor: 0 !!! Sep 15 15:18:15 unRaid kernel: mpt2sas_cm1: Current Temp In Celsius: 51 Sep 15 15:18:15 unRaid kernel: mpt2sas_cm0: Temperature Threshold flags 0 exceeded for Sensor: 0 !!! Sep 15 15:18:15 unRaid kernel: mpt2sas_cm0: Current Temp In Celsius: 44 One thing you could try is flashing a BIOS and checking if the devices are detected there, also take the opportunity to flash the latest firmware.

That looks related to rclone, best bet is to ask on the existing support thread.

It's not right, only member of the pool is cache2, stop array, unassign cache1, start/stop array, re-assign cache1, start array, that should fix it, if it doesn't please post new diags.

That is a corrupt cache filesystem, best bet is to backup and re-format. RAM is overclocked for current config, see here, it's a known issue with Ryzen and in some cases a reason for data corruption.

If cache keeps getting corrupt without an apparent reason that usually indicates a hardware problem.

Yeah, that's why we ask for the full diags instead of just the syslog, and I should have asked for them before replying, the problem would be visible there.

Yeah, and only 3 SATA ports are being detected, have you tried the new beta? Newer kernel might make a difference.

Sep 15 20:13:03 BIG-BOSS kernel: ata1: SATA link down (SStatus 0 SControl 300) Sep 15 20:13:03 BIG-BOSS kernel: ata3: SATA link down (SStatus 0 SControl 300) Sep 15 20:13:03 BIG-BOSS kernel: ata2: SATA link down (SStatus 0 SControl 300) Strange they show up in the BIOS but don't see what can be done on the Unraid side.

Yes, forgot about those, they should remain on cache.

It's very straight forward, more info here: https://unraid.net/blog/top-support-and-forum-questions-answered

Try disabling NIC bonding, sometimes causes issues.

Yes, if you want to have everything on those shares in the array after the mover runs (and use cache for initial transfer).

Any share that has files (or just even the top level folder) on cache, like the M----s share for example, will say unprotected, since you have a single cache device, set them to cache="yes" and run the mover, so everything is moved to the array.

Most free is bad for performance since writes to parity disk will overlap when changing data disk, resulting in worse write performance.