JorgeB

Apr 17 16:28:45 Tower emhttpd: unclean shutdown detected A few sync errors are normal, even expected, after an unclean shutdown.

Errors on parity also look like a power/connection issue, it dropped offline.

Apparent connections issues with cache2, replace cables.

One request if you don't mind, I would like to see the devices grouped more closely together, similar to the array devices, so they didn't take so much vertical real estate and more could fit on the page, e.g. 8 arrays devices vs 8 UDs: Also not a very big fan of the new color, maybe because they are links now? But not a big deal.

You can recover the space with trim, see here.

Already solved here:

Please post the diagnostics: Tools -> Diagnostics

Apr 13 22:59:55 CHASM kernel: usb 1-1-port4: disabled by hub (EMI?), re-enabling... Apr 13 22:59:55 CHASM kernel: usb 1-1.4: USB disconnect, device number 16 Apr 13 22:59:55 CHASM kernel: usb 1-1.4: new low-speed USB device number 17 using ehci-pci Apr 13 22:59:55 CHASM kernel: hid-generic 0003:0764:0501.000F: hiddev96,hidraw0: USB HID v1.10 Device [CPS Value2200E] on usb-0000:00:1a.0-1.4/input0 Apr 13 23:00:01 CHASM apcupsd[30039]: Communications with UPS restored. USB ports is getting disable and the device keeps disconnecting and reconnecting, try a different USB port.

You can mirror he syslog to the flash drive or to the array, AFAIK you can't use devices outside user shares.

Try this.

Cache filesystem is corrupt again, if it's happening multiple times without an apparent reason you likely have some hardware issue.

Those are system devices, not errors.

Please post the diagnostics: Tools -> Diagnostics

Please post the diagnostics: Tools -> Diagnostics

You could remove just the controller an updated it on a Windows desktop, that's what I usually do.

Since you mentioned strange noises, and when you get the new disk, make sure to check/replace the power connection, bad/failing power can sometimes cause disks to develop bad sectors.

Also note that unmap doesn't work with all vdisk drivers, more info here.

It's a known issue with smartmontools on latest release and some SAS devices, it will work if you downgrade to v6.8.2.

Try this, it might catch something.

Try transferring a large file from your desktop to Unraid, if you get the same 40MB/s there's likely a problem with the array, if you get 100MB/s+ (assuming gigabit) it's likely a problem with the NAS.

It would be faster but pretty sure Unraid/UD won't be able to mount that disk, even if you had the other raid members there.

Yes, not an issue without parity, source NAS is the likelier bottleneck.

If you don't need the extra space remove it, one less point of failure, also array writes can be faster since it's basically RAID1, but as long as you have system notifications enable and do regular parity checks it's unlikely to fail "silently".

Thats's supported by UD, so it's fine.

This is a weird one. Lets first confirm if it's related to something installed/configured on the flash drive, backup current flash drive, recreate it using the USB tool, then restore only super.dat and the key (both on the config folder), boot Unraid, disable docker and VM services, start array, check for disk activity.