Dub Posted January 6, 2022 Share Posted January 6, 2022 I find lots of suggestions on how to resolve a parity situation when you have one parity drive, but no specifics when you have more than one. I'm unsure if anything is different about the process. I recently had one of my two parity drives fail and I'm apprehensive about doing much of anything without a little guidance. Here is what SMART is throwing: ATA Error Count: 2 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 2 occurred at disk power-on lifetime: 10463 hours (435 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 b8 96 01 0e Error: WP at LBA = 0x0e0196b8 = 234985144 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 ff ff ff 4f 00 19d+01:46:18.556 WRITE FPDMA QUEUED 61 00 00 ff ff ff 4f 00 19d+01:46:18.509 WRITE FPDMA QUEUED 60 00 c8 ff ff ff 4f 00 19d+01:46:18.508 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 19d+01:46:18.508 READ FPDMA QUEUED 60 00 e8 ff ff ff 4f 00 19d+01:46:18.506 READ FPDMA QUEUED Error 1 occurred at disk power-on lifetime: 10463 hours (435 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 95 01 0e Error: UNC at LBA = 0x0e019578 = 234984824 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 f8 ff ff ff 4f 00 19d+01:46:14.191 READ FPDMA QUEUED 61 00 10 ff ff ff 4f 00 19d+01:46:14.189 WRITE FPDMA QUEUED 60 00 08 ff ff ff 4f 00 19d+01:46:14.189 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 19d+01:46:14.187 READ FPDMA QUEUED 60 00 10 ff ff ff 4f 00 19d+01:46:14.181 READ FPDMA QUEUED Any suggestions would be most appreciated! Quote Link to comment
ChatNoir Posted January 6, 2022 Share Posted January 6, 2022 Please attach your diagnostics to your next post. Quote Link to comment
Dub Posted January 6, 2022 Author Share Posted January 6, 2022 1 hour ago, ChatNoir said: Please attach your diagnostics to your next post. Apologies, I didn't realize the entire diagnostics would be necessary. diagnostics-20220106-0327.zip Quote Link to comment
JorgeB Posted January 6, 2022 Share Posted January 6, 2022 4 hours ago, Dub said: I find lots of suggestions on how to resolve a parity situation when you have one parity drive, but no specifics when you have more than one. It's the same, just replace that parity disk and start the array to re-sync parity. 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.