JorgeB

There are PCIe errors affecting multiple devices Sep 18 15:12:49 TheVault kernel: xhci_hcd 0000:01:00.0: AER: can't recover (no error_detected callback) Sep 18 15:12:49 TheVault kernel: ahci 0000:01:00.1: AER: can't recover (no error_detected callback) Sep 18 15:12:49 TheVault kernel: pci 0000:03:00.0: AER: can't recover (no error_detected callback) Sep 18 15:12:49 TheVault kernel: igb 0000:05:00.0 eth0: PCIe link lost Then Sep 18 15:13:30 TheVault kernel: ahci 0000:01:00.1: AHCI controller unavailable! Look for a BIOS update, you can also try updating to v6.11.0-rc5, newer kernel might help.

Not with the default write mode, assuming there are no controllers bottlenecks you can get much better write speeds with turbo write, at the expense of all disks spinning up for any write, note that you have a disable disk, need to rebuild it first for turbo write to work correctly.

Not that I know of.

Still having issues with multiple disks, looks more like a power/connection problem.

Nothing relevant logged that I can see, that usually points to a hardware problem, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Post read can fail because of bad RAM, run memtest.

Changed Status to Solved

Yes, if you still have issues with that do, but see here and here for some info, usually v6.10 is not the problem, how the containers are configured is.

They will be under /mnt/disks/UD_label, e.g. /mnt/disks/TV

See here, Ryzen with overclocked RAM like you have is known to corrupt data, and btrfs is detecting data corruption on the cache device, after fixing that run a scrub and delete/replace any corrupt files.

LSISAS3008: FWVersion(05.00.00.00) This will happen after updating to v6.10 with a very old firmware, update to current firmware for that model, IIRC it's 16.00.12.00, then do a new config, assign all devices to their previous slots, check "parity is already valid" and start the array.

Please post the diagnostics.

As mentioned this is normal.

Once there's corruption updating won't fix anything, but it should prevent more, run a scrub, if corrupt files are found they will be listed in the syslog, delete/replace them from backups.

LSISAS2308: FWVersion(20.00.06.00) This should be updated to 20.00.07.00, all other 20.00.xx releases have known issues.

LSISAS2308: FWVersion(15.00.00.00) This is old, update to latest (20.00.07.00).

Looks more like a power problem, could be the PSU.

It means data corruption is being detected by btrfs, likely the result of the error above.

Also make sure it's not the 3.3v issue, google "SATA 3.3v pin" or power the disks(s) with a Molex to SATA adapter since that won't have 3.3v.

Enable the syslog server and post that after a crash, also make sure power supply idle control is correctly set.

It can disable any the disks, parity or data, which one(s) it's luck of the draw, but it won't disabled more disks than there are parity drives.

SATA pool is OK, corruption errors are old, you should clear the stats, for the NVMe pool if the scrub fails best bet is to backup and re-format.

Yes, firmware is the same as the 9207-8i, you have both the IT and IR firmware on Broadcom's site

Sorry posted the wrong link: https://forums.unraid.net/bug-reports/stable-releases/6100-vnc-no-longer-connects-r1902/?do=findComment&comment=19127

Yes, at least most the ones I've used have, e.g.: [2:0:22:0] enclosu HP HP SAS EXP Card 2.08 - /dev/sg34 [23:0:28:0] enclosu HPE 12G SAS Exp Card 4.21 - /dev/sg41 [1:0:18:0] enclosu Intel RES2SV240 0d00 - /dev/sg19 [1:0:12:0] enclosu INTEL RES3TV360 B057 - /dev/sg26 But it can be a little cryptic, for example the Intel RES2SV240 uses hexadecimal in the device, in the download page you see firmware is v13 and that corresponds to 0d00, v12 to 0c00, v11 to 0b00, etc.