#641 closed defect (invalid)

kingston ssd uv300 Runtime_Bad_Block

Reported by: poiuty Owned by:
Priority: major Milestone:
Component: smartctl Version: 6.4
Keywords: Cc:

Description

Hi, kingston ssd uv300 Runtime_Bad_Block => FAILING_NOW => 393217
And this value increase. So, it`s real bad ssd drive?
Or it`s normal increase value for this ssd model?

./smartctl -A /dev/sda
smartctl 6.5 2016-01-22 r4209 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
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   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   100   100   050    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0013   100   100   050    Pre-fail  Always       -       0
  7 Unknown_SSD_Attribute   0x000b   100   100   050    Pre-fail  Always       -       0
  8 Unknown_SSD_Attribute   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       24
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       12
168 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       0
170 Unknown_Attribute       0x0003   100   100   010    Pre-fail  Always       -       270
173 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       65542
175 Program_Fail_Count_Chip 0x0013   100   100   050    Pre-fail  Always       -       0
183 Runtime_Bad_Block       0x0012   100   100   100    Old_age   Always   FAILING_NOW 393217
187 Reported_Uncorrect      0x0012   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       7
194 Temperature_Celsius     0x0023   069   051   030    Pre-fail  Always       -       31 (Min/Max 23/49)
196 Reallocated_Event_Count 0x0002   100   100   010    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x000b   100   100   050    Pre-fail  Always       -       0
218 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
231 Temperature_Celsius     0x0013   100   100   000    Pre-fail  Always       -       100
233 Media_Wearout_Indicator 0x000b   100   100   000    Pre-fail  Always       -       375
240 Unknown_SSD_Attribute   0x0013   100   100   000    Pre-fail  Always       -       0
241 Total_LBAs_Written      0x0012   100   100   000    Old_age   Always       -       318
242 Total_LBAs_Read         0x0012   100   100   000    Old_age   Always       -       215
244 Unknown_Attribute       0x0002   100   100   000    Old_age   Always       -       1
245 Unknown_Attribute       0x0002   100   100   000    Old_age   Always       -       6
246 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       98976

Change History (1)

comment:1 Changed 18 months ago by chrfranke

  • Resolution set to invalid
  • Status changed from new to closed

Please don't use tracker for support questions. Use mailing list instead.

Regarding your question: Attributes look sane. Names may be incorrect because drive is not in database.

The RAW values may have any vendor specific meaning. A large value does not necessarily indicate a problem.

FAILING_NOW is printed by smartctl because VALUE 100 is less or equal THRESHold 100. Firmware possibly returns a bogus threshold.

Note: See TracTickets for help on using tickets.