Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Interpreting SMART report

Need help with peripherals or devices?
Post Reply
Message
Author
gpw928
Posts: 3
Joined: 2019-03-31 21:56

Interpreting SMART report

#1 Post by gpw928 »

Hi,

Even though the SMART overall-health self-assessment repeatedly gets a "PASSED", the SMART daemon keeps on reporting sdd as a problem.

There's also a lot of these in the daemon.log

Code: Select all

Aug  5 10:49:58 orac smartd[1356]: Device: /dev/sdd [SAT], 1 Currently unreadable (pending) sectors
I can read the entire sdd drive with dd and finish with an exit status of zero:

Code: Select all

[orac.751] # dd if=/dev/sdd bs=10240k of=/dev/null
95386+1 records in
95386+1 records out
1000204886016 bytes (1.0 TB, 932 GiB) copied, 8685.34 s, 115 MB/s
[orac.788] # echo $?
0
The only significant difference between sdd (SMART complains constantly) and its mirror, sdc (no problems), is the value of ID# 197.

Hoping somebody familiar with SMART diagnostics can tell me how significant ID# 197 is. Can it be reset? Why does it persist? Why are "unreadable sectors" not fatal? Why doesn't bad block forwarding make it go away?

These are old disks. The only sensible option is probably to retire them both if the prognosis is bad, so some risk is acceptable, especially given that there is a mirror.

Code: Select all

# [orac.738] uname -a
Linux orac 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u4 (2019-07-19) x86_64 GNU/Linux

[orac.739] # smartctl -H -a /dev/sdd
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-9-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F3
Device Model:     SAMSUNG HD103SJ
Serial Number:    S246J9FB103441
LU WWN Device Id: 5 0024e9 2043c6f53
Firmware Version: 1AJ10001
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Mon Aug  5 14:53:26 2019 AEST
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:  (0x80)	Offline data collection activity
					was never started.
					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: 		( 9180) 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: 	 ( 153) minutes.
SCT capabilities: 	       (0x003f)	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   100   051    Pre-fail  Always       -       187
  2 Throughput_Performance  0x0026   054   054   000    Old_age   Always       -       8610
  3 Spin_Up_Time            0x0023   071   068   025    Pre-fail  Always       -       8966
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       347
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       67468
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       362
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       2
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   060   043   000    Old_age   Always       -       40 (Min/Max 7/57)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0030   252   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       22
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       362

SMART Error Log Version: 1
No Errors Logged

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%      1920         -
# 2  Short offline       Completed without error       00%      1897         -
# 3  Extended offline    Completed without error       00%      1875         -
# 4  Short offline       Completed without error       00%      1872         -
# 5  Short offline       Completed without error       00%      1848         -
# 6  Short offline       Completed without error       00%      1824         -
# 7  Short offline       Completed without error       00%      1800         -
# 8  Short offline       Completed without error       00%      1776         -
# 9  Short offline       Completed without error       00%      1752         -
#10  Short offline       Completed without error       00%      1728         -
#11  Extended offline    Completed without error       00%      1707         -
#12  Short offline       Completed without error       00%      1704         -
#13  Short offline       Completed without error       00%      1680         -
#14  Short offline       Completed without error       00%      1656         -
#15  Short offline       Completed without error       00%      1632         -
#16  Extended offline    Completed without error       00%      1619         -
#17  Short offline       Completed without error       00%      1617         -
#18  Short offline       Completed without error       00%      1608         -
#19  Short offline       Completed without error       00%      1584         -
#20  Short offline       Completed without error       00%      1560         -
#21  Extended offline    Completed without error       00%      1539         -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    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.
It's all just 1's and 0's.  You just have to get them in the right order.
Top
User avatar
phenest
Posts: 1702
Joined: 2010-03-09 09:38
Location: The Matrix

Re: Interpreting SMART report

#2 Post by phenest »

The self assessments are more reliable than software interpreting the SMART data. There are hard drives with unknown attributes that the software has to guess at what it represents.

If the self assessments show as PASSED, don't worry about it.
ASRock H77 Pro4-M i7 3770K - 32GB RAM - Pioneer BDR-209D
Top
linuxbuild
Posts: 9
Joined: 2018-10-26 08:44
Has thanked: 3 times

Re: Interpreting SMART report

#3 Post by linuxbuild »

It's critical according to the Acronis database: https://kb.acronis.com/content/9133

Use hardware probe next time: https://wiki.debian.org/Hardware/Database. It highlights bad attributes automatically.
Top
User avatar
eor2004
Posts: 251
Joined: 2013-10-01 22:49
Location: Puerto Rico
Has thanked: 4 times
Been thanked: 5 times

Re: Interpreting SMART report

#4 Post by eor2004 »

linuxbuild wrote:Use hardware probe next time: https://wiki.debian.org/Hardware/Database. It highlights bad attributes automatically.
Sorry man but, I think that's for sending debian a list of what hardware you have on your system so they can determine if it's compatible with linux kernel and/or debian!
Debian 12 Gnome on a MSI H61M-P25 (B3) PC & on a Dell Latitude E6410 & HP EliteBook 8540p Laptops.
LMDE 6 on a Panasonic ToughBook CF-C1 Laptop.
Bodhi Linux 7 on a HP Compaq DC5750 Small Form Factor PC.
Windows 11 on a Intel DH55TC PC.
Top
User avatar
eor2004
Posts: 251
Joined: 2013-10-01 22:49
Location: Puerto Rico
Has thanked: 4 times
Been thanked: 5 times

Re: Interpreting SMART report

#5 Post by eor2004 »

gpw928 wrote:Hi, Even though the SMART overall-health self-assessment repeatedly gets a "PASSED", the SMART daemon keeps on reporting sdd as a problem.
Looking at the disk "Raw_Value" I dare to say your disk is OK, if it is an SSD don't worry, ssd realocates sectors all the time, but if it is an HDD and if it says it has a lot of reallocated sectors, I would use them to make backups of my data only, install "gnome-disk-utility" and/or "gsmart" both available on debian repos, if they both says "PASS" your disk is ok!
Debian 12 Gnome on a MSI H61M-P25 (B3) PC & on a Dell Latitude E6410 & HP EliteBook 8540p Laptops.
LMDE 6 on a Panasonic ToughBook CF-C1 Laptop.
Bodhi Linux 7 on a HP Compaq DC5750 Small Form Factor PC.
Windows 11 on a Intel DH55TC PC.
Top
p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: Interpreting SMART report

#6 Post by p.H »

Code: Select all

197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1
This attribute is supposed to count currently known unreadable sectors. When unreadable sectors are discovered, it is increased. When they are successfully read, repaired or reallocated, it is decreased. But dd (you should use badblocks instead) over the full length and all previous offline self-tests did not report any error.
I had a old disk in this situation which worked fine. I guess this is a firmware bug. It is just annoying because it triggers bogus alerts by SMART software.
Top
linuxbuild
Posts: 9
Joined: 2018-10-26 08:44
Has thanked: 3 times

Re: Interpreting SMART report

#7 Post by linuxbuild »

eor2004 wrote:
linuxbuild wrote:Use hardware probe next time: https://wiki.debian.org/Hardware/Database. It highlights bad attributes automatically.
Sorry man but, I think that's for sending debian a list of what hardware you have on your system so they can determine if it's compatible with linux kernel and/or debian!
It also checks all your hard drives: https://linux-hardware.org/?probe=8309a ... g=smartctl
Top
User avatar
sunrat
Administrator
Administrator
Posts: 6458
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 472 times

Re: Interpreting SMART report

#8 Post by sunrat »

linuxbuild wrote:
eor2004 wrote:
linuxbuild wrote:Use hardware probe next time: https://wiki.debian.org/Hardware/Database. It highlights bad attributes automatically.
Sorry man but, I think that's for sending debian a list of what hardware you have on your system so they can determine if it's compatible with linux kernel and/or debian!
It also checks all your hard drives: https://linux-hardware.org/?probe=8309a ... g=smartctl
So that runs smartcl from a website. How is that different from running it locally as the OP has done?
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Top
Post Reply

Return to “Hardware”