tuxbass Posted April 6 Share Posted April 6 (edited) For a couple of weeks parity drive was getting UDMA CRC Error Count notifications which generally is harmless and potentially related to bad power and/or data connection. My cache drive (SSD) has been racking up those for a few years now with no problem. Now however parity is disabled with syslog full of read&write errors with parity being disabled. Is there still a chance this is a bad connection, or time for a drive change? Bit odd how quickly I'm going through WD Reds though. srvr-diagnostics-20240405-1141.zip Edited April 6 by tuxbass Quote Link to comment
JorgeB Posted April 7 Share Posted April 7 Looks more like a SATA cable problem, but the disk dropped offline so there's no SMART, replace the cable and post new diags. Quote Link to comment
mauriceatkinson@btconnect. Posted April 9 Share Posted April 9 I have the same issue with the parity disk being disabled. I swopped this out for a new drive and all worked for a few weeks and now the new replacement drive is showing as disabled. I have looked at the diagnostic data for the failed drive but I am at a loss as to the probelm. I have attached the diagnostic zip file and would appreciate any direction as to what is causing the issue. cheers Maurice freedom-diagnostics-20240409-2016.zip Quote Link to comment
Solution JorgeB Posted April 10 Solution Share Posted April 10 It's not logged as a disk problem and SMART looks fine, so most like a power/connection issue, replace both power and SATA cable and try again. 1 Quote Link to comment
tuxbass Posted April 22 Author Share Posted April 22 On 4/7/2024 at 9:53 AM, JorgeB said: Looks more like a SATA cable problem, but the disk dropped offline so there's no SMART, replace the cable and post new diags. Been swapping power & data cables between the drives (including SATA ports on mobo side), and absolutely nothing has changed. Although I'm not seeing I/O errors for the drive in the syslog anymore. Also done an extended SMART test for the drive with no problems surfaced. Just some idiopathic failure? srvr-diagnostics-20240422-1003.zip Quote Link to comment
JorgeB Posted April 22 Share Posted April 22 49 minutes ago, tuxbass said: Been swapping power & data cables between the drives (including SATA ports on mobo side), and absolutely nothing has changed. If you mean the disk remaining disabled that is expected, SMART looks OK, re-sync parity. Quote Link to comment
tuxbass Posted April 22 Author Share Posted April 22 (edited) Ah, didn't realize. Is this the way to re-sync the parity? Quote unassigning the parity drive, then starting and stopping the array (that makes it forget the current assignment), then reassign the parity drive and restart the array Edited April 22 by tuxbass Quote Link to comment
JorgeB Posted April 22 Share Posted April 22 37 minutes ago, tuxbass said: Is this the way to re-sync the parity? Yep. 1 Quote Link to comment
tuxbass Posted April 23 Author Share Posted April 23 Thanks JorgeB, that was it. So looks like cable connectivity caused drive to be disabled, but to re-enable, it requires explicit action from the user. Quote Link to comment
JorgeB Posted April 23 Share Posted April 23 Correct, once a disk gets disabled, and it doesn't matter what caused it, it will never be re-enabled automatically. 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.