SSD Wearout - Wear Level Reporting Wrong value on Samsung SSD 870 Evo

[Mikesco3]

Hi I just wanted to share this because of the potential of this impacting more people, and there is the small possibility that I might be wrong...
I have a 1TB Samsung 870 EVO Sata SSD.
Proxmox is reporting the Wearout Value to be 4%


However when I go to get he smart values, it is showing 79%:


The reason I discovered this, is because I have a small tool that I sort of vibe-coded (I'm not a real programmer), so please don't judge:
https://github.com/Mikesco3/drivestatus.sh

And it was reporting:


So I ran

smartctl -a /dev/sde

And got:

smartctl 7.4 2024-10-15 r5620 [x86_64-linux-6.17.2-2-pve] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 870 EVO 1TB
Serial Number:    REDACTED-SN
LU WWN Device Id: 5 002538 fc252589a
Firmware Version: SVT02B6Q
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Dec  3 02:02:25 2025 CST
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:              (0x53) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    No 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:      (  85) 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: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       23246
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       20
177 Wear_Leveling_Count     0x0013   096   096   000    Pre-fail  Always       -       79
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   069   058   000    Old_age   Always       -       31
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   100   100   000    Old_age   Always       -       0
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       11
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       250639857185
252 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       4

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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
  256        0    65535  Read_scanning was never started
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.

The above only provides legacy SMART information - try 'smartctl -x' for more

And if you notice the Wear_Leveling_Count 79% and the 4 is some unknown attribute...

For good meassure I also ran smartctl -x /dev/sde:
(I've attached those results in the text file)

 

[uzumo]

It does not appear to be retrieving incorrect values.

The raw value appears to be 79.
The normalized value is 96, and the 4% loss is correct.

We will verify the normalized rather than the raw value.

The reason drivestatus.sh retrieves raw values should be confirmed with the script's developer; I don't think it's something we should discuss here.

 

[LnxBil]

You can verify with the Samsung Magician if you can find a version that works on Linux. A quick check revealt, that it may not be the case anymore.

 

[Mikesco3]

You can verify with the Samsung Magician if you can find a version that works on Linux. A quick check revealt, that it may not be the case anymore.

I checked and there is no Samsung Magician tool available for Samsung Evo Drives...
I even tried to download the only Linux tool I saw under Samsung Magician software (even though it said it's only available for DC drives) and predictably it didn't detect my Samsung Drive...


All of that being said, I still think Proxmox is picking up the wrong value to display on the Web Gui...
And if that is true I can totally see a bunch of people affected by this and about to have a bad surprise coming up...

 

[Mikesco3]

It does not appear to be retrieving incorrect values.

The raw value appears to be 79.
The normalized value is 96, and the 4% loss is correct.

We will verify the normalized rather than the raw value.

The reason drivestatus.sh retrieves raw values should be confirmed with the script's developer; I don't think it's something we should discuss here.

Can you explain this a bit more... ?
I'm the one that wrote the script, and I would totally love to improve it if that's the case...

 

[Mikesco3]

It does not appear to be retrieving incorrect values.

The raw value appears to be 79.
The normalized value is 96, and the 4% loss is correct.

We will verify the normalized rather than the raw value.

The reason drivestatus.sh retrieves raw values should be confirmed with the script's developer; I don't think it's something we should discuss here.

Thank you uzumo... I just plugged in what you said into ChatGPT and I learned that the

> Samsung SMART RAW_VALUE=79 is not 79% wear

and that I should be going by the normalized Value...

I'll look into changing that...

Thank you for sharing that!!

 

[uzumo]

Learning various things on the forum is a good thing.

I'm glad I could help you understand it.

Once your question is resolved, please mark it as resolved.