Kryspy Posted June 15, 2014 Share Posted June 15, 2014 Error 2 occurred at disk power-on lifetime: 10813 hours (450 days + 13 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 -- -- -- -- -- -- -- 04 51 01 00 00 00 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d5 01 e1 4f c2 00 08 07:07:06.801 SMART READ LOG b0 d5 01 e1 4f c2 00 08 07:07:06.800 SMART READ LOG b0 d6 01 e0 4f c2 00 08 07:07:06.800 SMART WRITE LOG b0 d6 01 e0 4f c2 00 08 07:07:06.798 SMART WRITE LOG b0 d5 01 e0 4f c2 00 08 07:07:06.798 SMART READ LOG Error 1 occurred at disk power-on lifetime: 10736 hours (447 days + 8 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 -- -- -- -- -- -- -- 04 51 01 00 00 00 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d5 01 e1 4f c2 00 08 02:25:08.316 SMART READ LOG b0 d5 01 e1 4f c2 00 08 02:25:08.315 SMART READ LOG b0 d6 01 e0 4f c2 00 08 02:25:08.315 SMART WRITE LOG b0 d6 01 e0 4f c2 00 08 02:25:08.314 SMART WRITE LOG b0 d5 01 e0 4f c2 00 08 02:25:08.313 SMART READ LOG Ideas??? I changed the SATA cable. Kryspy Quote Link to comment
SSD Posted June 15, 2014 Share Posted June 15, 2014 These two errors - whatever they are, occurred at 10736 and 10813 powered on hours. What at the current power of hours for the drive? Was that very recent? Perhaps you were trying to pull a smart report with the wrong parameters (e.g., "-d ata" on a SATA drive)? If not, search Google. I am not sure what they mean. Quote Link to comment
Kryspy Posted June 15, 2014 Author Share Posted June 15, 2014 Yeah they were within the last few days. I've changed slots on the Lian-Li case to see if it was a backplane problem; problem persists. Re-formatted, also still persists. Kryspy Quote Link to comment
SSD Posted June 15, 2014 Share Posted June 15, 2014 Once one of these shows up, it will never go away. It is permanently logged, unless you get more newer errors in which case it only remembers the details for a fixed number (5 I think). The way you tell if it is fixed is you don't see any more. What command do you use to pull smart reports? Is it possible you used some tool that may have passed bad arguments that could have triggered the drive to generate an error? 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.