JorgeB

Did you do this? What's the iperf max bandwidth with a single transfer?

HBA problem: Mar 13 19:29:28 Tower kernel: mpt2sas_cm0: fault_state(0x0d04)! Upgrade firmware to latest (20.00.07.00), make sure it's well seated and sufficiently cooled, you can also try a different slot if available.

Link keeps going up and down, try disabling bonding, failing that try a different NIC if available,

Since the pool was started with a single device it was converted to single profile, so the old device can't just be re-assigned and used with existing data, but you can re-add it to the pool and it will be balanced to raid1 again (and the warning is correct, all data on that device will be deleted, but that's OK), if the pool was never started with a single device then there would be a way to pick up the old pool without reconverting.

It can be used with any board that supports PCIe bifurcation, pretty sure the H310M-A doesn't, but check the manual/bios.

You'll need to copy any data from the emulated disk to other disk(s), then do a new config and re-sync parity.

Check filesystem on disk5: Mar 11 03:40:41 rubble kernel: XFS (md5): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x3851cf2a8 xfs_inode_buf_verify Mar 11 03:40:41 rubble kernel: XFS (md5): Unmount and run xfs_repair

Pre v6.8.3 it's reboot/powerdown, maybe you didn't reboot yet after updating?

If rebuilding on top make sure the emulated disk is mounting first.

First thing there's a problem identifying this disk: Mar 13 09:17:45 Tower emhttpd: ST2000DM006_Z505EWTZ (sdc) 512 8089950 Even the SMART report is incomplete, check/replace both cables and post new diags

There's a btrfs filesystem crashing, most likely the docker image, you should recreate it. CPU is still overheating: Mar 12 08:25:50 Valyria kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 51) Mar 12 08:25:50 Valyria kernel: CPU14: Package temperature above threshold, cpu clock throttled (total events = 51) Mar 12 08:25:50 Valyria kernel: CPU8: Package temperature above threshold, cpu clock throttled (total events = 51) Mar 12 08:25:50 Valyria kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 51) Mar 12 08:25:50 Valyria kernel: CPU11: Package temperature above threshold, cpu clock throttled (total events = 51)

Changed Priority to Other

Disk is failing to initialize, good idea to also swap/replace the power cable, if problem persists it's likely a failing disk.

No, you just need to monitor the UDMA_CRC attribute, if it keeps increasing there's still a problem, but note that it will never go back to 0, you can just acknowledge current value.

SMART attributes look fine, there are some UDMA CRC errors but that is a connection issue, usually the SATA cable, there are also some recent UNC @ LBA errors, but the extended test passed, so it's fine, at least for now, you can acknowledge the CRC errors.

According to the log mover schedule is disable: Mar 8 00:00:01 Tower root: Mover schedule disabled ... Mar 8 04:00:01 Tower root: Mover schedule disabled ... Mar 8 08:00:01 Tower root: Mover schedule disabled Can you post a screenshot of the mover settings?

Still SATA controller problems: Mar 12 16:34:37 SchumacherTower kernel: ahci 0000:02:00.1: AHCI controller unavailable! Mar 12 16:34:38 SchumacherTower kernel: ata10: failed to resume link (SControl FFFFFFFF) Mar 12 16:34:38 SchumacherTower kernel: ata10: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Mar 12 16:34:43 SchumacherTower kernel: ata10: hard resetting link Mar 12 16:34:43 SchumacherTower kernel: ahci 0000:02:00.1: AHCI controller unavailable! Mar 12 16:34:44 SchumacherTower kernel: ata10: failed to resume link (SControl FFFFFFFF) Mar 12 16:34:44 SchumacherTower kernel: ata10: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Mar 12 16:34:44 SchumacherTower kernel: ata10: limiting SATA link speed to <unknown> Mar 12 16:34:49 SchumacherTower kernel: ata10: hard resetting link Mar 12 16:34:49 SchumacherTower kernel: ahci 0000:02:00.1: AHCI controller unavailable! Mar 12 16:34:50 SchumacherTower kernel: ata10: failed to resume link (SControl FFFFFFFF) Mar 12 16:34:50 SchumacherTower kernel: ata10: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Mar 12 16:34:50 SchumacherTower kernel: ata10.00: disabled ... Mar 12 16:35:05 SchumacherTower kernel: ata9.00: disabled ... Mar 12 16:35:59 SchumacherTower kernel: ata6.00: disabled ... Mar 12 16:35:59 SchumacherTower kernel: ata5.00: disabled Multiple disks dropping offline, there are also several NIC related errors, if you can I would try with a different board, that one appears to have issues, either actual problems or compatibility issues with Linux.

Yes, drives are tracked by serial number, though you'll need a PCIe controller, there aren't any good PCI-X options.

If memtest finds nothing try with a btrfs pool again, btrfs usually gets corrupted faster when there's a hardware problem, and the type of corruption might give a clue on what the issue is, just be sure to save the diags before rebooting.

Recreating the docker image should fix it for now, but it will likely happen again.

Multiple filesystem corruptions suggest a hardware problem, like bad RAM, I would start with memtest.

SAT2-MV8 controller keeps crashing, those controllers have issues with recent devices (both HDD and SSD) and not recommended for some time, they usually work fine with all older disks up to 2/3TB, but have issues with some newer ones, it *might* work if you disconnect the 8TB disk.

What plex docker are you using?

Please use the appropriate support thread for that docker: