rykr Posted February 9, 2020 Share Posted February 9, 2020 My parity check has been running for 12 hours on a 11TB array with single parity. I hear that is somewhat normal. However it indicates that it is finding 760244 errors. That sounds bad. Does indicate a serious problem? Quote Link to comment
trurl Posted February 9, 2020 Share Posted February 9, 2020 The only acceptable number of parity errors is exactly zero. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Quote Link to comment
PeteAsking Posted February 9, 2020 Share Posted February 9, 2020 Yes it indicates a problem. You are not allowed to ignore it. Quote Link to comment
trurl Posted February 9, 2020 Share Posted February 9, 2020 If you are waiting for it to complete don't waste your time. Just get us the diagnostics. Quote Link to comment
rykr Posted February 9, 2020 Author Share Posted February 9, 2020 it completed some time in the night and I had likely erroneously set the parity check to daily (not really realizing it was such a lengthy process). So it's now running again. Anyway to stop it since it says it will run for another 19 hours. Btw, here are the digs I just pulled. vault-diagnostics-20200209-0746.zip Quote Link to comment
rykr Posted February 9, 2020 Author Share Posted February 9, 2020 The syslog seems to have quite a lot of exceptions and lines like failed command: READ FPDMA QUEUED related to an HGST drive I have. I'm checking that now since this could be my problem. From my reading this could be (a) a bad sata cable, (b) a sata cable not plugged in snugly, (c) a bad power supply, or (d) a bad drive. Smart report says drive is not bad. From my reading online this is unlikely to damage the drive but can damage the filesystem (which would cause havoc with the parity check) 1 Quote Link to comment
trurl Posted February 9, 2020 Share Posted February 9, 2020 8 minutes ago, rykr said: From my reading online this is unlikely to damage the drive but can damage the filesystem (which would cause havoc with the parity check) Parity doesn't know or care about filesystem. But it could corrupt your data. 24 minutes ago, rykr said: I had likely erroneously set the parity check to daily (not really realizing it was such a lengthy process) Most of us only check parity monthly. It is just a check. Parity is maintained all the time whether you check it or not. 25 minutes ago, rykr said: Anyway to stop it Did you figure out how to stop it? There should be a button in Main - Array Operations for that. 12 minutes ago, rykr said: From my reading this could be (a) a bad sata cable, (b) a sata cable not plugged in snugly, (c) a bad power supply, or (d) a bad drive. SMART for all disks looks fine. Check all connections, power and SATA, both ends, including any power splitters. Quote Link to comment
rykr Posted February 9, 2020 Author Share Posted February 9, 2020 changed schedule to monthly. sounds good. Yes, managed to cancel parity check. It's an old i7 860 chip with 5 internal SATA drives and 2 external USB drives. 620 watt Seasonic PS so capacity *should* be ok . I'll power it down in a minute and check all sata connectors and replace the one going to that one drive just to see if it's the cable. Quote Link to comment
itimpi Posted February 9, 2020 Share Posted February 9, 2020 2 hours ago, rykr said: changed schedule to monthly. sounds good. You might want to look at the Parity Check Tuning plugin so that the monthly check runs in increments outside prime time to minimise the disruption to users. Quote Link to comment
Recommended Posts
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.