JorgeB

In my experience some SMR disks work fine with Unraid, e.g., the Seagate drives I've have, both the 8TB Archive model as well as 4TB 2.5" drives, they are fast during a rebuild/sync and don't notice any big slowdowns during large sequential transfers (mostly large files, might be different with small files), on the other hand WD and Toshiba SMR drives behave normally during rebuild/sync but they get extremely slow during large transfers, even for large files.

So if the respective folders already exist in disk6 it will be used by Unraid.

The vdisk might be corrupt, no way of knowing.

This points to a device problem.

Best bet is to try a different flash drive, you can see if it works first before transferring the license.

Enabling NOCOW turns off data checksum, so those can't be checked or fixed.

Split level overrides allocation method.

This means it was corrupt, btrfs won't let you copy/read a corrupt file. That shouldn't be a problem. Unlikely to be a device problem, if it's hardware related it's likely RAM.

Use IP from a different subnet.

WD and Toshiba 8TB or above Seagate 10TB or above All others might be.

I would think so, extremely unlikely to have 2 disks returning corrupt data, having one is already very unusual.

Most likely, I would run another one just to make sure, kind of worrying that a disk starts corrupting data out of the blue without any apparent reason, and SMART looks normal.

I've never used that program, best bet is to ask for help directly from them.

Looks more like a disk problem, there's no SMART report for that disk in the diags, see if you can get one manually.

You can try this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

You can try this: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disk you want to rebuild, replacement disk should be same size or larger than the old one -Check both "parity is already valid" and "maintenance mode" and start the array -Stop array -Unassign the disk you want to rebuild -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk -If the emulated disk mounts and contents look correct stop the array -Re-assign the disk to rebuild and start array to begin.

That issue is usually caused by the flash drive, but not always clear why it happens, wiping the flash drive can sometimes fix it but not always, kind of an elusive problem, a different flash drive can also help, glad it's solved.

Try rebooting to reload the new partition info.

Might not be a config issue, copy your config to the new flash drive, array won't start because of the key but you can still see if it boots.

Only breakout cables (miniSAS to SATA or vice versa) have a direction, forward or reverse, miniSAS to miniSAS cables work in any direction.

That's not official, with 4 dual rank DIMMs max officially supported RAM speed for that CPU is 2666Mhz, and Ryzen and known issues with overclocked RAM, including data corruption.

Some SMART issues, but because of the way it dropped and the very large number of CRC errors (though these could be old) it could just be a connection issue, replace/swap cables and see how it goes.

How many ports do you need? There aren't many good 4 port options, there's the 5 port JMB385 controller, though most times you can get an used 8port LSI HBA for about the same.

I have the Microtik CRS309-1G-8S+IN, still need transceivers for the longer fiber cables.

For me SFP+ was the best option, since most servers are close together and can work with just a DAC cable, I do have 3 or 4 that are too far away for DAC, but got fiber cables together with the transceivers pretty cheap on ebay.