February 16, 20233 yr I've been having crazy performance issues for the past few days. I've tested direct drive performance and disk speeds seem fine, but anything within the shares has been crazy slow. If I attempt to copy a file to the server, or initiate a copy from within unraid, it never surpasses 20 MB/S, slowing down to a crawl and sometimes staying at 0MB/S for several seconds. I tried running without the parity and speeds improved slightly, as expected, but didn't resolve the issue. I'm currently running a parity-sync and its running at about 1-5 MB/s. It almost feels like the entire system is bottlenecking at 20MB/S across the system. Out of ideas, welcome to any suggestions! zero-server-diagnostics-20230216-0115.zip
February 16, 20233 yr Community Expert Wait for the parity sync to finish then start suing the array, performance will be terrible during a parity sync.
February 16, 20233 yr Community Expert Your parity drive is SMR, so parity builds may become atrociously slow. Best way to go about it in this configuration is probably to stop the array, leave the drives powered and idle for a few hours so it can do its internal reorganization, then start it again in maintenance mode so that nothing else accesses the array and start the parity build there. Hopefully this is a "good" SMR drive that recognises sequential accesses and bypasses cache and parity build will go at normal speeds.
February 16, 20233 yr Community Expert 11 minutes ago, Kilrah said: Your parity drive is SMR Yeah, that won't help, wait for the sync to finish and retest, some SMR drives performance decently with large files, if performance remains bad use CMR, at least for parity.
February 16, 20233 yr Author 38 minutes ago, Kilrah said: Your parity drive is SMR, so parity builds may become atrociously slow. Best way to go about it in this configuration is probably to stop the array, leave the drives powered and idle for a few hours so it can do its internal reorganization, then start it again in maintenance mode so that nothing else accesses the array and start the parity build there. Hopefully this is a "good" SMR drive that recognises sequential accesses and bypasses cache and parity build will go at normal speeds. Oddly enough previous parity operation would run at 100m+, so maybe its just worse due to it being filled? Is there an easy way to swap a data drive and a parity drive?
February 16, 20233 yr Community Expert 1 hour ago, zeroframes said: Oddly enough previous parity operation would run at 100m+, so maybe its just worse due to it being filled? Depends a lot on access patterns, could be that you tried to do something else at the same time that threw it into the "bogged down" state...
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.