January 25, 20251 yr Hi all, I am fairly new to using parity and I am building it for the first time. I would just like to know what to expect speed wise. When I started the parity sync last night it was running at the advertised 280mbs and now I wake up this morning and I see it running at 170mbs and now a little bit later it is in the 150mbs'. I paused the parity sync and did short SMART self-tests on all drives and they all (1x 18tb exos 18(parity drive), 2x 16tb exos 16) came back without errors. Temps have all been below 45c. Is this slowdown to be expected as the parity sync grows closer to completion? Could it be a disk fragmentation issue? If so would it be worth solving before completing the parity sync or should I wait for it to finish and solve it after? Thanks in advance! resolute-diagnostics-20250125-1056.zip
January 25, 20251 yr Community Expert Solution It is normal for parity checks (and other array level operations) to slow down over time as the heads move towards the inner tracks (which hold less sectors per track).
January 25, 20251 yr Author Thanks! This gives me some peace of mind. I will just let it finish building parity then.
January 25, 20251 yr Community Expert 31 minutes ago, jeroenvandenhoogen said: short SMART self-tests on all drives and they all (1x 18tb exos 18(parity drive), 2x 16tb exos 16) came back without errors It is worth pointing out that passing a short SMART test is not a good indication of a drives health (although failing is. However running the extended test (which is a good indication) would take a long time at around 1.5-2 hours per TB on such large drives so I can see you not wanting to do it without cause..
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.