JorgeB

I don't think SAS vs SATA will make much of a difference with Unraid, more important is the disk platter size, i.e., more recent disks with a higher areal density will likely be generally faster.

Would need the diags with the new NVMe to confirm, but most likely adding the new device changes the IDs of the current devices being passed-through, and because of that the SATA controller where that drive is connected is now unavailable to Unraid.

Second NVMe device is bound to vfio-pci.

Please post the complete diagnostics: Tools -> Diagnostics

Post new diags downloaded during a transfer, they might give a clue.

Also note that assuming this really has 4 controllers, an Asmedia controller maxes out at around 200MB/s with both ports in use, so that will limit speed before the SATA2 link.

Might not be, according to the description it has 4 Asmedia chips, and that would explain being x4, each Asmedia controller would use an x1 link, @Zippiplease post the diagnostics to confirm. Yep, link speed issue is likely a compatibility problem, but it won't make any difference for current spinning disks.

Yeah, pool error handing could use some improvements, I've been requesting that for many years but not yet implemented.

It's up to you, IMHO servers and overclock don't go very well together, but you can do it, just remember to go back to stock before doing any future troubleshooting, to rule that out.

Create a new flash using the USB tool and restore only the config folder, that's all you need.

That suggests it's a SAS1/SATA2 backplane.

Maybe, or another network issue, but I've always used SMB for Kodi and never had any issues.

That means it's not an Unraid issue, try it in a different slot.

Old disk2 was corrupt, now the problem is that parity isn't 100% valid because you are using the old disk4, so there's some filesystem corruption on the emulated disk, this is expected in this case and if it's the only issue it should be easily fixed by xfs_repair.

It's in the link above, but depends on the config, if you're not sure how to check you can post the diagnostics and I can tell you.

You should also lower the RAM speed to the officially supported max for that config, it's not 3600MHz.

Looks like it didn't mount, not that surprising since like mentioned parity wouldn't 100% in sync, you'll need to run xfs_repair on it after it's done (or now after canceling the rebuild).

No, but if you didn't format it something else happened.

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

It does:

Try uninstalling the docker folder plugin.

USB errors are possibly from the card reader, but syslog is not showing the boot process, post a new one after you reboot.

That's from the Dynamix File Integrity plugin.

That command enables all disks except the ones listed, disk2 that needs to be rebuilt, and disk29 (parity2), since there won't be one.

You can try the invalid slot command, follow the instructions below carefully and ask if there's any doubt. -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, don't assign parity2, if you have a spare to rebuild disk2 (same size or larger) use it since it will leave you with more options if this doesn't work -Important - After checking the assignments leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters): mdcmd set invalidslot 2 29 -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk2 will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.