JorgeB

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.

Easiest is probably Unbalance.

You're welcome, just for completion and having more time to look at the logs the UD disk didn't unmount because it was busy: Apr 25 12:30:06 Universe unassigned.devices: Unmount of '/dev/sde1' failed. Error message: umount: /mnt/disks/WDC_WD20EZRZ-00Z5HB0_WD-WMC4N0N5FTHH: target is busy. Apr 25 12:30:07 Universe unassigned.devices: Since there aren't any open files, will force unmount. You likely had a terminal windows open on it, in those cases UD forces an unmount to prevent an unclean shutdown, so it appears unmounted in the GUI but it really isn't, hence why rebooting fix it. Also, if you don't mind I'm going to tag this solved.

It's constantly running out of memory.

Make sure rsync isn't using compression (-z) and enable turbo write.

What if you disconnect the LAN cable?

Not with UD, but you can use the ZFS plugin.

Btrfs also has snapshots and many of the same features as zfs, it's also much more flexible, i.e., multiple size devices can be used fully, raid profile can be changed without destroying the pool and new devices can be easily added or removed, on the other hand no doubt zfs is much more reliable. Yes, you can use them but all larger devices will have the extra capacity unused. It has its issues, but there's no Unraid without shfs, or something similar.

I'm sorry but what exactly is your question?

To remove it from the array you need to do a new config (tools -> new config), but note that you need to copy the data form the 1TB disk manually before or after removing it.

Cache has plenty of space, both the system and appdata shares exist on both cache and array, and there are some duplicate files, decide where you want them (set the appropriate use cache option) and move/delete the other ones, the domains share exists only on the array, I assume you want cache for that, so change it also.

Failed to initialize PAL happens on more recent boards with UEFI support when booting DOS, you'd need to boot UEFI and uses sas2flash.efi, what I usually do is use an older board (without UEFI) to do the flashing or any available Windows desktop.

That should work, just make sure disk5 is formatted with an fs supported by UD.

WD20/30/(40/60EFRX are CMR, WD20/30/40/60EFAX are SMR, but note that SMR disks usually work fine with Unraid.