Parity check slow but just on one tower


Recommended Posts

I have 4 towers and they did their parity checks on the first of the month.

 

The 3 towers ran just fine with no errors but one tower is very slow at doing the parity check (9Mb/s). It said it is going to take 3 days to complete.

 

I am using Unraid 6.0-beta15

 

Please help

 

Syslog attached

syslog.zip

Link to comment

Here is a smart report for the parity drive

 

SMART report was for Disk 11, a WD15EARS, serial ending in 2484.  It looks good, except for a very high CRC count, which means drive has or had a very bad SATA cable.  Current syslog shows no drive errors now though, so probably was in the past.

Link to comment

I have 4 towers and they did their parity checks on the first of the month.

 

The 3 towers ran just fine with no errors but one tower is very slow at doing the parity check (9Mb/s). It said it is going to take 3 days to complete.

 

I am using Unraid 6.0-beta15

 

Please help

 

Syslog attached

 

Unfortunately, there does not appear to be anything wrong with the array, according to this syslog.  You started a parity check at midnight, and 22 hours later, you stopped it, without any issues reported at all here.  In fact, the only problem I see in the syslog is the email system not working, which is minor and unrelated.  I'm sorry I was not able to help.

 

Can you provide another SMART report, for the parity drive?

Link to comment

I've encountered similar problem. Running "top" reveals the reason.

 

Very interesting... I really hope this gets fixed.

I have noticed that this tower was even slower than the others in Unraid 5

 

I really do not want to replace the motherboard. The motherboard I am using is:

 

Gigabyte Technology Co., Ltd. - GA-MA785G-UD3H

 

 

Link to comment

...

I really do not want to replace the motherboard.

...

Same here. I was planning to run Dockers with this mobo (Supermicro H8DME-2) but with this bug (if it is a bug) running Dockers is out of question. I was busy lately, but going to eventually find some time and test the unRAID 6.0-beta15, it sports, it seems, latest version of the kernel. The unRAID versions 5.05, 6.0-beta2, 6.0-beta14b I did test - they all have the bug.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.