Looks good. I would consider migrating from reiserfs once you get parity rebuilt.

So the option I had was a Read Check. Not sure I've heard of that and I don't see that specific terminology here: https://lime-technology.com/wiki/index.php/Parity

 

Am I doing the right thing? I had parity checks automated on Sunday nights but it seems like I remember it says "Parity Check started" not "Read Check Started" like it does now. Also, that Disk4 has 1739 read errors so far. But it appears to have stopped.

Unassign parity, start the array, stop the array, re-assign parity to begin the sync, there could be read errors on disk4 due to the pending sectors, but let it finish if possible.

Edited May 5, 20179 yr by johnnie.black

2 days and 16 hours into the parity write\data rebuild. Drive 4 gave 1738 read errors right off the bat but that was it and I continued to see reads with no errors since then. It's estimated to take another half a day to be done. 

 

So how are those read errors going to hurt me in this process?

2 minutes ago, pinion said:

2 days and 16 hours into the parity write\data rebuild

 

That's a long time for such a small array, I'm guessing you're using USB2 for the external disk.

 

The errors are expected, when this finishes I would rebuild disk4 to a new disk, some file(s) will be corrupt because of the read errors, and then try to copy all files from the old disk, there will be some file(s) you can't copy, those would be the files that are corrupt on the rebuild, so you would now know which files are corrupt and replace them if available.

Nope, I have it plugged in via data to the mother board. Parity syncs normally took 10-12 hours before. Can't remember the last time I did a parity write. 

Post current diags.

Currently Disk 7 is the only one being read from. Everything else has been spun down since last night.

tower-diagnostics-20170508-1137.zip

Definitely too slow, it's writing parity at about 9MB/s, but don't see anything else wrong, let it finish.

If there is a problem with my parity drive should I try a parity read right after this? Or continue with removing Disk4 and replacing it?

If the speed was constantly like this doubt it's disk related, I remember some unusual cases where a parity sync was much slower than a check or a rebuild, try the rebuild to see if speed is better.

It's slowed to 640 KBps and that seems absurdly slow with 2.5% to go. Is it worth creating a new support thread to ask about this issue?

tower-diagnostics-20170509-0943.zip

Still don't see nothing in the logs that would explain this, how long does it estimate to finish?

It's sped up now to about 6 MBps and saying 3 hours. Before it was estimating another day. 

If it's another few hours I'd wait for it to finish, then see if the rebuild is faster, if it's the same it's probably issues with the parity disk.