JorgeB

If you mean this it just represents the total allocated chunks, they are allocated (and removed) as needed, GUI should show correct total, used and free space for this type of pool.

SMART section in the GUI only works correctly with SATA devices, with SAS some parts don't work correctly since SMART reports are very different, SMART tests also don't work.

10% is the test amount remaining. You should first replace the failing disk, if you want to upgrade parity and use one of the parity disks as a replacement for disk1 you can do a parity swap.

Disk dropped offline while unmounting the filesystem, not after array stop: Oct 12 08:15:17 Elshaneed kernel: XFS (md3): Unmounting Filesystem Oct 12 08:16:20 Elshaneed kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 12 08:16:20 Elshaneed kernel: ata5.00: failed command: FLUSH CACHE EXT Oct 12 08:16:20 Elshaneed kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 11 Oct 12 08:16:20 Elshaneed kernel: res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Oct 12 08:16:20 Elshaneed kernel: ata5.00: status: { DRDY } Oct 12 08:16:20 Elshaneed kernel: ata5: hard resetting link Oct 12 08:16:26 Elshaneed kernel: ata5: link is slow to respond, please be patient (ready=0) Oct 12 08:16:30 Elshaneed kernel: ata5: COMRESET failed (errno=-16) Oct 12 08:16:30 Elshaneed kernel: ata5: hard resetting link Oct 12 08:16:36 Elshaneed kernel: ata5: link is slow to respond, please be patient (ready=0) Oct 12 08:16:40 Elshaneed kernel: ata5: COMRESET failed (errno=-16) Oct 12 08:16:40 Elshaneed kernel: ata5: hard resetting link Oct 12 08:16:46 Elshaneed kernel: ata5: link is slow to respond, please be patient (ready=0) Oct 12 08:17:15 Elshaneed kernel: ata5: COMRESET failed (errno=-16) Oct 12 08:17:15 Elshaneed kernel: ata5: limiting SATA link speed to 3.0 Gbps Oct 12 08:17:15 Elshaneed kernel: ata5: hard resetting link Oct 12 08:17:20 Elshaneed kernel: ata5: COMRESET failed (errno=-16) Oct 12 08:17:20 Elshaneed kernel: ata5: reset failed, giving up Oct 12 08:17:20 Elshaneed kernel: ata5.00: disabled Since it dropped there's no SMART, but this is usually a power/connection problem.

Current array with disk5 and without disk4.

No problem, and technically it's not a plugin issue, but since you're using the plugin and it can be solved by the plugin it can be posted there.

That meas the same filesystem is already mounted in another device, you can change the UUID in the UD plugin setting, also next time please use the existing plugin support thread.

You can do a new config with disk5 to recover that, assuming the disk is OK, if disk4 is really failing no easy way to recover that, you can try ddrescue.

No, because disk5 is already disable, just connecting it won't enable it, it would need to be rebuilt, but since disk4 has issue it's not possible.

Sounds like flash drive problems, make sure you're using a USB 2.0 port.

You can do it manually using the console, to replace a device from a pool (if you have enough ports to have both old and new devices connected simultaneously): You need to first partition the new device, to do that format it using the UD plugin, you can use any filesystem, then with the array started type: btrfs replace start -f /dev/sdX1 /dev/sdY1 /mnt/poolname Replace X with source, Y with target, note the 1 in the end of both, you can check replacement progress with: btrfs replace status /mnt/poolname When done you need to reset the pool assignments, for that you can do this: Stop the array, if Docker/VM services are using that pool disable them, unassign all pool devices, start array to make Unraid "forget" current pool config, stop array, reassign all pool devices now with the replaced device (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any pool device), re-enable Docker/VMs if needed, start array.

There are still constant ATA errors on disk4, if you replaced the cables it's likely a disk problem, disabled disk5 can't be correctly emulated because of those errors.

Both are logged as disk issues, run an extended SMART test on both parity and disk1.

That's how high water works: https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water

That shows remapped sectors, like mentioned it's not a good sign but it doesn't mean the disk failed.

Replace cables on parity disk and try again.

There's a bug: You'd need to do it manually.

One of the LSI HBAs dropped: Oct 10 22:14:24 Tower kernel: mpt2sas_cm1: sending diag reset !! Oct 10 22:14:24 Tower kernel: mpt2sas_cm1: diag reset: FAILED Oct 10 22:14:26 Tower kernel: iommu: Removing device 0000:03:00.0 from group 19 Check that it's well seated and sufficiently cooled, you can also try a different PICe slot if available.

It might help if you mention on what disk(s) you have been getting warnings.

Please post the diagnostics.

You run both on Unraid, if you want one Unraid server to access another one.

Please continue discussion here:

Best bet is to post in the existing docker support thread:

Sorry, meant to say disk4.

It's still above the officially supported speeds by AMD, see the tables in the link above.