I ran smartctl --test=long on my ssd drive and then after checked it. The smart erase count seems ridiculously high. This is running on btrfs and it’s a fairly fresh install. I have btrfs-assistant-git with snapper installed.
fstab
[ricklinux@rick-ms7c37 ~]$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=160D-667B /boot/efi vfat defaults,noatime 0 2
UUID=5763454c-2b31-4858-aeaa-b717a836c98d / btrfs subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=5763454c-2b31-4858-aeaa-b717a836c98d /home btrfs subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=5763454c-2b31-4858-aeaa-b717a836c98d /var/cache btrfs subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=5763454c-2b31-4858-aeaa-b717a836c98d /var/log btrfs subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=5763454c-2b31-4858-aeaa-b717a836c98d /swap btrfs subvol=/@swap,defaults,noatime 0 0
/swap/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
[ricklinux@rick-ms7c37 ~]$
smart test
[ricklinux@rick-ms7c37 ~]$ sudo smartctl -a /dev/sda
[sudo] password for ricklinux:
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.17.1-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: WD Blue / Red / Green SSDs
Device Model: WDC WDS500G2B0A-00SM50
Serial Number: 19432C804100
LU WWN Device Id: 5 001b44 8b19db68c
Firmware Version: 411030WD
User Capacity: 500,107,862,016 bytes [500 GB]
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/5319
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: Fri Apr 1 21:08:45 2022 EDT
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: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No 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: ( 10) minutes.
SMART Attributes Data Structure revision number: 4
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0032 100 100 --- Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 --- Old_age Always - 6478
12 Power_Cycle_Count 0x0032 100 100 --- Old_age Always - 2094
165 Block_Erase_Count 0x0032 100 100 --- Old_age Always - 799149199355
166 Minimum_PE_Cycles_TLC 0x0032 100 100 --- Old_age Always - 23
167 Max_Bad_Blocks_per_Die 0x0032 100 100 --- Old_age Always - 38
168 Maximum_PE_Cycles_TLC 0x0032 100 100 --- Old_age Always - 64
169 Total_Bad_Blocks 0x0032 100 100 --- Old_age Always - 154
170 Grown_Bad_Blocks 0x0032 100 100 --- Old_age Always - 0
171 Program_Fail_Count 0x0032 100 100 --- Old_age Always - 0
172 Erase_Fail_Count 0x0032 100 100 --- Old_age Always - 0
173 Average_PE_Cycles_TLC 0x0032 100 100 --- Old_age Always - 42
174 Unexpected_Power_Loss 0x0032 100 100 --- Old_age Always - 88
184 End-to-End_Error 0x0032 100 100 --- Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 --- Old_age Always - 0
188 Command_Timeout 0x0032 100 100 --- Old_age Always - 9
194 Temperature_Celsius 0x0022 073 042 --- Old_age Always - 27 (Min/Max 17/42)
199 UDMA_CRC_Error_Count 0x0032 100 100 --- Old_age Always - 2
230 Media_Wearout_Indicator 0x0032 008 008 --- Old_age Always - 0x081204140812
232 Available_Reservd_Space 0x0033 100 100 004 Pre-fail Always - 100
233 NAND_GB_Written_TLC 0x0032 100 100 --- Old_age Always - 20513
234 NAND_GB_Written_SLC 0x0032 100 100 --- Old_age Always - 42192
241 Host_Writes_GiB 0x0030 253 253 --- Old_age Offline - 36236
242 Host_Reads_GiB 0x0030 253 253 --- Old_age Offline - 10002
244 Temp_Throttle_Status 0x0032 000 100 --- Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 6470 -
# 2 Short offline Completed without error 00% 5905 -
Selective Self-tests/Logging not supported
[ricklinux@rick-ms7c37 ~]$
Is my ssd getting destroyed? I don’t know how to read this?
then keep in mind that the raw values don’t mean much - it’s an internal value that the disk knows about but doesn’t have very much meaning to anyone else looking at it. The VALUE/WORST/THRESH values are generally a more useful guide to disk health (and these all indicate your disk is pretty darned new).
Keep in mind this is my testing desktop and I’m putting it through hell. It gets erased and reloaded at the flip of a switch. I use it with vm installed deleting erasing, formatting etc etc. Many times i have had to hard restart it or shut it down. I’m not that concerned if i destroy the disk They aren’t expensive anyway. I just reloaded it this week so it’s fairly fresh. First time i have run a test on it. This drive has been wiped many times including secure erase. I just wondered as I’m not that familiar with the readout.
Edit: I was wondering more if it had something to do with btrfs.
Assuming these raw values are actually GB then you have written to disk around 134GB per day, which is 0.27 “drive writes per day”. You’d need to check the drive specifications to find out what its life expectancy is based on those values.
I think the key here though, if you’re using a drive heavily for testing etc., is to consider the drive as a consumable and assume you’ll get maybe five years’ use out of it, and budget to replace it when it fails.
Ya …i’m not concerned about life expectancy. It works fantastic on KDE and i have no issues. I just wondered because i don’t really know that much about the btrfs set up other than how to install it set it up and make it work. Understanding all the ins and outs of how it works and doing it the manual method is quite daunting because i don’t have a wealth of knowledge about it. Just the basics. I was more curious with the read out. It’s just a Western digital Blue SSD 500 GB. Nothing special really. Decent drives.
Your mount options looks good.
I was left wondering, does the snapper need a mountpoint in fstab?
I’m not a snapper user but I was under the impression that it should be. Gentoo wiki - Arch Wiki - Reddit
This looks like a Hard Drive? I do see the errors reported but I’m no expert at evaluating what it really means. Looks like errors at the start of the power on? I would assume those errors are from a sudden event such as power loss or hard start? I would run the long test first. It takes 10 minutes or more and then run this to show what it found.
sudo smartctl --test=long /dev/sda
After the time it takes for this test to run which it tells you at the start because it will run offline in the background. Then run the other smart test to show what it reported.
