JorgeB

Backup current flash, redo-it with the USB util and then restore only the key from the backup.

Pending sectors usually mean bad sectors, i.e. sectors that can't be read, extended SMART test confirms it's a disk problem, so yes you need to replace it. Regarding parity valid or not, we'd need the diagnostics, but if there were no errors during the parity sync it can be assumed valid (assuming no other hardware issues that would cause sync errors like bad or failing RAM), and it also depends if the parity check that ran after was correct or non correct, in some rare cases a correcting check can corrupt parity if there are read errors an a data disk, but again we'd need the diags to confirm.

The HBA would be one of the last suspects for me, power related would be my first, but if you replaced practically everything else...

Still no link on either NIC, also you need to set the main NIC you want use as eth0 (then reboot)

This looks like a power/connection issue, and it's affecting multiple disks, if you already replaced cables and PSU next step would be trying a different HBA.

Thanks for reporting back, if you don't mind I'm going to tag it solved.

See here to enable syslog mirror to flash, then post that syslog when the shares fails again. Cache pool is not redundant, see here to fix.

See if this helps, if not please post the diagnostics. P.S. you can upload screenshots/files directly to the forum, no need to use external sites.

Then you'll need to force a reboot. Nothing I can see.

Memtest doesn't detect all errors, but it appears to be especially true with Ryzen and OC RAM as the same happened to other users in similar cases, no errors on memtest but always sync errors on every parity check.

They were both mounted, despite one being unassigned, but I see by the edits you made it work. For now I recommend having auto array start disable when there's a cache pool, since Unraid will start with a missing cache device and can cause issues.

Pool mounted but went read-only, if needed backup any data because you'll likely need to re-format it.

Try pause/unpause, if it doesn't work reboot and start another check.

Possibly, would need the diags form a start with just the single cache, unassign cache2 before starting.

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

Current HBA with single link is still good for 2GB/s+, unlikely that you need more than that except during a parity check/disk rebuild, you can go to dual link and it will double the available bandwidth, but very unlikely to make any different for file streaming.

Yes and yes.

If the scrub isn't working best bet it's to move the data, and all data successfully moved can be considered OK, any files that give you i/o error during the transfer are corrupt, you can get them with btrfs restore, but like mentioned before they will still be corrupt.

Log is being spammed with these: Apr 13 09:05:38 SundialNAS rc.diskinfo[9965]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sda 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Apr 13 09:05:38 SundialNAS rc.diskinfo[9965]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdb 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Apr 13 09:05:38 SundialNAS rc.diskinfo[9965]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdc 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 See you can find what's causing them, maybe preclear?

There won't be any bottlenecks reading from a single disk, there will be during a parity check/ disk rebuild, but improving that won't resolve your problem.

If the subtitles were moved to disk1 the movie folder has to exist there also.

If the folder already exists on disk1 it will still try to move it there to respect split level, you need to delete/move the folder.

It's pretty common to have issues with the onboard SATA controller on some Ryzen boards, try v6.9-beta1, there are reports that the newer kernel helps.

Google "3.3v sata pin" if it's not that then please post the diagnostics: Tools -> Diagnostics

First thing would be not overclocking the RAM it's a known issue with Ryzen, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173