January 20, 20233 yr So I got a pop up today of a CRC Error count, the count was a very low 2 I've had this drive in there for about a year with no issues. In the past I had an issue with another drive and it ended up being the SATA connector, but with the fact that this only showed 2 errors I am not sure if I should be worried or be doing something?? What do you guys think?? Got another error warning so I checked the log Quote ATA Error Count: 3 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 3 occurred at disk power-on lifetime: 12961 hours (540 days + 1 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 -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 00 20 79 df 40 00 11d+15:30:11.541 READ FPDMA QUEUED 60 40 48 c0 8d df 40 00 11d+15:30:11.539 READ FPDMA QUEUED 60 40 40 80 8b df 40 00 11d+15:30:11.539 READ FPDMA QUEUED 60 c0 38 c0 89 df 40 00 11d+15:30:11.539 READ FPDMA QUEUED 60 70 30 50 88 df 40 00 11d+15:30:11.539 READ FPDMA QUEUED Error 2 occurred at disk power-on lifetime: 12914 hours (538 days + 2 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 -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 18 b8 a5 f4 40 00 9d+16:48:54.839 READ FPDMA QUEUED 60 00 30 b8 a9 f4 40 00 9d+16:48:54.834 READ FPDMA QUEUED 60 a0 28 00 3e dc 40 00 9d+16:48:54.834 READ FPDMA QUEUED 60 00 20 b8 ad f4 40 00 9d+16:48:54.834 READ FPDMA QUEUED 60 00 10 b8 a1 f4 40 00 9d+16:48:54.834 READ FPDMA QUEUED Error 1 occurred at disk power-on lifetime: 12723 hours (530 days + 3 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 -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 10 f8 31 3e 40 00 1d+17:49:12.918 READ FPDMA QUEUED 60 00 08 28 4b 71 40 00 1d+17:49:12.917 READ FPDMA QUEUED 60 20 00 c8 8d 3e 40 00 1d+17:49:12.916 READ FPDMA QUEUED 60 08 20 60 ff 0d 40 00 1d+17:49:12.862 READ FPDMA QUEUED 60 88 18 70 28 3e 40 00 1d+17:49:12.862 READ FPDMA QUEUED Edited January 20, 20233 yr by SiRMarlon added info
June 12, 20242 yr I just logged onto my server today and was met with this error log and I am wondering what it means and if a new SATA cable on the drive could fix it: Quote ATA Error Count: 9 (device log contains only the most recent five errors) 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 9 occurred at disk power-on lifetime: 14877 hours (619 days + 21 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 40 88 48 ce 91 40 08 2d+11:03:30.261 READ FPDMA QUEUED 61 40 d8 58 c1 91 40 08 2d+11:03:30.258 WRITE FPDMA QUEUED 61 08 d0 50 c1 91 40 08 2d+11:03:30.258 WRITE FPDMA QUEUED 61 40 c8 10 bc 91 40 08 2d+11:03:30.254 WRITE FPDMA QUEUED 61 08 c0 08 bc 91 40 08 2d+11:03:30.253 WRITE FPDMA QUEUED Error 8 occurred at disk power-on lifetime: 14877 hours (619 days + 21 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 30 70 e8 66 88 40 08 2d+11:03:12.381 READ FPDMA QUEUED 60 28 c8 60 cf 90 40 08 2d+11:03:12.374 READ FPDMA QUEUED 60 f8 c0 68 e5 f7 40 08 2d+11:03:12.374 READ FPDMA QUEUED 61 f0 28 18 e0 f7 40 08 2d+11:03:12.365 WRITE FPDMA QUEUED 61 68 20 b0 df f7 40 08 2d+11:03:12.364 WRITE FPDMA QUEUED Error 7 occurred at disk power-on lifetime: 14877 hours (619 days + 21 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 10 c0 d0 95 fd 40 08 2d+11:03:06.548 READ FPDMA QUEUED 61 c0 58 60 8d fd 40 08 2d+11:03:06.547 WRITE FPDMA QUEUED 61 40 50 20 8d fd 40 08 2d+11:03:06.542 WRITE FPDMA QUEUED 60 a0 48 f8 de a7 40 08 2d+11:03:06.530 READ FPDMA QUEUED 60 e0 40 18 de a7 40 08 2d+11:03:06.529 READ FPDMA QUEUED Error 6 occurred at disk power-on lifetime: 14877 hours (619 days + 21 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 28 68 f8 dd 9f 40 08 2d+11:03:06.059 READ FPDMA QUEUED 60 10 70 f0 65 91 40 08 2d+11:03:06.058 READ FPDMA QUEUED 60 f8 60 f8 64 91 40 08 2d+11:03:06.058 READ FPDMA QUEUED 60 08 58 f0 61 91 40 08 2d+11:03:06.057 READ FPDMA QUEUED 60 28 38 98 75 36 40 08 2d+11:03:06.057 READ FPDMA QUEUED Error 5 occurred at disk power-on lifetime: 14875 hours (619 days + 19 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 40 08 40 a8 c2 40 08 2d+08:44:06.055 READ FPDMA QUEUED 60 40 00 00 a3 c2 40 08 2d+08:44:06.042 READ FPDMA QUEUED 60 40 f8 c0 9d c2 40 08 2d+08:44:06.042 READ FPDMA QUEUED 60 40 b8 80 98 c2 40 08 2d+08:44:06.042 READ FPDMA QUEUED 60 40 b0 40 93 c2 40 08 2d+08:44:06.042 READ FPDMA QUEUED WDC_WD101EFBX-68B0AN0_VHG5T4VM-20240611-1820.txt Edited June 12, 20242 yr by Darcy Bell
June 12, 20242 yr 5 hours ago, DarB said: a new SATA cable on the drive could fix it: It should, but note that it won't reset the current errors, but as long as they stop increasing it's resolved.
June 12, 20242 yr 6 hours ago, JorgeB said: It should, but note that it won't reset the current errors, but as long as they stop increasing it's resolved. Noted, I will change the cable. Sorry if this is a stupid question, but do I need to do anything to clear the current errors or do I just leave them?
June 12, 20242 yr The errors cannot be reset, but you can click the thumbs down on the dashboard to acknowledge them.
June 12, 20242 yr 6 hours ago, JorgeB said: The errors cannot be reset, but you can click the thumbs down on the dashboard to acknowledge them. Okay, gotcha. Thanks so much Edited June 12, 20242 yr by DarB
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.