July 8, 20242 yr I have an array of 9 SAS HHDs, 2 being parity drives. Both parity drives recently showed up as disabled with a red X but were reporting their temperature. I stopped the array, removed the two parity drives, added the parity drives back and started parity sync. It has now been 2 days stuck at 75% with zero movement, this job normally takes just over a day. During the rebuild disk 6 showed errors for the first time, reporting 11,672 errors and parity drive 1 showed 1024 errors for the first time also. My last SMART test data shows that all drives passed a recent SMART test. I can not run a test on parity drive 1 (the drive with 1024 errors) as it is listed disabled with a red X. I have tried to pause and then cancel the parity sync but nothing has happened. Looking for advice on what to do next, my next step is probably to do a reboot and try this again.
July 8, 20242 yr Author So I tried to restart the server but no dice, but I was able to shutdown. I did this after stopping docker. Upon boot I was able to stop the array, remove the 2 parity drives, clear both drives, add them back as parity drives and now the parity is rebuilding. So far I do not see any errors but will run extended SMART tests if and when this parity finishes. Both parity drives are invalid but neither are disabled, so looking better. Still 100% unsure what the cause is.
July 9, 20242 yr Author 19 hours ago, JorgeB said: If there are more errors post the diagnostics. See attached. It has been stuck at 39.6% for some time now. the-gibson-diagnostics-20240708-2118.zip
July 9, 20241 yr Community Expert There are read errors on disk6 and write errors with parity, so it got disabled. Jul 8 00:06:05 The-Gibson kernel: sd 1:0:2:0: Power-on or device reset occurred These type of errors usually mean a power/connection issue, check cables for those two disks, if they share a splitter that could also be the problem.
July 10, 20241 yr Author 18 hours ago, JorgeB said: There are read errors on disk6 and write errors with parity, so it got disabled. Jul 8 00:06:05 The-Gibson kernel: sd 1:0:2:0: Power-on or device reset occurred These type of errors usually mean a power/connection issue, check cables for those two disks, if they share a splitter that could also be the problem. I just unplugged all my drives and plugged them back in. One drive might have felt a little loose, the rest didn't. Thanks for assisting me with this issue, I will let you know in a day or two how things have progressed. Thanks!
July 17, 20241 yr Author On 7/9/2024 at 1:22 AM, JorgeB said: There are read errors on disk6 and write errors with parity, so it got disabled. Jul 8 00:06:05 The-Gibson kernel: sd 1:0:2:0: Power-on or device reset occurred These type of errors usually mean a power/connection issue, check cables for those two disks, if they share a splitter that could also be the problem. Not totally sure what the issue was but everything is fine now, I hope this isn't a regal event. I re-silvered parity drive 1 and added it to the pool and parity check was successful. I also ran short and extensive smart tests on all drives and none showed any errors. * On a separate note, if there any way to get rid of the drive under "Historical Unassigned Devices"? There have been a few entries during the process and selecting the red x removed them. This one is white and unselectable. Thanks
July 17, 20241 yr Community Expert 3 hours ago, lan said: if there any way to get rid of the drive under "Historical Unassigned Devices" Just click the x under "Remove"
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.