Helping someone with their thread and stumbled upon questions of my own.
The issue is: Using SMART on a Samsung SSD in Kubuntu (Linux).
The SSD is pretty typical: Samsung SSD 870 EVO 500GB. I'm in K22.04. It's about 4 years old. Holds just one OS, K22.04.
Yep, read the Wikipedia article on SMART, which raises more questions than it answers. Each disk vendor doing things their own way, etc.
Checked at Samsung, too. They have a diagnostic program you can download, but it's for Windows, Mac, and Android.
Checked at Ask Ubuntu, Stack's, etc., quickly, and so far am not seeing definitive conversations about the issue, especially about interpreting SMART results or output.
I did run the short and long programs on SMART, using standard commands. Lots of output, but I can post some of it.
SMART's bottom-line is: "SMART overall-health self-assessment test result: PASSED"
But I'm wondering about the output. I'll post some it, and see if anyone has thoughts or experience with such.
I had previously run the short 2-minute test. Now the long test:
Test good for 85 minutes (long test):
sudo smartctl -t long /dev/sda
Then check the results with
sudo smartctl -a /dev/sda
Device is: Not in smartctl database [for details use: -P showall]
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
...
I can't (easily) control the columns, but it's easy to sort out from the header line "ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE"
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 072 072 010 Pre-fail Always - 156
9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 25809
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 41
177 Wear_Leveling_Count 0x0013 099 099 000 Pre-fail Always - 12
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 072 072 010 Pre-fail Always - 156
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 072 072 010 Pre-fail Always - 156
187 Reported_Uncorrect 0x0032 099 099 000 Old_age Always - 28
190 Airflow_Temperature_Cel 0x0032 075 056 000 Old_age Always - 25
195 Hardware_ECC_Recovered 0x001a 199 199 000 Old_age Always - 28
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0
235 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 24
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 17139593317
...
Error 28 occurred at disk power-on lifetime: 25392 hours (1058 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
...
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 90% 25807 519240
# 2 Short offline Completed: read failure 90% 25807 519240
# 3 Short offline Completed: read failure 90% 25807 519240
Any ideas/help with any of this? (Yep, backed up my data! ;-) )
The issue is: Using SMART on a Samsung SSD in Kubuntu (Linux).
The SSD is pretty typical: Samsung SSD 870 EVO 500GB. I'm in K22.04. It's about 4 years old. Holds just one OS, K22.04.
Yep, read the Wikipedia article on SMART, which raises more questions than it answers. Each disk vendor doing things their own way, etc.
Checked at Samsung, too. They have a diagnostic program you can download, but it's for Windows, Mac, and Android.
Checked at Ask Ubuntu, Stack's, etc., quickly, and so far am not seeing definitive conversations about the issue, especially about interpreting SMART results or output.
I did run the short and long programs on SMART, using standard commands. Lots of output, but I can post some of it.
SMART's bottom-line is: "SMART overall-health self-assessment test result: PASSED"
But I'm wondering about the output. I'll post some it, and see if anyone has thoughts or experience with such.
I had previously run the short 2-minute test. Now the long test:
Test good for 85 minutes (long test):
sudo smartctl -t long /dev/sda
Then check the results with
sudo smartctl -a /dev/sda
Device is: Not in smartctl database [for details use: -P showall]
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
...
I can't (easily) control the columns, but it's easy to sort out from the header line "ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE"
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 072 072 010 Pre-fail Always - 156
9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 25809
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 41
177 Wear_Leveling_Count 0x0013 099 099 000 Pre-fail Always - 12
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 072 072 010 Pre-fail Always - 156
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 072 072 010 Pre-fail Always - 156
187 Reported_Uncorrect 0x0032 099 099 000 Old_age Always - 28
190 Airflow_Temperature_Cel 0x0032 075 056 000 Old_age Always - 25
195 Hardware_ECC_Recovered 0x001a 199 199 000 Old_age Always - 28
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0
235 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 24
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 17139593317
...
Error 28 occurred at disk power-on lifetime: 25392 hours (1058 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
...
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 90% 25807 519240
# 2 Short offline Completed: read failure 90% 25807 519240
# 3 Short offline Completed: read failure 90% 25807 519240
Any ideas/help with any of this? (Yep, backed up my data! ;-) )
Comment