JorgeB

I would, the pending sectors are real since it failed the SMART test, also these attributes look very bad: They should be zero, or at least very low, on a healthy WD drive.

Please post the diagnostics: Tools -> Diagnostics

Most likely, either those are new disks or something else happened that wiped the partitions, if the latter a file recovery util like UFS explorer should still find the data.

You need to format the disks, next to array start/stop buttons.

Yes

Do you really have 1TB of RAM? I'm guessing that's confusing Unraid, probably first user with so much RAM.

2.5GT/s means a PCIe 1.0 slot, if it was also a x4 link instead of x8 it would only have a quarter of normal bandwidth, so big impact is expected.

Diags don't show any disk1 issues, they do show read errors on disk4 (looks more like a power/connection problem) during the pariuty sync, so parity is invalid, because of the log spam caused by those errors it doesn't show anything more after that. Please post current diags.

New config didn't take, all disks must change to a blue icon, repeat it. You missed the "Apply"

Mover won't overwrite any existing files, you can enable mover logging and see why they are not being moved, or post the diags after doing that.

The "invalid partition error" suggests those disks weren't array data disks, or something happened to them and the partition/mbr was changed and is not what Unraid expects, unassigned them all and check with the UD plugin if a filesystem is detected on any of them, UD won't care for the partition layout, as long as there is a partition.

Yes, but always from disk to disk, never disk to share or share to disk.

This started with the disk dropping offline: Mar 4 08:24:11 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Mar 4 08:24:15 Tower kernel: ata4: COMRESET failed (errno=-16) Mar 4 08:24:21 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Mar 4 08:24:25 Tower kernel: ata4: COMRESET failed (errno=-16) Mar 4 08:24:31 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Mar 4 08:25:00 Tower kernel: ata4: COMRESET failed (errno=-16) Mar 4 08:25:00 Tower kernel: ata4: limiting SATA link speed to 3.0 Gbps Mar 4 08:25:05 Tower kernel: ata4: COMRESET failed (errno=-16) Mar 4 08:25:05 Tower kernel: ata4: reset failed, giving up Mar 4 08:25:05 Tower kernel: ata4.00: disabled Then it came back online, before dropping again, so it suggests a power/connection issue, especially if SMART is OK, replace/swap both cables or slot with a different disk to rule that out, if it happens again to the same disk after that it could be a disk problem.

Check the board bios, usually there's more than one virtualization option, vt-d might be enable but not vt-x, also look for a bios update

Depends if the controller will be installed on a CPU or PCH slot, if PCH it will share the bandwidth with the onboard SATA ports, there are also some performance numbers for that in the link above.

Correct, but 2GB/s is more than enough for 4 disks, 4 SSDs would be a different story.

^this

Those are the same, still recommend changing the paths to /mnt/cache instead of /mnt/user, no idea what happened to the dockers since there weren't any errors I could see, but that image looks brand new based on the transid, you can quickly add them back using the CA previous apps function.

If it was on cache it would have been re-created, but since you're using /mnt/user paths you might have two images, what's the output of: find /mnt -name docker.img

Did you re-format cache? Also please post current diags.

There are issues with the flash drive, backup and re-create: Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (5 != 4) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): Filesystem has been set read-only Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (6 != 5) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (7 != 6) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (8 != 7) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (9 != 8) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (10 != 9) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (11 != 10) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (12 != 11) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (13 != 12) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (14 != 13) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (15 != 14) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (16 != 15) Mar 4 16:31:44 Beast kernel: ata11.00: configured for UDMA/133 Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (17 != 16) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (18 != 17) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (19 != 18) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (20 != 19)

x4 is more than enough for 4 spinners. Also note that the JMB controller is PCIe 3.0, so approximately same bandwidth as an x8 PCIe 2.0 slot, assuming board supports PCIe 3.0 obviously. Some performance numbers in this thread.

I assume you mean disk5, if so a few reallocated sectors can be OK, if it remains stable, though it's never a good sign, especially on a fairly new disk, you should at least run an extended SMART test, as for warranty you'll get a refurbished disk, and those are a crapshoot, sometimes the devil you know...assuming the extended SMART test is OK. Regarding the data in case you decide to replace it, you can use the server with the emulated disk for a few days, especially since you have dual parity, or rebuild to a spare.

Also see this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

You can see in the syslog that ata10 is parity2, doesn't look like a disk problem, looks like a connection problem.