May 2, 201511 yr 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
May 3, 201511 yr Author Can someone please check my log. If the parity is failing then I will replace it
May 3, 201511 yr 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.
May 3, 201511 yr 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?
May 4, 201511 yr Author Here is parity drive smart report. It looks ok to me I cannot figure out why the parity check speed is 9Mb/s which takes forever. smart_report_parity.txt
May 4, 201511 yr Author 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
May 4, 201511 yr ... 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.
May 5, 201511 yr Author I am running beta15 and it is still there. Parity check takes too long (4 days)
Archived
This topic is now archived and is closed to further replies.