Can anyone shed a bit of light from their experience as to how long a parity check should take?

 

I had a power cut on Saturday evening - when the power was restored, I fired up my server and it started the corrective parity check. This was approximately 10pm Saturday night. It seemed to be moving along nicely at about 30MB/s but by Sunday morning, at about 7am it had reached 31% and was showing a speed of 1.9MB/s.  By this morning, it had reached 42% - so that is about 36 hours to get 42% though the parity check.  No errors have been listed so far.

 

Currently running UnRAID Pro 5 rc12a

 

Parity Drive is a 3Tb WD Red

The array consists of 2No3Tb; 4No2Tb; 1No1.5Tb; 4No1Tb and 2No320Gb.

 

The parity drive is in an icydock enclosure, which is connected back to one of the main SATA 2 ports on the mobo.

I would think that anything less than 30MB/s indicates a problem and ranges along the lines of 50-100+ MB/s are typical.

 

It is probably worth attaching a syslog so we can see if you are getting errors reported.

Thanks for the input - I would have thought that the speeds are too low, but I cannot see the problem - just wanted the experience of someone else to guide me...

 

I'm quite new to UnRAID, having built the server the other month and all has been progressing well with it - I have no plugins installed at all and haven't even added my cache drive as yet...When the parity check finished - I will post a syslog

Thanks for the input - I would have thought that the speeds are too low, but I cannot see the problem - just wanted the experience of someone else to guide me...

 

I'm quite new to UnRAID, having built the server the other month and all has been progressing well with it - I have no plugins installed at all and haven't even added my cache drive as yet...When the parity check finished - I will post a syslog

 

Are you leaving the website interface open (or active)?  You might try closing it and only occasionally starting it to check for a few seconds on the progress.  I seem to recall that either one or both (Simple features and/or the stock) web interfaces had issues with slowing down the parity check in some of the earlier rc releases. 

 

You do realize that the current rc release is rc16c and it is about to become ver 5.0.  You might want to update and see if the problem is present in the latest rc. 

Thanks for the advice - I have left the web interface open for about 12 hours but also closed it for 12 hours to see what the difference was - nothing in my case!

 

I do realise the latest RC is 16a, to be honest, it has taken me weeks to get all my drives cleared and set up and the data all copied to the array (it is primarily media storage) so I am just finalising the metadata for films etc before I add the cache drive and then I was going to update the OS to the latest rc...

Would it be of benefit to stop the parity check, update the OS to 16a and then try again?

Would it be of benefit to stop the parity check, update the OS to 16a and then try again?

 

Possibly, I seem to recall that slow parity checks were a big, big issue a few rc's back.  I also seem to remember that  some motherboards had issues-- and  some issues  was associated with having more than 4096GB of RAM installed.  ( If I am not directly effected by an issue, I often have problems remembering the exact details...      )

 

Another thought. Are you running any add-ins that might be writing to the disks while you are running the check? 

After thinking about it again, if the above post of another process writing to the disk is not a possibility, I would definitely stop the parity check and update to rc16c.  If the problem is not fixed, there may some unresolved issue in rc16! 

I have absolutely no plugins installed at all - I am intending to, but haven't got all my data where I want it yet, so haven't installed any yet. Will upgrade to 16c when I get home tonight and see if that makes a difference...

As an update - I upgraded to 16c last night, rebooted and started a new parity check. As of this morning (after the check had been running approximately 10 hours, it was at 48% and no errors found. So this is a huge improvement so far. Will provide an update when it is completed!

As a further update - when I got home yesterday evening - the parity check had completed with no errors found...seems like upgrading to 16c sorted the issue.

 

Thanks everyone for your help!