JorgeB

Best bet would probably be to email Asrock support to get a list all the SEL codes, or at least tell you what those are about.

If there's no parity the problem is likely with the USB enclosure, it might not be linked at USB 3.0, test transferring from your desktop to the array.

That's odd, many users with that board, you could try booting UEFI instead.

It will work, depending on how you copy it you might need to be re-created, but that's easy to do, in fact probably best to just do that instead of copying it, only copy the other folders.

This requires all data devices to me members of the same pool, it prevents the full utilization of different size devices and if more disks fails than current redundancy you lose the whole pool, for that you already have FreeNAS, one of the main advantages of Unraid is every data disk being an independent filesystem, even if LT supports ZFS in the future, and I hope they will, array devices will still be an independent filesystem, i.e. without zfs redundancy, redundancy would still be done by parity, zfs would be nice mostly for use with cache pool(s), and shfs is still needed to make them part of the user shares.

Flash drive problems: Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32768) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32769) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32770) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32771) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32772) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32773) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32774) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32775) failed Apr 23 04:40:12 Tower kernel: FAT-fs (sda1): Directory bread(block 32776) failed Run chkdsk on it and make sure it's using a USB 2.0 port, if if keeps happening try recreating or replacing it.

You can just rename the current plugins so they don't install on boot, you can then rename them back, they are on flash/config/plugins, change the extension from .plg to anything else.

If it doesn't do it in safe mode remove all plugins, check it still doesn't do it then start adding them one by one.

Then that looks more like a problem with your desktop, and I'm not seeing any smb/shares related issues on the syslog.

Did you find out and stopped what's doing the multiple writes to the array? Until you fix that there's not much point in looking at other things.

You can't add data and parity disks at the same time, do it one a a time.

Try running xfs_repair again, and if the reallocated sectors keep increasing you should consider replacing that disk.

CRC errors are a connection problem, also a single error is nothing to worry about, just acknowledge it on the dashboard, if it keeps increasing re-seat the device.

Please don't double post, the other post was on the correct forum, likely didn't get much help because it's a very specific question, not because it wasn't seen, but if anyone else has any idea how to help the OP please reply in the original thread.

If you current cache if btrfs (and it was on the last diags you posted) and you can connect the new device while keeping the old one connected you can do an online replacement, see here, but see the notes, especially the bold parts.

We need the diagnostics (Tools -> Diagnostics), grabbed after the problem manifests itself and before rebooting.

Make sure you're respecting max officially supported RAM speed depending on the config, a common source of problems with Ryzen.

That's a hardware issue, most likely RAM, CPU or board related.

That's old news, and the WD blog I linked above is also about that, WD clarifying which models are CMR and what which are SMR.

Usually the Barracuda Compute SMR, ST8000DM004 for the 8TB, other sizes usually use disks from the same family, SMR disk are usually fine with Unraid, but these Seagates do have a low workload, for whatever that's worth, not even enough for a monthly parity check.

Could be a disk issue, SMART looks mostly OK, run an extended SMART test.

No, cancel current check (since it's non correct), start a correcting check, then run reiserfsck.

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

They are, and SMR is also PMR (with SMR), that 's why now CMR is preferred when referring to conventional PMR drives, for example: https://blog.westerndigital.com/wd-red-nas-drives/

That's odd, pv is usually much faster than rsync and closer to real device speed, if it's not working for you you need to find another tool to test with, like I mentioned rsync is not a good tool for benchmarking.