March 10, 20233 yr Been using Unraid for a few years now and this is my first batch of parity errors. During my monthly non-corrected parity check I got 9 errors, I immediately repeated the non-corrected parity check and got the same 9 errors. I've looked and the diagnostics but honestly I don't know what I'm looking for and how to proceed. I'm hoping someone on here can give me some guidance. Thanks! bifrost-diagnostics-20230310-0944.zip
March 10, 20233 yr Community Expert Solution Mar 3 05:45:59 Bifrost emhttpd: unclean shutdown detected A few sync errors are normal, even expected, after this, just run a correcting check.
March 10, 20233 yr Author Okay, that's a relief. I'll mark this solved once the corrected parity is complete.
March 10, 20233 yr Author I added "1,200" raw read error rate and raw write error rate to my SMART attribute notifications per something I read on here. During my parity check I'm now getting read error rate warnings for (sdo). First rate was 327,693 and then 30 minutes later 3,473,409. I'm not entirely sure I know what that means but it doesn't seem good to be an order of magnitude higher 30 minutes later.
March 11, 20233 yr Author 6 hours ago, JT Marshall said: I’m thinking my disk1 (sdo) is in need of a replacement but maybe there is more I can do to try and correct its behavior? Okay, parity check completed and I assume corrected the 9 errors, but that disk1 (sdo) has me worried. I definitely think I should replace it. bifrost-diagnostics-20230311-1317.zip
March 12, 20233 yr Community Expert Raw read error rate is now at zero, there are some UNC @ LBA errors logged, but they are all sector 0, so could be bogus, if there's aren't any read errors during the next parity checks I wouldn't worry for now.
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.