JorgeB

Boot in normal mode, grab the diags by typing "diagnostics" in the console and attach them here.

That should work assuming it's a redundant pool, start the array with all pool devices assigned and post the diagnostics.

Yep.

Note also that after the problem is fixed the first check may still find sync errors, but the 2nd one should find 0.

Try the other options, btrfs restore is the most likely to work with disk1, if none of the options work can't help anymore, you can try the mailing list or IRC.

Yeah, that's normal, but yeah, I would also prefer if they didn't reset.

If you want future proof look for a Supermicro chassis with a SAS3 expander, those are databolt enable, chassis is also much better than the Norco you were looking at, but also much more expensive.

Or the JMB controller doesn't like that specific disk model, if it was only that disk you can try connecting it to another controller instead, like the onboard SATA ports.

It may be LSI, but it's not SAS3, so no databolt.

👍 It does .

That's what cache=prefer does: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=537383

You have an unassigned disk spamming the log with ATA errors, since it's unassigned disconnect it (or replace cables to see if it helps): ST10000VN0004_ZA2B8RZL As for the unmountable disks: Parity can't help with filesystem corruption, btrfs was detecting data corruption, this is usually a hardware problem like bad RAM, if you think that's fixed there are some recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490 Also see here for what to do about the stats errors: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

Changed Priority to Other

If you set it to that you'll get a not enough space error for any transfer, that's the minimum free space for disk in that share, when that threshold is met it starts writing to another disk, and there are no 200TB disks.

Unlikely

I just did without any issues, on v6.9.2, but yeah, post the diags, might be something visible there.

Yes.

It won't work if you're booting UEFI, only for CSM/Legacy BIOS.

Depends if the expander is an LSI SAS3 with databolt, again see here:

That's not normal and should never happen, new config by itself doesn't touch the drives, encrypted or not, but without the diagnostics can't really say what it could be.

I was responding to this: But if you don't have cache you still need to selected the correct setting, or will still get not enough space errors once disks start filling up, depending on allocation method. That sounds like a Krusader issue, but I never used it.

It's serious unless they are false positives, you can confirm by running an extended SMART test.

During a balance, i.e., right after adding a new device, it's normal for the space to be wrong until it's finished.

Please post the diagnostics: Tools -> Diagnostics.