I have a 512GB Samsung SSD in a 2014 MacBook Pro that I purchased new around 2 months ago. I installed Smartmontools via Homebrew to take a look at some of the SSD health / SMART data. Everything looks fine for the most part, but one thing that I'm not understanding is the Wear_Leveling_Count which currently has a value of 12895125514.
This really isn't my area of expertise but I thought Wear_Leveling_Count was typically reported as either a percentage (indicating the life remaining according to the endurance specifications of the manufacturer), or as a raw P/E cycle count. In either case, the value I'm getting seems extremely high.
Does anybody know what's going on here? Am I misinterpreting / misunderstanding something here? Could this potentially be a bug in Smartmontools or the SSD firmware? Smartmontools is also reporting the Wear_Leveling_Count ID as 173 when it should be 177 shouldn't it?
As I mentioned, I'm a bit of a novice in this particular area so any info / suggestions are greatly appreciated.
Update: I came across this reddit thread regarding Wear_Leveling_Count: https://www.reddit.com/r/linux/comments/31btmz/what_is_your_177_wear_leveling_count/
About halfway down the page there's a Samsung XP941 user (which I believe is the same SSD used in the 2014 MacBook Pro). He reports a Wear_Leveling_Count value of 197, which is much more in line with what I'd expect. It also looks like the Wear_Leveling_Count ID should indeed be 177 (as I mentioned, I get an ID of 173). This makes me think it might be some sort of OS X / Apple specific bug.
Does anybody know if Samsung does something different to the SSDs they manufacture for Apple? Smartmontools reports the SSD as an APPLE SSD SM0512F (which as I mentioned, is supposedly just a Samsung XP941). Could something unique to Apple SSDs be confusing Smartmontools?
Thanks
sudo trimforce enable
. After entering your password (it's normal that you don't see what you type), it should enable TRIM on your device, so when deleting a file, the OS doesn't "delete" the file itself, but delegates that to the SSD with its own implementation. That reduces the OS overhead over the SSD a lot. – Alejandro Iván Aug 9 '15 at 3:11