trurl

Post them and setup syslog server.

Ideally no more than 4 drives per PSU cable. MOLEX-SATA power splitters are better than SATA-SATA power splitters. What is the exact model of your PSU?

Configuring it to be on the array won't move anything already on cache. But... Better if Docker/VM related shares - appdata, domains, system - are all on cache or other pool, so Docker/VM will perform better, and so array disks can spin down since these files are always open. Nothing can move open files so you will have to disable Docker and VM Manager in Settings before these can be moved.

Attach Diagnostics ZIP to your NEXT post in this thread.

Click the diagnostics link if you don't know what we mean.

Is it still plugged in to the controller? If not, plug it back in and post new diagnostics. It can be tested in place no need for a dock. Not seen any evidence there is anything wrong with the disk. If the disk is OK it would be simpler and better to just rebuild it.

Unrelated, your appdata and system shares are on the array, and configured to be moved to the array. Better if docker/VM related shares - appdata, domains, system - are on cache or other pool with nothing on the array, so docker/VM will perform better, and so array disks can spin down since these files are always open. Nothing can move open files, so you will have to disable Docker and VM Manager in Settings before these shares can be moved Assuming you mean MB/s, a little slow but not unexpected for writes to the array. Are you writing to a cached user share? Have you tried turbo (reconstruct write)? https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/overview/#array-write-modes

Do you have an attached monitor and keyboard?

Do you still have the original disk5? In what way did it "fail"? Connection problems are much more common than disk problems.

Attach Diagnostics ZIP to your NEXT post in this thread.

Why are you trying to move files from an emulated disk?

I should have said nearly empty. Filesystem overhead can make it seem like a drive has a lot of used space even it if is empty. Disk5 has a lot less used than many of your other disks so I thought perhaps it should have more. Diagnostics does show one user share with files on disk5 U--------S shareUseCache="yes" # Share exists on cache, disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk9

You mention Proxmox. Are you running Unraid as a VM?

Looks like disk5 was disabled, but I don't see disk5 in the SMART reports. Emulated disk5 is mounted but it appears to be empty. Is disk5 supposed to be empty?

Why didn't you ask for help on the forum?

Attach Diagnostics ZIP to your NEXT post in this thread.

At that point, the (emulated) disk contents should be accessible for reading (and even writing), assuming it is a mountable filesystem.

I have JMB585 in my backup server, no problems on any version

Start the array in normal (not maintenance) mode with nothing assigned as disk6 then post diagnostics

Attach Diagnostics ZIP to your NEXT post in this thread.

Just set umask to 000

lsblk shows some drives with multiple partitions. Were these taken from a Windows system without wiping the partitions?

In appdata for transmission, what do you have in settings.json for umask?

Check filesystem on (emulated) disk7.

No reason to expect read check to recover anything.