How to check remaining endurance on Samsung SM1625 SSDs?

BLinux

cat lover server enthusiast
Jul 7, 2016
2,579
1,035
113
artofserver.com
I got a few SM1625 SSDs, and although they seem to work fine (format, zpool, run benchmarks are all good, no errors), smartctl --xall doesn't seem to output total writes or anything else. Just says "SMART Health status: OK" and the usually SMART header data. Do i need a newer version of smartctl ? (was using CentOS 7 bundled smartctl) or, is there a Samsung tool I need to run?
 

ari2asem

Active Member
Dec 26, 2018
751
140
43
The Netherlands, Groningen
i dont have experience with centos, but experience between 2 different versions of smartmontool in windows 10.

when using smartmontool v6.6 i saw the same description (TEMPERATURE) for 2 different attribute numbers. so, i saw 2 different attribute numbers with the name TEMPERATURE.

with version 7.2 of smartmontools was this bug fixed.

i mean...try another software, another version,
 

BLinux

cat lover server enthusiast
Jul 7, 2016
2,579
1,035
113
artofserver.com
Have you tried hdd sentinel?
no... do you know that works with this drive?

i dont have experience with centos, but experience between 2 different versions of smartmontool in windows 10.

when using smartmontool v6.6 i saw the same description (TEMPERATURE) for 2 different attribute numbers. so, i saw 2 different attribute numbers with the name TEMPERATURE.

with version 7.2 of smartmontools was this bug fixed.

i mean...try another software, another version,
yeah... i was thinking maybe a newer version of smartmontools...

as an example, this is what it shows me right now:

Code:
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-3.10.0-1062.12.1.el7.x86_64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SAMSUNG
Product:              MZ6ER400HAGL/003
Revision:             DM0L
Compliance:           SPC-4
User Capacity:        400,088,457,216 bytes [400 GB]
Logical block size:   512 bytes
Physical block size:  8192 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Logical Unit id:      0x5002538475b1b620
Serial number:        SXXXXXXXXXXXX
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Tue Mar 24 17:24:00 2020 PDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Elements in grown defect list: 0

Error Counter logging not supported

Device does not support Self Test logging
Device does not support Background scan results logging
The output is kind of strange for SAS drive... i can usually see total bytes written/read/error corrected ... not here. and the temp reading is always 0C.
 

Indecided

Active Member
Sep 5, 2015
153
71
28
I've had issues with Samsung drives having issues with v7.0 of smartmontools. See linked ticket -

#1258 (Error Counter logging not supported (SAMSUNG MZILT800HAHQ0D3)) – smartmontools

Not sure if it's the same issues you were seeing, but I was seeing issues with PM1633 SAS SSDs not showing up SMART data.
Solution is to downgrade < 7.0 or upgrade to 7.1.

Edit : just saw your post, definitely looks like the same issue. Upgrade or downgrade! You might have to compile yourselves to upgrade, thankfully FreeBSD has a ports system (just trying it out) to automagically upgrade to latest.
 

BLinux

cat lover server enthusiast
Jul 7, 2016
2,579
1,035
113
artofserver.com
I've had issues with Samsung drives having issues with v7.0 of smartmontools. See linked ticket -

#1258 (Error Counter logging not supported (SAMSUNG MZILT800HAHQ0D3)) – smartmontools

Not sure if it's the same issues you were seeing, but I was seeing issues with PM1633 SAS SSDs not showing up SMART data.
Solution is to downgrade < 7.0 or upgrade to 7.1.

Edit : just saw your post, definitely looks like the same issue. Upgrade or downgrade! You might have to compile yourselves to upgrade, thankfully FreeBSD has a ports system (just trying it out) to automagically upgrade to latest.
thanks for that tip! i'm going to rebuild RPM for smartmontools with version 7.1 and see if that resolves the issue! thanks man... sounds somewhat promising...
 

BLinux

cat lover server enthusiast
Jul 7, 2016
2,579
1,035
113
artofserver.com
@Indecided that was it! thanks man...

Code:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-3.10.0-1062.18.1.el7.x86_64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SAMSUNG
Product:              MZ6ER400HAGL/003
Revision:             DM0L
Compliance:           SPC-4
User Capacity:        400,088,457,216 bytes [400 GB]
Logical block size:   512 bytes
Physical block size:  8192 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Logical Unit id:      0x5002538475b1e990
Serial number:        XXXXXXXXXXXX
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Thu Mar 26 00:36:56 2020 PDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Percentage used endurance indicator: 0%
Current Drive Temperature:     30 C
Drive Trip Temperature:        58 C

Manufactured in week 28 of year 2015
Accumulated start-stop cycles:  18
Specified load-unload count over device lifetime:  0
Accumulated load-unload cycles:  0
Elements in grown defect list: 0

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0        0         0         0          0        414.250           0
write:         0        0         0         0          0        814.363           0

Non-medium error count:        4

No Self-tests have been logged

Background scan results log
  Status: waiting until BMS interval timer expires
    Accumulated power on time, hours:minutes 23:46 [1426 minutes]
    Number of background scans performed: 0,  scan progress: 3.00%
    Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 3
  number of phys = 2
  phy identifier = 0
    attached device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5002538475b1e992
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization = 0
    Phy reset problem = 0
    Phy event descriptors:
     Received ERROR  count: 0
     Received address frame error count: 0
     Received abandon-class OPEN_REJECT count: 0
     Received retry-class OPEN_REJECT count: 0
     Received SSP frame error count: 0
relative target port id = 2
  generation code = 3
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5002538475b1e993
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization = 0
    Phy reset problem = 0
    Phy event descriptors:
     Received ERROR  count: 0
     Received address frame error count: 0
     Received abandon-class OPEN_REJECT count: 0
     Received retry-class OPEN_REJECT count: 0
     Received SSP frame error count: 0
 
  • Like
Reactions: nikalai