LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 10-05-2019, 01:46 AM   #1
greentea11
LQ Newbie
 
Registered: Oct 2019
Distribution: Fedora 34 x86_64
Posts: 2

Rep: Reputation: Disabled
GSmartControl reported error logs of my harddrive


Hello, I want re-install Antix Linux GSmartControl reported some error on my harddrive. This is results

Code:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.146-antix.1-amd64-smp] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Travelstar Z5K500
Device Model:     HGST HTS545050A7E680
Serial Number:    RBF50FM535G6DR
LU WWN Device Id: 5 000cca 7a3ecc1b2
Firmware Version: GR2OA350
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Oct  5 13:34:17 2019 WIB
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(   45) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 108) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   088   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0025   198   100   040    Pre-fail  Offline      -       118
  3 Spin_Up_Time            0x0023   227   100   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0032   096   096   000    Old_age   Always       -       6880
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   147   100   040    Pre-fail  Offline      -       37
  9 Power_On_Hours          0x0032   063   063   000    Old_age   Always       -       16555
 10 Spin_Retry_Count        0x0033   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       3761
183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   090   000    Old_age   Always       -       16836271865996
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       249122062338
190 Airflow_Temperature_Cel 0x0022   062   052   045    Old_age   Always       -       38 (Min/Max 28/38)
191 G-Sense_Error_Rate      0x0032   098   098   000    Old_age   Always       -       671
192 Power-Off_Retract_Count 0x0032   098   098   000    Old_age   Always       -       36241961
193 Load_Cycle_Count        0x0032   028   028   000    Old_age   Always       -       722562
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       2
223 Load_Retry_Count        0x002a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 138 (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 138 occurred at disk power-on lifetime: 16517 hours (688 days + 5 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 41 08 18 9c 9f 09  Error: UNC at LBA = 0x099f9c18 = 161455128

  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 08 58 18 9c 9f 40 00      01:10:20.862  READ FPDMA QUEUED
  60 08 50 10 9c 9f 40 00      01:10:20.862  READ FPDMA QUEUED
  60 08 48 08 9c 9f 40 00      01:10:20.861  READ FPDMA QUEUED
  60 08 30 00 9c 9f 40 00      01:10:20.850  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:10:20.848  SET FEATURES [Enable SATA feature]

Error 137 occurred at disk power-on lifetime: 16517 hours (688 days + 5 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 41 e8 18 9c 9f 09  Error: UNC at LBA = 0x099f9c18 = 161455128

  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 00 9c 9f 40 00      01:10:17.495  READ FPDMA QUEUED
  60 00 f0 00 9a 9f 40 00      01:10:17.493  READ FPDMA QUEUED
  60 00 e8 00 98 9f 40 00      01:10:17.490  READ FPDMA QUEUED
  60 00 e0 00 96 9f 40 00      01:10:17.485  READ FPDMA QUEUED
  60 00 d8 00 94 9f 40 00      01:10:17.483  READ FPDMA QUEUED

Error 136 occurred at disk power-on lifetime: 16516 hours (688 days + 4 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 41 08 c0 fd 60 02  Error: UNC at LBA = 0x0260fdc0 = 39910848

  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 08 60 c0 fd 60 40 00      00:12:52.104  READ FPDMA QUEUED
  60 08 58 b8 fd 60 40 00      00:12:52.104  READ FPDMA QUEUED
  60 08 50 b0 fd 60 40 00      00:12:52.104  READ FPDMA QUEUED
  60 08 48 a8 fd 60 40 00      00:12:52.104  READ FPDMA QUEUED
  60 08 40 a0 fd 60 40 00      00:12:52.103  READ FPDMA QUEUED

Error 135 occurred at disk power-on lifetime: 16516 hours (688 days + 4 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 41 40 c0 fd 60 02  Error: UNC at LBA = 0x0260fdc0 = 39910848

  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 e8 00 fc 60 40 00      00:12:48.698  READ FPDMA QUEUED
  60 00 e0 00 fa 60 40 00      00:12:48.697  READ FPDMA QUEUED
  60 00 d8 00 f8 60 40 00      00:12:48.695  READ FPDMA QUEUED
  60 00 d0 00 f6 60 40 00      00:12:48.693  READ FPDMA QUEUED
  60 00 c8 00 f4 60 40 00      00:12:48.691  READ FPDMA QUEUED

Error 134 occurred at disk power-on lifetime: 15931 hours (663 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
  -- -- -- -- -- -- --
  40 41 80 80 71 57 01  Error: UNC at LBA = 0x01577180 = 22507904

  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 08 40 38 b9 1b 40 00      08:07:46.928  READ FPDMA QUEUED
  60 08 28 b8 ad 1b 40 00      08:07:46.928  READ FPDMA QUEUED
  60 08 f8 28 6c 04 40 00      08:07:46.928  READ FPDMA QUEUED
  60 08 f0 68 bc 1b 40 00      08:07:46.928  READ FPDMA QUEUED
  60 08 e8 c8 f0 10 40 00      08:07:46.927  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     15964         698326040
# 2  Extended offline    Completed: read failure       90%     15962         698326040
# 3  Short offline       Completed without error       00%      2013         -
# 4  Short offline       Completed without error       00%      1982         -
# 5  Short offline       Completed without error       00%      1864         -
# 6  Short offline       Completed without error       00%      1471         -
# 7  Short offline       Completed without error       00%      1366         -
# 8  Short offline       Completed without error       00%      1347         -
# 9  Short offline       Completed without error       00%       473         -
#10  Short offline       Completed without error       00%       455         -
#11  Short offline       Completed without error       00%       133         -
#12  Short offline       Completed without error       00%       123         -
#13  Short offline       Completed without error       00%       113         -
#14  Short offline       Completed without error       00%       104         -
#15  Short offline       Completed without error       00%        91         -
#16  Short offline       Completed without error       00%        81         -
#17  Short offline       Completed without error       00%         3         -
#18  Short offline       Completed without error       00%         3         -
#19  Short offline       Completed without error       00%         2         -
#20  Short offline       Completed without error       00%         2         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
What's that mean of the report? Can somebody explain to me what happened on my harddrive? Thanks
 
Old 10-15-2019, 09:50 AM   #2
beachboy2
Senior Member
 
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 22 MATE, Peppermint OS-Devuan, EndeavourOS
Posts: 4,312
Blog Entries: 48

Rep: Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590
greentea11,

Welcome to LQ forums.

I don’t think your drive is in poor health.
There has only been one Reallocated Event Count. It just means one sector on your drive failed at LBA 698326040 but the drive firmware acted to deactivate it and replace it with a spare sector.

Keep an eye on the Current Pending Sector which is currently zero (good news).
This is the number of bad sectors that the drive firmware hasn't yet dealt with.

These links may help:
https://ubuntuforums.org/showthread.php?t=2406078

https://serverfault.com/questions/10...n-a-linux-disk

https://www.smartmontools.org/wiki/BadBlockHowto
 
Old 10-17-2019, 03:13 AM   #3
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
Is there no program that can translate smartctl data into something humanely understandable?

I recently found log entries saying "Usage Attribute: 194 Temperature_Celsius changed from 110 to 105" - almost gave me a heart attack; but the last 2 numbers are not actually temepratures in degrees celsius!
 
Old 09-02-2021, 06:19 PM   #4
greentea11
LQ Newbie
 
Registered: Oct 2019
Distribution: Fedora 34 x86_64
Posts: 2

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by beachboy2 View Post
greentea11,

Welcome to LQ forums.

I don’t think your drive is in poor health.
There has only been one Reallocated Event Count. It just means one sector on your drive failed at LBA 698326040 but the drive firmware acted to deactivate it and replace it with a spare sector.

Keep an eye on the Current Pending Sector which is currently zero (good news).
This is the number of bad sectors that the drive firmware hasn't yet dealt with.

These links may help:
https://ubuntuforums.org/showthread.php?t=2406078

https://serverfault.com/questions/10...n-a-linux-disk

https://www.smartmontools.org/wiki/BadBlockHowto
Well, at last I'd change my hard drive because it's going bad on my old device.
GSmartcontrol has reported true about condition my hard drive have a serious problem.
Sorry I'm too late for reply this

Last edited by greentea11; 09-02-2021 at 06:20 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Does gsmartcontrol work on SSD? d.foxx Linux - Newbie 4 04-20-2017 07:02 AM
Gsmartcontrol bug in Mageia3 nigelc Mageia 10 07-28-2013 05:50 AM
LXer: Test your Hard Drives with GSmartControl! LXer Syndicated Linux News 0 08-10-2012 08:50 AM
LXer: GSmartControl - Useful Hard Disk Drive Health Inspection Tool For Linux LXer Syndicated Linux News 0 07-21-2010 02:40 PM
LXer: Check your disks' health with GSmartControl LXer Syndicated Linux News 0 10-25-2008 03:42 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:41 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration