JorgeB

Better, but when all is working good would should get close to line speed with iperf.

Best bet is to post this on the Nvidia plugin support thread.

Likely to get a faster response if you post on the nerdpack support thread.

Edit network.cfg on flash/config or just delete/rename it and a new one will be created.

Should be fine assuming it's genuine. Not easy to diagnose power issues with the logs, easiest way is just to try with a different PSU if available.

Please post the diagnostics: Tools -> Diagnostics

Please don't double post, continue discussion here:

Though SMART looks bad I would first confirm disk1 is really failing by running an extended SMART test.

Run a single stream iperf test to check network bandwidth.

After starting the array see if you get the diags on the console by typing "diagnostics"

Pool has 3 assigned devices but only 2 are actually part of the pool, but appears to still be working, though completely full, move all data to the array, then worry about fixing it.

2 port Asmedia is fine, any Asmedia with more than 2 ports is using SATA port multipliers and that is no good. If 4/5 ports are enough look for a JMB585 based controller, for 8 ports look for any LSI with a SAS2008/2308/3008/3408 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.

By no issue do you mean you get 100MB/s+ with a single stream?

There is, but it will likely require a new config and possibly rebuilding every disk.

One of the cache pool devices had many errors (also there are also a few read errors on the other one) and it's failing to remove: May 17 14:55:35 WhiteHouse kernel: BTRFS info (device sdb1): bdev (null) errs: wr 6420558, rd 28315, flush 142629, corrupt 0, gen 0 May 17 14:55:35 WhiteHouse kernel: BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 20, flush 0, corrupt 0, gen 0 Best bet it to backup any cache data and recreate the pool, there are some recovery options here if needed, after recreation also see here for better pool monitoring.

If it's running yes.

It is, though there was a bug for pools created with v6.7.x where it wasn't.

Looks like that one is toast, btrfs restore is likely the only option, but if the pool was redundant you can try the other device, you can safely assign it after making Unraid forget current pool: Stop the array, unassign current cache device, start array to make Unraid "forget" current cache config, stop array, reassign the other cache device (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array. If the other device also doesn't mount see here for other recovery options.

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

That looks like an old xfs_repair bug, if you are not running latest Unraid (v6.8.3) upgrade and try again.

An LSI megaRAID controller is not the best option for Unraid, an LSI based HBA would be best, still better than the one you were using before.

It should be recoverable, run again without -n or nothing will be done, and if it asks for it use -L.

SMART looks bad and it's failing the extended SMART test, it needs to be replaced.

The disk appears to be failing, you can confirm by running an extended SMART, and WD must replace it if it's within the warranty period.

I would start with the cables and/or PSU.