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 09-24-2020, 11:39 AM   #1
Completely Clueless
Member
 
Registered: Mar 2008
Location: Marbella, Spain
Distribution: Many and various...
Posts: 913

Rep: Reputation: 71
Hard Drive Health smartctl Data


Gentlemen,

I've just updated from Mint 17 to 20, got the essentials all up and running and thought I'd better run a HDD health check at the same time before going any further, just in case the drive is a junker. As ever, the smartctl output passeth all my understanding so I was hoping some kind souls here could interpret the hieroglyphs below for me? Is the disk any good?

Many thanks.


Code:
bruno@bruno-laptop:~$ sudo smartctl -s on /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-48-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

bruno@bruno-laptop:~$ sudo smartctl -a -d ata /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-48-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HCC543232A7A380
Serial Number:    E203421L3TZSTP
LU WWN Device Id: 5 000cca 706f5a2ea
Firmware Version: ES2OA60W
User Capacity:    320,072,933,376 bytes [320 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Thu Sep 24 16:26:56 2020 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

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: 		(   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     0x000b   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   238   238   033    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       14
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       7
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       14
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       2
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       14
194 Temperature_Celsius     0x0002   150   150   000    Old_age   Always       -       40 (Min/Max 20/53)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 4
	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 4 occurred at disk power-on lifetime: 30051 hours (1252 days + 3 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
  -- -- -- -- -- -- --
  84 51 81 0b 48 7e 06  Error: ICRC, ABRT 129 sectors at LBA = 0x067e480b = 108939275

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 8c 47 7e e6 08   1d+00:06:19.717  READ DMA
  c8 00 00 8c 46 7e e6 08   1d+00:06:19.712  READ DMA
  c8 00 00 8c 45 7e e6 08   1d+00:06:19.707  READ DMA
  c8 00 00 8c 44 7e e6 08   1d+00:06:19.702  READ DMA
  c8 00 00 8c 43 7e e6 08   1d+00:06:19.698  READ DMA

Error 3 occurred at disk power-on lifetime: 29134 hours (1213 days + 22 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
  -- -- -- -- -- -- --
  84 51 70 1c 5b 3c 00  Error: ICRC, ABRT at LBA = 0x003c5b1c = 3955484

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ca 00 00 8c 5a 3c e0 08   1d+20:50:01.806  WRITE DMA
  ca 00 00 8c 59 3c e0 08   1d+20:50:01.796  WRITE DMA
  ca 00 00 8c 58 3c e0 08   1d+20:50:01.120  WRITE DMA
  ca 00 00 8c 57 3c e0 08   1d+20:50:01.108  WRITE DMA
  ca 00 00 8c 56 3c e0 08   1d+20:50:01.096  WRITE DMA

Error 2 occurred at disk power-on lifetime: 14089 hours (587 days + 1 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
  -- -- -- -- -- -- --
  84 51 d1 bb 93 89 05  Error: ICRC, ABRT 209 sectors at LBA = 0x058993bb = 92902331

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 00 8c 93 89 e5 08      00:20:24.382  READ DMA
  c8 00 00 8c 92 89 e5 08      00:20:24.377  READ DMA
  c8 00 00 8c 91 89 e5 08      00:20:24.372  READ DMA
  c8 00 00 8c 90 89 e5 08      00:20:24.366  READ DMA
  c8 00 00 8c 8f 89 e5 08      00:20:24.332  READ DMA

Error 1 occurred at disk power-on lifetime: 9757 hours (406 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
  -- -- -- -- -- -- --
  84 51 00 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 08      06:38:27.792  IDENTIFY DEVICE
  ca 00 05 32 01 00 e0 08      06:38:27.792  WRITE DMA
  27 00 00 00 00 00 e0 08      06:38:27.790  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 08      06:38:27.787  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      06:38:27.784  SET FEATURES [Set transfer mode]

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%     40182         -
# 2  Short offline       Completed without error       00%     40179         -
# 3  Short offline       Completed without error       00%         0         -

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.
 
Old 09-24-2020, 12:01 PM   #2
beachboy2
Senior Member
 
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 22 MATE, Peppermint OS-Devuan, EndeavourOS
Posts: 4,287
Blog Entries: 48

Rep: Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581Reputation: 1581
Completely Clueless,

Nothing to worry about. Your disk is fine.

Reallocated_Sector_Count (#5) and Current_Pending_Sector (#197) are both zero.

5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0

197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0

https://www.thomas-krenn.com/en/wiki...using_Smartctl

https://ubuntuforums.org/showthread.php?t=2414921

https://www.smartmontools.org/wiki/BadBlockHowto

Last edited by beachboy2; 09-24-2020 at 12:03 PM.
 
2 members found this post helpful.
Old 09-24-2020, 12:12 PM   #3
Completely Clueless
Member
 
Registered: Mar 2008
Location: Marbella, Spain
Distribution: Many and various...
Posts: 913

Original Poster
Rep: Reputation: 71
Many thanks for the swift reply, bb2!
 
Old 09-24-2020, 12:29 PM   #4
michaelk
Moderator
 
Registered: Aug 2002
Posts: 26,512

Rep: Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223Reputation: 6223
Looks like a new hard drive. Nothing indicates there are any problems. The only thing that bares interest is the spin up time. Hitachi is supposed to support this parameter but is basically just informational. As posted since the other specific error parameters are zero you are good.
 
1 members found this post helpful.
Old 09-24-2020, 01:40 PM   #5
rknichols
Senior Member
 
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,804

Rep: Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224Reputation: 2224
As other have said, it's basically a new drive (only 7 power-on hours, only 14 power cycles). The only issue is that a 320GB drive is pretty small by today's standards, but if that suits your needs, go with it.
 
Old 09-24-2020, 03:17 PM   #6
Completely Clueless
Member
 
Registered: Mar 2008
Location: Marbella, Spain
Distribution: Many and various...
Posts: 913

Original Poster
Rep: Reputation: 71
Thanks, guys.
AFAIC, 320Gb is more than enough! To be honest, I could easily get away with 100Gb for my needs, but I've partitioned this drive roughly in two, so have 160 odd Gb to play around with. I can't ever recall having more than about 70-80Gb of total drive space used up (that's OS, apps and data!) on any of my previous installations regardless of which OS I was using. I have no idea why anyone would need more unless they do something crazy like store movies on their drives for some reason.
 
Old 09-28-2020, 02:52 PM   #7
rnturn
Senior Member
 
Registered: Jan 2003
Location: Illinois (SW Chicago 'burbs)
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,849

Rep: Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553
Quote:
Originally Posted by Completely Clueless View Post
Thanks, guys.
AFAIC, 320Gb is more than enough! To be honest, I could easily get away with 100Gb for my needs, but I've partitioned this drive roughly in two, so have 160 odd Gb to play around with. I can't ever recall having more than about 70-80Gb of total drive space used up (that's OS, apps and data!) on any of my previous installations regardless of which OS I was using. I have no idea why anyone would need more unless they do something crazy like store movies on their drives for some reason.
Just try buying a new 320GB drive nowadays. The local 'puter store never has anything smaller than 2TB on the shelves. (I can recall when management thought our having just under 2TB for the data warehouse was an expensive extravagance.)

Cheers...

Last edited by rnturn; 09-28-2020 at 02:52 PM. Reason: typo
 
Old 09-28-2020, 05:05 PM   #8
sgosnell
Senior Member
 
Registered: Jan 2008
Location: Baja Oklahoma
Distribution: Debian Stable and Unstable
Posts: 1,943

Rep: Reputation: 542Reputation: 542Reputation: 542Reputation: 542Reputation: 542Reputation: 542
I can remember when 10 MB was huge. I have several HDDs lying around that are in the hundreds of MB range. Their only use is for scavenging the magnets.
 
  


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
'Gender Differences in Twitter Use and Influence Among Health Policy and Health Services Researchers' RandomTroll General 14 12-14-2019 10:07 AM
LXer: Smartctl - Monitoring & Analysis tool for Hard drive LXer Syndicated Linux News 0 11-17-2014 02:00 PM
LXer: Jamaican Ministry of Health is the first to adopt free and open source health system nationwid LXer Syndicated Linux News 0 11-28-2013 08:02 PM
Smartctl giving errors, is hard drive going bad? sk545 Linux - Hardware 8 09-01-2012 07:49 AM
LXer: Strategy & Management: Issues and innovations: Our health is your health LXer Syndicated Linux News 0 07-13-2006 06:33 PM

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

All times are GMT -5. The time now is 01:42 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