November 3, 20214 yr Hi guys! I was setting up a new Unraid but this time I went from ZFS zu the "normal" Unraid setup and now my problem: The smb transfer speed is sloooooooooooooooooow really sloooooooooow in avg 15 MB/s?! Is there anyway to fix that? I mean the drives should make at least 80 MB/s It's the same Hardware and same Unraid I only removed the ZFS pool and created a Unraid-Array. If I switch back to the ZFS pool I have around 350MB/s. I know that the ZFS pool is faster thanks to its "traditional" raid setup and Unraid is as slow as the HDD but 15 MB/s? Can someone help? Edited November 4, 20241 yr by PyCoder solved
November 3, 20214 yr Community Expert Are you using a cache drive for the array? Writes directly to the array are much slower than reads. Second (and major) factor is the file sizes being transferred. Writing directly to array is very slow because of file creation overhead, and the extra reads and writes necessary to keep parity updated on a real time basis. There are also two methods to (Settings >>> Disk Settings > 'Tunable (md_write_method):') Using the "reconstruct write" is faster but it will spin up all of the disks in the array as opposed to the parity disk(s) and one data disk. It looks like you are doing an initial data load of a new server setup. If you have a good backup of all the data you are transferring, you could unassign the parity disk-- leaving the aray unprotected. But that would at least double the transfer speed. (When you assigned the parity disk after the data is loaded, a parity build will be required.) One more observation. Small capacity drives have slower speeds than large capacity drives because of the higher data density of the large capacity drives. Edited November 3, 20214 yr by Frank1940
November 3, 20214 yr Author 17 minutes ago, Frank1940 said: Are you using a cache drive for the array? Writes directly to the array are much slower than reads. Second (and major) factor is the file sizes being transferred. Writing directly to array is very slow because of file creation overhead, and the extra reads and writes necessary to keep parity updated on a real time basis. There are also two methods to (Settings >>> Disk Settings > 'Tunable (md_write_method):') Using the "reconstruct write" is faster but it will spin up all of the disks in the array as opposed to the parity disk(s) and one data disk. It looks like you are doing an initial data load of a new server setup. If you have a good backup of all the data you are transferring, you could unassign the parity disk-- leaving the aray unprotected. But that would at least double the transfer speed. (When you assigned the parity disk after the data is loaded, a parity build will be required.) One more observation. Small capacity drives have slower speeds than large capacity drives because of the higher data density of the large capacity drives. Hi, No I dont use any cache drives and i tested md_write_method without any success. I know that the array is slow as slow as the HDD but 15 MB/s? Even when i copy a file from my PC to my Laptop i have at least 50MB/s soooooooo something must be off. And this is now with ZFS. Yes is stripped and faster but 15 MB/s isn't normal.
November 3, 20214 yr Community Expert I looked at your screenshot and the server had been up for 33 minutes. You were copying 504Gb of data. Start that transfer again, put the Windows Explorer transfer screen on top, walk away from the computer and just let it complete. Come back every fifteen minutes and just look at the progress. Touch nothing but the screen with your eyes. IF you need something to do while waiting, you can read this post on the Laptop (the computer not doing the transfer..): https://forums.unraid.net/topic/50397-turbo-write/
November 4, 20214 yr Author I played around with scheduler and md_write_method. Btw if all the disks have to spin then I can just stick to ZFS. 115 MB/s Problem solved Edited November 4, 20214 yr by PyCoder
November 7, 20214 yr On 11/4/2021 at 5:25 AM, PyCoder said: I played around with scheduler and md_write_method. Btw if all the disks have to spin then I can just stick to ZFS. 115 MB/s Problem solved This is where a cache disk will be helpful. Large capacity SSD or ideally NVME used as a write cache will speed up your writes as fast as your network and sending disks can handle.
November 3, 20241 yr Hi, I also had this problem (main problem was slow SMB transfer to my Unraid server (stuck at around 25-30 MB/sec)) and it seems to be finally fixed. My Hardware is not the problem at all (Ryzen 9 / actual Ryzen 7, NVMEs, etc). I have 2.5GBit NICs and also some 2.5GBit Switches (Aliexpress). Tried a lot and it's fixed now. I think changing MTU to 9000 on the Unraid Server + Clients fixed it finally, but here a list of what I did: -------------------------------------------------------------------------------- https://www.youtube.com/watch?v=t6MZGboDMZs&t=9s --> all of suggested tweaks -------------------------------------------------------------------------------- SMB Performance Tuning -------------------------------------------------------------------------------- Permit exclusive Shares --> Yes MTU 9000 (Unraid) + Windows clients --------------------------------------------------------------------------------
November 4, 20241 yr Author Solution Ty for the respond, but I switched like 2 years ago to TrueNAS Scale, so its solver as the titles says.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.