Long story short, I'm at the moment copying everything from my array to another harddrive which I'll store elsewhere after which I'll fix my failed drive.

 

All harddrives are capable of read and write speeds in excess of 185MB/s but still the transferspeed is 'stuck' at around 80MB/s.

 

All hard drives are directly connected in the server via SATA so that shouldn't be an issue. Docker and VM services are disabled to prevent anything else on the server from read/writing data to/from the array.

 

The command I'm using for the transfer I saved it as a user script (copy shares) and is running in the background:

 

rsync -ah --info=progress2 --stats /mnt/user/{Backups,Cursus,data,DCIM,isos,roms,software,temp_vm,VMstorage} /mnt/disks/WR501C57/ &> /mnt/user/Cache_ssd/rsynclog_20231230.txt

 

Could someone explain/figure out what the bottleneck is here and maybe hoe this could be solved? System diagnostics are included. Thanks in advance.

 

PS. It's my first time posting something here so if I did something wrong, please guide me.

klaroen-diagnostics-20231231-1151.zip

Edited December 31, 20232 yr by Zero Cool
Typo

Nothing obvious, are these mostly large files? Also, at the moment the diags were saved it was copying from disk3, is it the same when copying from a different disk?

It's mostly mediafiles (between 300MB and 1,5GB in size). And I got the same speed when copying from disk1 and from (emulated) disk2.

 

I've included a screenshot to go with it.

Try the same rsync command but using /mnt/disk1 (or disk3) has source instead of /mnt/user, it will only copy files from that disk, it's just to see if it has to do with FUSE.

Sorry for the late reply. Happy New Year by the way! 🙂

 

I did some tests with /mnt/disk1 and /mnt/disk3 (and even /mnt/disk2). The transfer rates did go up to round 100MB/s (thus being higher than 80MB/s) but no where near the 'minimum' transfer rates of what my disks are capable of.

 

For comparison, I’m currently rebuilding disk2 and these are the speeds I’m getting so it can’t be a hard drive issue. Or am I missing something and comparing apples and oranges?

 

 

Edited January 2, 20242 yr by Zero Cool
Typo

If you are writing to a drive in the parity protected array then you will get nowhere near the raw write speed of drives.   To understand why read this section of the online documentation.