eetsumrobins Posted November 16, 2020 Share Posted November 16, 2020 So I've built up my first server in the last month or so, and for some reason every time I try and do a parity sync to build up my first parity disk, it always hangs at 12.5% (exactly 1 TB since it's an 8 TB parity drive). When the check starts I see read speeds around 130 MB/s and then it drops into the 60-85 MB/s range, until it completely stops all R/W activity at 12.5%. I also can't export diagnostics or save any changes to system settings from the GUI at this point. I captured two different syslog dumps today as examples. I've tried multiple drives, run memtest to make sure my RAM isn't causing issues, and at this point I'm not sure of the best way to move forward. Would appreciate any guidance. syslog1 syslog2 Quote Link to comment
ChatNoir Posted November 16, 2020 Share Posted November 16, 2020 Could you share your diagnostics in your next post ? (Tools / Diagnostics) There are more information than is the syslog. Quote Link to comment
trurl Posted November 16, 2020 Share Posted November 16, 2020 4 hours ago, eetsumrobins said: can't export diagnostics or save any changes to system settings from the GUI at this point Then get us Diagnostics before it gets to that point Quote Link to comment
eetsumrobins Posted November 16, 2020 Author Share Posted November 16, 2020 Wasn't sure if those would be useful without the issue presenting itself. Have attached here. rph-ur-diagnostics-20201116-1153.zip rph-ur-diagnostics-20201116-1153.zip Quote Link to comment
trurl Posted November 17, 2020 Share Posted November 17, 2020 Run an extended SMART test on parity Quote Link to comment
eetsumrobins Posted November 18, 2020 Author Share Posted November 18, 2020 Completed without any errors. Report attached. ST8000NM0055-1RM112_ZA1J2TLH-20201118-1139.txt Quote Link to comment
JorgeB Posted November 18, 2020 Share Posted November 18, 2020 It's always at 12.5%? Quote Link to comment
eetsumrobins Posted November 18, 2020 Author Share Posted November 18, 2020 Yep, every single time and I've tried two separate drives. It still think's it's running and I'm still able to navigate around the GUI, but there is zero disk activity and I can't save any changes I try to make. Quote Link to comment
JorgeB Posted November 18, 2020 Share Posted November 18, 2020 There have been a couple of similar cases, looks like a possible GUI problem, don't remember if we ever got to the bottom of it, did you try safe mode? Quote Link to comment
eetsumrobins Posted November 18, 2020 Author Share Posted November 18, 2020 Haven't tried safe mode yet, just rebooted and started a sync. Will report back. Quote Link to comment
eetsumrobins Posted November 18, 2020 Author Share Posted November 18, 2020 Same result. The only thing I can think of is that one of my drives started giving back some pending sector and uncorrectable errors in its SMART report. Would that cause parity sync to grind to a halt at the same place every time? I'm attaching the SMART report for that drive to this comment. WD_My_Book_25EE_574343374B355A565850414C-0_0-20201118-1602.txt Quote Link to comment
JorgeB Posted November 19, 2020 Share Posted November 19, 2020 That drive does appear to be failing but there should be some errors in the log if that's reason, please post syslog or diags. Quote Link to comment
eetsumrobins Posted November 19, 2020 Author Share Posted November 19, 2020 The syslogs and diags earlier in the thread included the failing disk. I'm currently transferring data off of that disk to remove it from the array and see if that solves the problem. Quote Link to comment
eetsumrobins Posted November 22, 2020 Author Share Posted November 22, 2020 So after removing the drive with errors and doing a new config, parity sync completed, so I guess the bad drive was just causing sync to totally freeze up once it got to a bad sector every time. 1 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.