JorgeB

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.

Likely won't make much (if any) difference but since surveillance drives are optimized for write intensive workloads I would probably use it as parity.

I have to go now, someone else should be able to help you if still needed, but I'll check back tomorrow.

It's showing as duplicate UUID, which suggest it didn't unmount successfully, reboot the server and all should be OK, then run the parity check.

NEVER format, did you unmount it from UD before starting the array? If not do that (and re-start the array), if yes post new diags.

OK, check contents and make sure data looks correct, look for any lost files/folders inside a lost+found folder, if everything looks good assign disk 3 to the array, all disks should still be new (blue icon), if yes check "parity is already valid" and start the array, then run a correcting parity check since a few sync errors are expected.

When attempting to mount again no need for read-only mode anymore.

On the console/terminal type: xfs_repair -v /dev/sde1 If it asks for -L use it: xfs_repair -vL /dev/sde1 When done try to mount it again.

That suggests it didn't mount, please post the diagnostics: Tools -> Diagnostics P.S. I'll be leaving for the day in a few minutes so if you can reply fast.

Yes, try that, also check/replace power cable, without full diags it's difficult to say more.

LSI 9200 (or Dell H200) is PCIe 2.0, LSI 9207 is PCIe 3.0

Tools -> Diagnostics

You can post the diags grabbed after or during a transfer, there might be some clues there.