Question Anything wrong with this SMART data?

[mikeymikec]

The PC refused to boot, citing the disk's failure. The Windows system log cited multiple bad blocks and (source 'DiskDiagnostic') SMART data showing some kind of failure too. Can anyone tell me what I should be paying attention to here?

 

[Soulkeeper]

Looks like 100 reallocated sectors
Backup anything that isn't already backed up, and keep a close eye on it.
It's probably done, but I guess you could try to keep it going. If no more bad sectors happen it might still be worth keeping.

 

[mxnerd]

Looks like 100 reallocated sectors

Where did you get this number from the posted picture?

This is my drive.

 

[Steltek]

View attachment 20033

The PC refused to boot, citing the disk's failure. The Windows system log cited multiple bad blocks and (source 'DiskDiagnostic') SMART data showing some kind of failure too. Can anyone tell me what I should be paying attention to here?

The ones I always start off looking at are, in addition to reallocated sector counts, reported uncorrectable errors, command timeout, current pending sector count, and uncorrectable sector count. When those items start increasing, it is often an indicator of a problem.

 

[mikeymikec]

I'm a wee bit confused. CrystalDiskInfo in my experience reports the status of any drive with >0 bad sectors (of any category) as 'Caution' yet it says 'Healthy' here and all those raw values say zero.

I'm already in the process of replacing the drive but I'm curious to know what's actually wrong with it. With the BIOS reporting the drive as failed I was expecting either a disk that wouldn't spin up / power up at all or reporting its SMART status as 'BAD' (though I've seen a machine boot Windows with that status ).

 

[Steltek]

I'm a wee bit confused. CrystalDiskInfo in my experience reports the status of any drive with >0 bad sectors (of any category) as 'Caution' yet it says 'Healthy' here and all those raw values say zero.

I'm already in the process of replacing the drive but I'm curious to know what's actually wrong with it. With the BIOS reporting the drive as failed I was expecting either a disk that wouldn't spin up / power up at all or reporting its SMART status as 'BAD' (though I've seen a machine boot Windows with that status ).

Sorry, I had to edit my answer. I had edited something else I had saved for an answer I previously gave, then like an idiot posted the original. That answer didn't pertain to your situation.

 

[coercitiv]

Why are people talking about issues with some fault indicators that have zero as raw value? Example: Reallocated Sector Count is 0, UltraDMA CRC Error Count is 0, Current Sector Count and Uncorrectable Sector Count are also at 0.

 

[Soulkeeper]

The problem might be he's using an older version of crystal disk info.
It's possible the wrong attribute names can even be in place if it don't have a recent enough drive database.
Update and see if things change, or use a different program. All I saw was "100" so I can't know if it's right or not.
The "Temperature" attribute is clearly wrong.

 

[coercitiv]

The "Temperature" attribute is clearly wrong.

Why is it clearly wrong?

 

[mikeymikec]

The temp stat wasn't wrong (26C). That reading was with the drive plugged into an open USB enclosure, within a minute or so of being switched on.

The version of CDI is old, but I've been using that version for many years without any question of its function. It's an interesting point though, perhaps a newer version would flag other attributes as being within a questionable range. I'll give it a try soon.

 

[ArisVer]

I find that CrystalDiskInfo is inconsistent with its results, take a look at my results, same disk.
The top one taken on July 2019 and the bottom one just yesterday. Look at number 7.

 

[Soulkeeper]

The different ID/Attributes rely on an internal database or lookup table. It varies between drives and must be updated from time to time.
In linux we use the command smartctl to display smart data, It come with a command update-smart-drivedb which downloads the latest database to ensure you are interpretting the drive correctly.
I'd imagine windows/crystal does something similar. The latest database likely comes with the self extracting .exe for whatever version you install.

 

[mikeymikec]

As I normally use Linux I tried another tactic, connecting the disk up and checked its SMART data through the Disks app.

Its overall assessment was: "Disk is OK, one attribute failed in the past"

The attribute in question was the 'seek error rate':
Value: 0
Normalised: 100
Threshold: 67
Worst: 64

Smartctl's output for that entry:

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-96-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA100
Serial Number:    bork!
LU WWN Device Id: 5 000039 ffeed0e28
Firmware Version: MS2OA7C0
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun Apr 26 11:33:35 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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x84)    Offline data collection activity
                    was suspended by an interrupting command from host.
                    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:         ( 7216) 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:      ( 121) 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   095   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0027   142   100   054    Pre-fail  Always       -       69
  3 Spin_Up_Time            0x0023   212   100   024    Pre-fail  Always       -       139 (Average 77)
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       8443
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   064   067    Pre-fail  Always   In_the_past 0
  8 Seek_Time_Performance   0x0025   108   100   020    Pre-fail  Offline      -       37
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       11360
10 Spin_Retry_Count        0x0033   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       4591
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       65535
187 Reported_Uncorrect      0x0032   074   074   000    Old_age   Always       -       26
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       743111983109
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   072   052   000    Old_age   Always       -       28 (Min/Max 25/28)
192 Power-Off_Retract_Count 0x0032   093   093   000    Old_age   Always       -       8573
193 Load_Cycle_Count        0x0032   093   093   000    Old_age   Always       -       8573
194 Temperature_Celsius     0x0022   214   125   000    Old_age   Always       -       28 (Min/Max 10/48)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
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    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 26 (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 26 occurred at disk power-on lifetime: 11358 hours (473 days + 6 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 18 08 97 5a 00  Error: UNC at LBA = 0x005a9708 = 5936904

  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 20 20 80 fe 6a 40 00      00:09:15.737  READ FPDMA QUEUED
  61 18 80 80 ee 21 40 00      00:09:15.736  WRITE FPDMA QUEUED
  61 08 18 10 28 3a 40 00      00:09:15.736  WRITE FPDMA QUEUED
  61 08 10 f8 fc ee 40 00      00:09:15.736  WRITE FPDMA QUEUED
  61 28 08 80 ba 4b 40 00      00:09:15.736  WRITE FPDMA QUEUED

Error 25 occurred at disk power-on lifetime: 11358 hours (473 days + 6 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 38 30 e2 9d 01  Error: UNC at LBA = 0x019de230 = 27124272

  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 20 98 20 d3 2f 40 00      00:07:37.692  READ FPDMA QUEUED
  60 20 88 60 dd 2f 40 00      00:07:37.692  READ FPDMA QUEUED
  60 20 80 a0 a2 16 40 00      00:07:37.692  READ FPDMA QUEUED
  60 20 78 e0 b0 16 40 00      00:07:37.692  READ FPDMA QUEUED
  61 08 70 58 c3 3c 40 00      00:07:37.692  WRITE FPDMA QUEUED

Error 24 occurred at disk power-on lifetime: 11358 hours (473 days + 6 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 58 e0 6b 60 06  Error: UNC at LBA = 0x06606be0 = 106982368

  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 40 f8 e0 19 23 40 00      00:06:00.206  READ FPDMA QUEUED
  60 40 f0 78 7d 37 40 00      00:05:59.704  READ FPDMA QUEUED
  60 40 e8 82 3f 3b 40 00      00:05:59.202  READ FPDMA QUEUED
  60 01 d8 00 40 2b 40 00      00:05:58.700  READ FPDMA QUEUED
  60 20 d0 40 c6 6a 40 00      00:05:58.689  READ FPDMA QUEUED

Error 23 occurred at disk power-on lifetime: 11358 hours (473 days + 6 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 f8 7c 4b 00  Error: UNC at LBA = 0x004b7cf8 = 4947192

  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 20 b0 08 40 35 40 00      00:03:47.191  READ FPDMA QUEUED
  61 08 a8 d0 32 8f 40 00      00:03:46.690  WRITE FPDMA QUEUED
  60 10 88 98 19 49 40 00      00:03:46.610  READ FPDMA QUEUED
  60 08 10 20 de 3c 40 00      00:03:46.163  READ FPDMA QUEUED
  61 20 a8 e0 9f c1 40 00      00:03:44.690  WRITE FPDMA QUEUED

Error 22 occurred at disk power-on lifetime: 11358 hours (473 days + 6 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 28 c8 63 81 09  Error: WP at LBA = 0x098163c8 = 159474632

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 f8 00 a9 1c 40 00      00:01:18.740  WRITE FPDMA QUEUED
  61 00 e8 00 a8 1c 40 00      00:01:18.740  WRITE FPDMA QUEUED
  60 14 50 d0 a6 3b 40 00      00:01:18.507  READ FPDMA QUEUED
  60 40 f0 7a e1 4d 40 00      00:01:18.493  READ FPDMA QUEUED
  61 08 e8 18 00 5f 40 00      00:01:18.492  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Interrupted (host reset)      90%         3         -

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.

So it was the seek error rate attribute that got tripped ('worst' reading is below 'threshold', and it's flagged). It's also pretty cool that you get the history of when the SMART system posted errors, so if you've got a squirrelly system event to line it up with, that should be more or less possible.

 

[Soulkeeper]

That looks ok.
I usually try to run smartctl -t long /dev/whatever on a regular basis (maybe once a month).

 

[Shmee]

Other good programs to try are HDtune and Partedmagic. Anyway, why is this computer not using an SSD?

 

[mikeymikec]

Anyway, why is this computer not using an SSD?

It is now!