Transcend TS120GMTS420

[tkaiser]

Transcend TS120GMTS420 is a M.2 2242 SATA SSD not yet supported. 'Smartctl -x' output made on a SATA controller here ​https://pastebin.com/hxkTJxcp (first task, not even mounted the drive at this point -- bash history: ​http://sprunge.us/WbOK) and hours later behind a JMS578 there ​https://pastebin.com/LHUhv5UG

https://www.smartmontools.org/attachment/ticket/761/Transcend.pdf seems to *not* properly describe the attributes since 148-151 are missing for example.

Observations wrt known attributes:
9 interpreted as Power_On_Hours seems to be wrong (still 0 after 2 hours operation)
194 interpreted as Temperature_Celsius matches thumb test

Observations wrt unknown attributes between the two smartctl executions:
148 increased from 9 to 315
149 increased from 1 to 14
150 remained 0
151 increased from 0 to 9
160 remained 0
161 remained 69
163 remained 5
164 increased from 0 to 1012
165 increased from 0 to 5
166 remained 0
167 increased from 0 to 2
169 remained 100
245 increased from 0 to 8096

[tkaiser]

Waited 2 hours and power cycled the device 5 times. Smartctl ouput: ​https://pastebin.com/XPbAjcpX

9 'Power_On_Hours' remains at 0
12 'Power_Cycle_Count' got incremented correctly (8 --> 13)
GP Log 0x04 shows a few more reads

128 MB zeroes written: ​https://pastebin.com/bQPkvuyt

148 increased (315 --> 316)
149 increased (14 --> 15)
164 decreased (1012 --> 1009)
167 decreased (2 --> 1)
241 Total_LBAs_Written increased (2151 --> 2155)
245 decreased (8096 --> 8072)
'Logical Sectors Written' (GP Log 0x04) increases by 262288

zeroes with 128MB random data overwritten: ​https://pastebin.com/sHwFePCB

148 increased (316 --> 318)
241 Total_LBAs_Written increased (2155 --> 2159)
'Logical Sectors Written' (GP Log 0x04) increases by 262384

New 128MB random data written: ​https://pastebin.com/nv2dhr3H

148 increased (318 --> 319)
241 Total_LBAs_Written increased (2159 --> 2163)
'Logical Sectors Written' (GP Log 0x04) increases by 262392

Deleted files, 1024MB zeroes written, buffers flushed, 1024MB read: ​https://pastebin.com/jWc3dKxb

148 increased (319 --> 342)
149 increased (15 --> 16)
151 increased (9 --> 10)
164 increased (1009 --> 1021)
165 increased (6 --> 7)
167 increased (1 --> 2)
241 Total_LBAs_Written increased (2163 --> 2195)
242 Total_LBAs_Read increased (1984 --> 2016)
245 increased (8072 --> 8168)
'Logical Sectors Written' (GP Log 0x04) increases by 2097472
'Logical Sectors Read' (GP Log 0x04) increases by 2097208

Conclusions:
'Logical Sectors' = 512 byte, Log 0x04 shows correct readouts
1 LBA = 32 MByte, attributes 241/242 show correct readouts
148, 149, 151 and 165 are incrementing only
164, 167 and 245 are floating
150, 160, 161, 163, 166 and 169 kept their values

No idea how to interpret these.

[tkaiser]

'SSD scope' output part 1

[tkaiser]

'SSD scope' output part 2

[tkaiser]

Vendor tech support answered to me asking for an interpretation of the SMART attributes today:

'Die SMART Attribute der MTS420 werden, so weit erkennbar, korrekt von "SSD scope" ausgewertet und angezeigt.

Nicht alle SMART Attribute sind "Mandatory", weshalb nicht alle Werte von 00 bis FF auch wirklich verwendet werden.
Da einige Werte "optional" sind, werden sie nicht von jedem Programm mit ihrer Funktion angezeigt
sondern lediglich als "Vendor specific", bei " SSD scope" werden aber die Funktionen "übersetzt"

Je nach Einstellung der Bildschirmeigenschaften des Rechners ist nicht sofort zu erkennen,
dass die SMART Anzeige von "SSD scope" mehr als einen "Bildschirm" mit Information bereitstellt.

Daher 2 Bildschirmfotos als Beispiel im Anhang.'

I'll try to come up with a drivedb.h patch ASAP. Or at least a redacted list of attributes first?

[tkaiser]

  //"-v 148,,SLC_Total_Erase_Cnt "
  //"-v 149,,SLC_Maximum_Erase_Cnt "
  //"-v 150,,SLC_Minimum_Erase_Cnt "
  //"-v 151,,SLC_Average_Erase_Cnt "
  //"-v 160,,Uncorrectable_Sectors_Cnt "
  //"-v 161,,Valid_Spare_Blocks "
  //"-v 163,,Initial_Invalid_Blocks "
  //"-v 164,,TLC_Total_Erase_Cnt "
  //"-v 165,,TLC_Maximum_Erase_Cnt "
  //"-v 166,,TLC_Minimum_Erase_Cnt "
  //"-v 167,,TLC_Average_Erase_Cnt "
  //"-v 169,,Remain_Life_Percentage "
  //"-v 245,,Flash_Write_Sector_Cnt "

[tkaiser]

Adding the following is working for me though I have no idea whether assuming 'raw48' is always correct:

  { "Transcend MTS420",
    "TS(120|240)GMTS420", // tested with TS120GMTS420 only
    "", "", // https://www.smartmontools.org/ticket/869
    "-v 148,raw48,SLC_Total_Erase_Cnt "
    "-v 149,raw48,SLC_Maximum_Erase_Cnt "
    "-v 150,raw48,SLC_Minimum_Erase_Cnt "
    "-v 151,raw48,SLC_Average_Erase_Cnt "
    "-v 160,raw48,Uncorrectable_Sector_Ct "
    "-v 161,raw48,Valid_Spare_Blocks "
    "-v 163,raw48,Initial_Invalid_Blocks "
    "-v 164,raw48,TLC_Total_Erase_Cnt "
    "-v 165,raw48,TLC_Maximum_Erase_Cnt "
    "-v 166,raw48,TLC_Minimum_Erase_Cnt "
    "-v 167,raw48,TLC_Average_Erase_Cnt "
    "-v 169,raw48,Remain_Life_Percentage "
    "-v 245,raw48,Flash_Write_Sector_Cnt "
  },

smartctl -x output as follows: ​http://sprunge.us/ITGF

Attribute 9 increased in the meantime from 0 to 1 so obviously the raw value has to be multiplied (real power on hours might now be 10 hours or something like that). I'll get back to Transcend support asking for help and will simply let the disk run and monitor every hour :)

[tkaiser]

With the following patch applied to latest smartmontools release from SVN I get the following -x output: ​http://sprunge.us/iJje

Index: drivedb.h
===================================================================
--- drivedb.h	(revision 4434)
+++ drivedb.h	(working copy)
@@ -3536,6 +3536,23 @@
     "QUANTUM FIREBALLP KA(9|10).1",
     "", "", ""
   },
+  { "Transcend MTS420",
+    "TS(120|240)GMTS420", // tested with TS120GMTS420 only
+    "", "", // https://www.smartmontools.org/ticket/869
+    "-v 148,raw48,SLC_Total_Erase_Cnt "
+    "-v 149,raw48,SLC_Maximum_Erase_Cnt "
+    "-v 150,raw48,SLC_Minimum_Erase_Cnt "
+    "-v 151,raw48,SLC_Average_Erase_Cnt "
+    "-v 160,raw48,Uncorrectable_Sector_Ct "
+    "-v 161,raw48,Valid_Spare_Blocks "
+    "-v 163,raw48,Initial_Invalid_Blocks "
+    "-v 164,raw48,TLC_Total_Erase_Cnt "
+    "-v 165,raw48,TLC_Maximum_Erase_Cnt "
+    "-v 166,raw48,TLC_Minimum_Erase_Cnt "
+    "-v 167,raw48,TLC_Average_Erase_Cnt "
+    "-v 169,raw48,Remain_Life_Percentage "
+    "-v 245,raw48,Flash_Write_Sector_Cnt "
+  },
 
   ////////////////////////////////////////////////////
   // USB ID entries

Power-on Hours is still way off and smartctl -a (full output ​http://sprunge.us/ZYfZ ) reports

Error 0 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)

and

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.

[Alex Samorukov]

Drive added in r4465. Self test checksum is typically wrong when there are no tests in it. It is a vendor fw bug.

[Christian Franke]

Merged in r4490.