You are not logged in.
- Topics: Active | Unanswered
#1 2017-08-29 01:13:49
- cfr
- Member
- From: Cymru
- Registered: 2011-11-27
- Posts: 7,132
Interpreting SMART reports & assessing status of drive
This month, I started seeing disk errors being reported by smartctl. I had non-zero numbers for both current pending sectors and offline uncorrectables, errors logged by both systemd's journal and SMART itself and some failed extended tests.
I assumed that the disk is dying, though I wasn't sure how fast. I started looking for a new laptop. (Not because a new hard drive requires a new laptop, but because I doubt it is worth buying a machine this age a new disk, especially since the case recently developed a crack.) I'm still working on this project.
I also thought that I would try to deal with the bad blocks by forcing reallocation, but have taken a while to get around to this. I just finally got around to reading the guide on the smartmontools wiki (https://www.smartmontools.org/wiki/BadBlockHowto) linked from the Arch wiki's coverage. However, SMART is now giving me zeros for current pending sectors and offline uncorrectables and the most recent extended test completed without error. So it seems that the disk finally managed to reallocate the bad block (possibly 2 - I'm not certain about this).
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.12.8-2-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus Thin
Device Model: ST320LT007-9ZV142
Serial Number: W0Q28DT3
LU WWN Device Id: 5 000c50 044c7204c
Firmware Version: 0004LVM1
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7242 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Tue Aug 29 00:36:18 2017 BST
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
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: ( 0) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 63) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x303b) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 090 034 Pre-fail Always - 164980576
3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 088 088 020 Old_age Always - 12438
5 Reallocated_Sector_Ct 0x0033 083 083 036 Pre-fail Always - 360
7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 311490823
9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 24023 (29 125 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 096 096 020 Old_age Always - 4935
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 086 086 000 Old_age Always - 14
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 7
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 053 041 045 Old_age Always In_the_past 47 (Min/Max 32/48 #38)
191 G-Sense_Error_Rate 0x0032 097 097 000 Old_age Always - 7278
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 0
193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 497808
194 Temperature_Celsius 0x0022 047 059 000 Old_age Always - 47 (0 13 0 0 0)
195 Hardware_ECC_Recovered 0x001a 048 031 000 Old_age Always - 164980576
196 Reallocated_Event_Count 0x000f 074 074 030 Pre-fail Always - 23187 (44982 0)
197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 099 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
250 Read_Error_Retry_Rate 0x0000 001 001 000 Old_age Offline - 235035
251 Unknown_Attribute 0x0000 100 001 000 Old_age Offline - 6413
252 Unknown_Attribute 0x0000 100 001 000 Old_age Offline - 0
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 14 (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 14 occurred at disk power-on lifetime: 23894 hours (995 days + 14 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 ff ff ff 4f 00 00:15:10.438 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:15:10.437 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:15:10.437 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:15:10.435 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:15:10.434 READ FPDMA QUEUED
Error 13 occurred at disk power-on lifetime: 23889 hours (995 days + 9 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 ff ff ff 4f 00 01:55:22.579 READ FPDMA QUEUED
61 00 08 60 ae 8b 43 00 01:55:22.579 WRITE FPDMA QUEUED
ef 90 03 00 00 00 a0 00 01:55:22.568 SET FEATURES [Disable SATA feature]
27 00 00 00 00 00 e0 00 01:55:22.568 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 01:55:22.565 IDENTIFY DEVICE
Error 12 occurred at disk power-on lifetime: 23889 hours (995 days + 9 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 ff ff ff 4f 00 01:55:17.620 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 01:55:13.968 FLUSH CACHE EXT
61 00 08 f0 28 96 43 00 01:55:13.968 WRITE FPDMA QUEUED
ea 00 00 00 00 00 a0 00 01:55:13.957 FLUSH CACHE EXT
61 00 08 e8 28 96 43 00 01:55:13.956 WRITE FPDMA QUEUED
Error 11 occurred at disk power-on lifetime: 23888 hours (995 days + 8 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 88 b3 e3 0a Error: UNC at LBA = 0x0ae3b388 = 182694792
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 18 b3 e3 4a 00 01:23:50.052 READ FPDMA QUEUED
60 00 88 60 b4 e3 4a 00 01:23:50.022 READ FPDMA QUEUED
60 00 20 00 a4 e3 4a 00 01:23:49.943 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 01:23:48.155 FLUSH CACHE EXT
61 00 08 d0 09 96 43 00 01:23:48.154 WRITE FPDMA QUEUED
Error 10 occurred at disk power-on lifetime: 23840 hours (993 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 08 ff ff ff 4f 00 02:46:10.944 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 02:46:10.940 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 02:46:10.934 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 02:46:10.892 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 02:46:10.873 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 without error 00% 24021 -
# 2 Short offline Completed without error 00% 24007 -
# 3 Conveyance offline Completed without error 00% 24006 -
# 4 Extended offline Completed without error 00% 23987 -
# 5 Short offline Completed without error 00% 23983 -
# 6 Short offline Completed without error 00% 23971 -
# 7 Short offline Completed without error 00% 23958 -
# 8 Conveyance offline Completed without error 00% 23957 -
# 9 Short offline Completed without error 00% 23944 -
#10 Short offline Completed without error 00% 23934 -
#11 Conveyance offline Completed without error 00% 23933 -
#12 Short offline Completed without error 00% 23923 -
#13 Short offline Completed without error 00% 23910 -
#14 Conveyance offline Completed without error 00% 23909 -
#15 Extended offline Interrupted (host reset) 80% 23889 -
#16 Extended offline Interrupted (host reset) 60% 23888 -
#17 Short offline Completed without error 00% 23887 -
#18 Short offline Completed without error 00% 23876 -
#19 Short offline Completed without error 00% 23866 -
#20 Short offline Completed without error 00% 23852 -
#21 Short offline Completed without error 00% 23841 -
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.Am I understanding what's happened correctly? How far can I trust this disk?
The vast majority of the data is backed up weekly-ish to an external disk. Critical data which changes frequently is under subversion. The svn repository is on the disk, so no backup there, but the database is backed up by SpiderOak to the cloud (along with some other stuff) and an encrypted dump is also copied to dropbox (when dropbox works, which I don't count on ever). I say this because it will certainly be bad if the drive suddenly fails completely, but it shouldn't be catastrophic. (The worst aspect would probably not be data loss - though I might lose something I've overlooked somewhere or something not yet committed to svn - but more that I would then be without a working laptop.)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
#2 2017-08-29 09:05:33
- R00KIE
- Forum Fellow
- From: Between a computer and a chair
- Registered: 2008-09-14
- Posts: 4,734
Re: Interpreting SMART reports & assessing status of drive
I would not trust that disk, you already have a good number of actual reallocated sectors and from what you say it seems sectors that can't be read back are showing up(1), it looks like a ticking time bomb, I suspect once it starts to go it will go bad fast.
(1) The unreadable sectors might not have been reallocated, if you wrote data over the unreadable sectors they might have become readable again. The sectors might have become unreadable because the disk was disturbed during the last write for example, and writing them again "fixed" the problem. I've seen this happen with a couple of disks, I suspect the cause was I was using the disk on a moving train, so overwriting the sectors solved the problem and the disks still seem to work fine today. However this depends on who you ask, some people are adamant that once you get pending or offline uncorrectable sectors the disk should not be trusted anymore and replaced.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline