So, is Error Log something we shouldn't worried about?

mangotree · 08-30-2012, 10:54 PM

Helo,

I just bought the second-hand SEAGATE external hard-drive and when I check with gsmartcontrol, I have the same problem with sk545, which is Error Log tab display in red.

Code:

 
SMART Error Log Version: 1
ATA Error Count: 10 (device log contains only the most recent five errors)

|
v

Error 10 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

|
v

Error 9 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

|
v

and so on

The other tabs of gsmartcontrol shows that everything is OK (overall health is pass, all attributes is never failed, and self-test logs{short & conveyance} is report completed without error). So, is Error Log something we shouldn't worried about?Then what is the meaning of that error log? Thank you

NB: oh, I just not try other tools yet to check the hard-drive. Should I?

segmentation_fault · 09-01-2012, 07:52 AM

Well, you haven't posted any log, so noone can tell you anything. It would be better if you posted the full output of

Code:

$ smartctl --all <your-hdd>

onebuck · 09-01-2012, 08:03 AM

@mangotree

Please do not hi-jack threads. When posting, please provide unedited log contents.

This thread was created by moving mangotree's hijacking post from Smartctl giving errors, is hard drive going bad?

Transposed portions of the log are not complete due to mangotree omission of content.

mangotree · 09-02-2012, 12:45 PM

First, to all LQ members and moderators,

I don't meant to hijack this thread

. I've been search the issue before then I found that my problem is exactly similar with sk545, so I thought I don't need to make a new thread. I apologize.

btw, here is my gsmartcontrol Error Log:

Code:

Complete error log:

SMART Error Log Version: 1
ATA Error Count: 10 (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 10 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 06 27 d4 05  Error: UNC at LBA = 0x05d42706 = 97789702

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 01 06 27 d4 45 00      00:00:16.636  READ DMA EXT
  25 00 01 05 27 d4 45 00      00:00:16.632  READ DMA EXT
  25 00 01 04 27 d4 45 00      00:00:16.631  READ DMA EXT
  25 00 01 03 27 d4 45 00      00:00:16.631  READ DMA EXT
  25 00 01 02 27 d4 45 00      00:00:16.631  READ DMA EXT

Error 9 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 06 27 d4 05  Error: UNC at LBA = 0x05d42706 = 97789702

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 7e 26 d4 45 00      00:00:13.914  READ VERIFY SECTOR(S) EXT
  42 00 00 7e 25 d4 45 00      00:00:13.836  READ VERIFY SECTOR(S) EXT
  42 00 00 7e 14 d4 45 00      00:00:13.804  READ VERIFY SECTOR(S) EXT
  42 00 00 7e 13 d4 45 00      00:00:13.700  READ VERIFY SECTOR(S) EXT
  ec 00 01 00 00 00 00 00      00:00:13.700  IDENTIFY DEVICE

Error 8 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 06 27 d4 05  Error: UNC at LBA = 0x05d42706 = 97789702

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 01 06 27 d4 45 00      00:00:35.711  READ DMA EXT
  25 00 01 05 27 d4 45 00      00:00:35.707  READ DMA EXT
  25 00 01 04 27 d4 45 00      00:00:35.707  READ DMA EXT
  25 00 01 03 27 d4 45 00      00:00:35.707  READ DMA EXT
  25 00 01 02 27 d4 45 00      00:00:35.707  READ DMA EXT

Error 7 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 06 27 d4 05  Error: UNC at LBA = 0x05d42706 = 97789702

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 00 7e 26 d4 45 00      00:00:32.990  READ VERIFY SECTOR(S) EXT
  42 00 00 7e 25 d4 45 00      00:00:32.912  READ VERIFY SECTOR(S) EXT
  42 00 00 7e 14 d4 45 00      00:00:32.880  READ VERIFY SECTOR(S) EXT
  42 00 00 7e 13 d4 45 00      00:00:32.870  READ VERIFY SECTOR(S) EXT
  ec 00 01 00 00 00 00 00      00:00:32.863  IDENTIFY DEVICE

Error 6 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 06 27 d4 05  Error: UNC at LBA = 0x05d42706 = 97789702

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 06 27 d4 e5 00      00:01:37.230  READ DMA EXT
  25 03 01 00 00 00 e0 00      00:01:36.763  READ DMA EXT
  25 03 01 00 00 00 e0 00      00:01:36.701  READ DMA EXT
  ef 03 44 01 00 00 e0 00      00:01:36.332  SET FEATURES [Set transfer mode]
  00 00 00 00 00 00 00 ff      00:01:36.326  NOP [Abort queued commands]

I just curious what is the meaning of zero in "power-on lifetime: 0 hours (0 days + 0 hours)".
This time I just don't have a time to perform extended long self-test. I'll post the result soon after the test is done.
Thanks a lot (again)

segmentation_fault · 09-02-2012, 02:04 PM

Again, you posted the time of the errors, not the SMART status of the disk. We need to check this part:

Code:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       841
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       44035522
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2926
 10 Spin_Retry_Count        0x0013   100   100   034    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       842
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   063   045   045    Old_age   Always   In_the_past 37 (Min/Max 16/55)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       206
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       833
193 Load_Cycle_Count        0x0022   001   001   000    Old_age   Always       -       200450
194 Temperature_Celsius     0x001a   037   055   000    Old_age   Always       -       37 (0 16 0 0 0)
195 Hardware_ECC_Recovered  0x0012   084   059   000    Old_age   Always       -       66285540
197 Current_Pending_Sector  0x0010   100   100   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x003e   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0000   200   200   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x0032   100   253   000    Old_age   Always       -       0
202 Data_Address_Mark_Errs  0x0000   100   253   000    Old_age   Offline      -       0

mangotree · 09-06-2012, 05:37 AM

Hello,

I think I forgot to re-explain that all attributes and parameter comes OK and my only concern here is in Error Log. Sorry I can't provide you with the text logs anymore because I'm not with my Linux box, but still have the Screenshots with me. Thanks.

segmentation_fault · 09-06-2012, 05:51 AM

Now we have something.

This report looks ok to me. Looks like you shouldn't worry more than taking your regular backups. SMART tools are available in any OS (in case you have wiped Linux from that box) so you should check the status from time to time.