smartctl- "Unknown_Attribute" and Missing "Current_Pending_Sector" Attribute

SwapLink · 02-06-2017, 04:16 PM

I am running windows and using smartontools. I have a 1Tb Sandisk X400 SSD on SATA and am trying to diagnose some bad block errors. I am new to this tool and need some things cleared up. Firstly, I ran an extended scan with smartctl -t long /dev/sda (I assume '/dev/sda' is the correct drive?). I ran this twice, and then did smartctl -a /dev/sda to get the results. Here is what I got:

Code:

C:\WINDOWS\system32>smartctl -a /dev/sda
smartctl 6.5 2016-05-07 r4318 [x86_64-w64-mingw32-win10] (sf-6.5-1)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SanDisk SD8SB8U1T001122
Serial Number:    161040441592
LU WWN Device Id: 5 001b44 4a49cac3f
Firmware Version: X4161000
User Capacity:    1,024,209,543,168 bytes [1.02 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Feb 06 13:43:59 2017 PST
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:                (    0) seconds.
Offline data collection
capabilities:                    (0x11) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        No 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:        (  10) minutes.

SMART Attributes Data Structure revision number: 4
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0032   100   100   ---    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   ---    Old_age   Always       -       2565
 12 Power_Cycle_Count       0x0032   100   100   ---    Old_age   Always       -       814
165 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       81630069062
166 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       1
167 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       37
168 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       10
169 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       797
170 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       0
171 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       0
173 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       2
174 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       104
184 End-to-End_Error        0x0032   100   100   ---    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   ---    Old_age   Always       -       63207
188 Command_Timeout         0x0032   100   100   ---    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   068   058   ---    Old_age   Always       -       32 (Min/Max 14/58)
199 UDMA_CRC_Error_Count    0x0032   100   100   ---    Old_age   Always       -       0
230 Unknown_SSD_Attribute   0x0032   100   100   ---    Old_age   Always       -       399433793629
232 Available_Reservd_Space 0x0033   100   100   004    Pre-fail  Always       -       100
233 Media_Wearout_Indicator 0x0032   100   100   ---    Old_age   Always       -       2510
234 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       6286
241 Total_LBAs_Written      0x0030   253   253   ---    Old_age   Offline      -       5104
242 Total_LBAs_Read         0x0030   253   253   ---    Old_age   Offline      -       4963
244 Unknown_Attribute       0x0032   000   100   ---    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 2890 (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 2890 occurred at disk power-on lifetime: 2560 hours (106 days + 16 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
  -- -- -- -- -- -- --
  41 40 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 58 48 dc 63 40 00      00:00:00.000  READ FPDMA QUEUED

Error 2889 occurred at disk power-on lifetime: 2560 hours (106 days + 16 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
  -- -- -- -- -- -- --
  41 40 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 08 70 98 80 40 00      00:00:00.000  READ FPDMA QUEUED

Error 2888 occurred at disk power-on lifetime: 2560 hours (106 days + 16 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
  -- -- -- -- -- -- --
  41 40 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 60 98 80 40 00      00:00:00.000  READ FPDMA QUEUED

Error 2887 occurred at disk power-on lifetime: 2560 hours (106 days + 16 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
  -- -- -- -- -- -- --
  41 40 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 68 98 80 40 00      00:00:00.000  READ FPDMA QUEUED

Error 2886 occurred at disk power-on lifetime: 2560 hours (106 days + 16 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
  -- -- -- -- -- -- --
  41 40 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 60 98 80 40 00      00:00:00.000  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       00%      2561         109297784
# 2  Extended offline    Completed: read failure       00%      2560         290713688
# 3  Short offline       Completed without error       00%         0         -

Selective Self-tests/Logging not supported

I am not sure how to find the number of bad blocks. I am also not sure why many so many attributes appear unknown. I also need to know how often I should be getting bad blocks before failure is imminent. I need to know if I should replace my drive. (I have checked other threads, but they did not have undefined attributes).

Windows 10 x64 (dual booting with Ubuntu)
i7-4710HQ
Sandisk X400 1Tb SSD SD8SB8U1T001122
Nvidia GTX 850m
16Gb DDR3

rtmistler · 02-07-2017, 07:22 AM

Hi SwapLink and welcome to LQ.

While your question is very detailed, it is not a Linux question. This thread will be moved to a non-Linux forum.

SwapLink · 02-07-2017, 09:43 PM

Quote:

Originally Posted by rtmistler

Hi SwapLink and welcome to LQ.

While your question is very detailed, it is not a Linux question. This thread will be moved to a non-Linux forum.

This can actually be considered a linux question. This SMART checking tool can be used on Windows or Linux. Just replace the word "Windows" in my post with Ubuntu, Arch, etc. if you like. There is also another thread that is about the same tool: here. However, this is a different question.